Full KES Agent Integration

[dnadales]

🧑‍⚖ Represents items requiring stakeholder decisions.

• Locked KES and DSIGN primitives
  • cardano-base:cardano-crypto-class
• Networking: RawBearer
• Direct serialization
  • cardano-base
  • ouroboros-network
• Use mlocked KES / DSIGN in ouroboros-consensus
  • Facilitate secure key deletion
  • Move opcerts into HotKey
  • Prepare LeaderCredentials to take a "recipe" for obtaining a KES SignKey, rather than the key itself.
  • Set up block forging threads for hot-swapping KES keys and correctly managing their ownership and lifecycles.
• KES Agent
  • Library
  • Control client
  • Example service client
  • Add KES agent connectivity to ouroboros-consensus
  • Split Serdoc stuff in kes-agent into a separate sub-library
  • KES agent integration #1487
  • Code audit
  • Address open questions:
    • Dealing with KES key validity discrepancies input-output-hk/kes-agent#39
    • OpCert counters input-output-hk/kes-agent#40
• Add TCP as an alternative to domain sockets (#42)¹.
• Integrate new ouroboros-consensus version with cardano-node²
• KES agent setup improvements (Make KES agents easier to set up, potentially by providing ready-to-use images for Docker containers).
• Deployment
  • Demo working system to (some) SPOs
  • Gather and address feedback
  • Limited field test
  • Roll out as an optional feature
  • Gauge adoption
  • Eventually: Make KES agents mandatory

Footnotes

1. This would require adding authentication and encryption features to KES agent itself, which might take 3 to 6 months. ↩

2. This will mostly be a matter of changing how configuration is loaded on startup, to match the new configuration structure of ouroboros-consensus. ↩