Skip to content

docs: write witness retrieval concept page#9

Merged
bgravenorst merged 1 commit into
mainfrom
feat/witness-retrieval
May 20, 2026
Merged

docs: write witness retrieval concept page#9
bgravenorst merged 1 commit into
mainfrom
feat/witness-retrieval

Conversation

@bgravenorst

@bgravenorst bgravenorst commented May 20, 2026

Copy link
Copy Markdown
Collaborator

Summary

Writes the Witness retrieval concept page (docs/concepts/witness-retrieval.mdx), covering:

  • What an execution witness is and what it contains.
  • Why Zesu needs a witness instead of holding full chain state.
  • The difference between a witness (input, megabytes, local) and a proof (output, kilobytes, distributed), presented as a comparison table.
  • How Zesu currently retrieves witnesses via the debug_executionWitness RPC endpoint provided by the besu-zkevm-plugin.

Review notes

  • A :::caution admonition at the top of the page notes the witness specification and retrieval method are under active development.
  • A :::note in the retrieval section links to execution-apis #741 and #773 for the longer-term Engine API delivery proposals.
  • The description of witness contents ("account states and storage slots accessed") is sourced from the L1 zkEVM explainer. Please flag if more precise wording is required.

Test plan

  • Local npm run build succeeds.
  • After deploy, verify the page renders correctly including the table and admonitions.
  • Confirm the witness contents description is technically accurate.

Made with Cursor


Note

Low Risk
Documentation-only update introducing new conceptual content; no runtime or security-sensitive code paths are affected.

Overview
Adds a substantially expanded Witness retrieval concept page explaining what an execution witness is, why Zesu needs it for stateless re-execution, and how it differs from a proof (including a comparison table).

Documents Zesu’s current witness-fetching approach via Besu’s debug_executionWitness RPC (via besu-zkevm-plugin) and adds frontmatter metadata (description, keywords) plus a top-level caution noting the spec/retrieval method are still in flux.

Reviewed by Cursor Bugbot for commit d33a8c9. Bugbot is set up for automated code reviews on this repo. Configure here.

Explains what an execution witness is, why Zesu needs one instead of
holding full chain state, the difference between a witness and a proof,
and how Zesu currently retrieves witnesses via the
debug_executionWitness RPC endpoint.

Includes a caution admonition noting the witness spec and retrieval
mechanism are under active development, and a note linking to the
execution-apis proposals for the longer-term Engine API delivery path.

Co-authored-by: Cursor <cursoragent@cursor.com>
@vercel

vercel Bot commented May 20, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
doc-zesu Ready Ready Preview, Comment May 20, 2026 6:20am

Request Review

@bgravenorst bgravenorst merged commit 92f5af7 into main May 20, 2026
8 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant