Evolution timing

Open
#7 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
haskell

Research direction

No files or tests are named. Start by tracing how the KES agent stores keys, receives keys from the Control server, and reads configuration; compare those entry points with the proposed RTC-based evolution timing. Done means the agent evolves keys on the configured schedule without contacting the chain and honors timing supplied with new keys.

Written by the indexing model from the issue text.

Description

backburner research

Plan:

We don't want the KES agent to actively contact the chain. Hence:

  • KES agent uses system clock (RTC) to autonomously decide when to evolve keys; we tune it to be slightly late, so that when things are slightly out of synch, connecting nodes get the previous key and can evolve by themselves as needed.
  • When Control server sends a new key, it also includes timing information (when the 0th evolution of the key becomes valid)
  • KES agent config tells Agent at what intervals to evolve.
Dominant language
Haskell
Stars
2
Forks
13
PR merge metrics
No merged PRs in 30d

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/kes-agent

All issues in IntersectMBO/kes-agent

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.