Repository navigation
docs: record purpose, zkVM findings, and consensus-layer roadmap - #6
Merged
Merged
Conversation
Capture the 2026-09-17/18 discussion: why the consensus-layer state transition is being proved, where weigh sits in the block and epoch flow, what the ZisK segment-padding result means for the metric to track, the PoC decisions (in-memory state model, Merkle access deferred to #4, resident prover later), the remaining consensus-layer work, and what is left for a consensus-layer zkVM once the execution layer is proved by a zkEVM and BLS is replaced by aggregated XMSS proofs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
docs/roadmap.mdand links it from README and DESIGN.md. It records the discussion following #5:weigh_justification_and_finalizationcame firstweighsteps equal RV64 steps, one 2^22-row segment is 98% padding, so steps by symbol is the metric to track and per-process overheads are deployment costsBeaconStatemodel per the spec, stateless Merkle access deferred to Stateless block_roots access: pass only the two read roots with SSZ Merkle proofs #4, resident prover later, no GPU re-measurement for a byte-identical guestAlso shortens README.md to a 30-line overview; the build, toolchain, test-coverage, and ZisK guest instructions move verbatim to
docs/build.md, anddocs/benchmarks.mdnow points there.Documentation only; no code changes.