List view
## Hash-Based Multi-Signature - A client instance is able to generate the keys for the selected hash-based signature scheme - The client instance is able to sign arbritary message with the selected hash-based signature scheme - The client instance is able to verify the signed message ## Block Production - A client instance is able to produce and sign an empty block - The client instance is able to propagate its signed block - Another client instance is able to receive and validate the propagated empty block
Due by September 30, 2025•0/2 issues closed## ZK State Transition Proving - Benchmarks for additional state transition functions against additional zkVM systems ## ZK State Propagation and Verification - A client instance is able to propagate its state proof - Another client instance is able to verify the propagated state proof - Benchmarks of the ZK state verification
Overdue by 1 day(s)•Due by June 30, 2025•30/31 issues closedUntil a beam specs come out, we are building a likely-throwaway beam client prototype based purely on our own assumptions, which happen to borrow some beacon specs. ## P2P Networking - Client instances can discover each other via discv5 protocol - Client instances can send/receive messages via gossipsub - Network simulation with 3 client instances ## ZK State Transition Proving & Self-Verification - Proof of concepts with SP1 and RiscZero - A client instance can prove state transition with a selected zkVM - The client instance can self-verify the proof - Benchmarks of the ZK state proving
Overdue by 3 month(s)•Due by March 31, 2025•87/91 issues closed