Support for KES agent

Open
  • Is something wrong?
#2,522 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
blockchain, security

Research direction

The issue does not name files, tests, or an entry point. Start by locating the Mithril Signer’s KES integration and the KES Agent interface; done means signing can optionally be delegated to the agent without direct access to hot KES secret key files.

Written by the indexing model from the issue text.

Description

roadmap :compass:

Why

This task will improve the security of the system by upgrading the Mithril Signer to optionally interact with the KES Agent rather than accessing the critical KES secret key files directly. By delegating the signing operations to the KES Agent, we remove the need for the Mithril Signer to handle "hot" block-producer keys, significantly reducing the attack surface.

Dominant language
Rust
Stars
155
Forks
52
Avg merge
2d 17h
Merged PRs (30d)
37

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IntersectMBO/mithril

All issues in IntersectMBO/mithril

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.