Skip to content

Support EIP-8025 zkboost - #2705

Draft
yorickdowne wants to merge 1 commit into
ethstaker:mainfrom
yorickdowne:support-zkboost
Draft

yorickdowne wants to merge 1 commit into
ethstaker:mainfrom
yorickdowne:support-zkboost

Conversation

@yorickdowne

@yorickdowne yorickdowne commented Jul 13, 2026 •

Copy link
Copy Markdown
Collaborator

What I did

  • Support EIP-8025 zkboost optional proofs with experimental Lighthouse build
  • Remove previous zk experiment

@yorickdowne
yorickdowne requested a review from pietjepuk2 July 13, 2026 08:27
@yorickdowne
yorickdowne force-pushed the support-zkboost branch 2 times, most recently from 6c0259c to b3bda0b Compare July 13, 2026 08:31
@yorickdowne

Copy link
Copy Markdown
Collaborator Author

Open question: Are there mainnet bootnodes that deliver proofs via P2P?

@yorickdowne

yorickdowne commented Jul 13, 2026 •

Copy link
Copy Markdown
Collaborator Author

"ideally CL would verify the proof locally without zkboost" - eventually come Hegotá time this may all be ripped out again. For now it's useful for testing.

@yorickdowne
yorickdowne marked this pull request as draft July 19, 2026 18:11
@yorickdowne
yorickdowne force-pushed the support-zkboost branch 2 times, most recently from 10212e5 to 062de76 Compare July 19, 2026 18:54
@yorickdowne

Copy link
Copy Markdown
Collaborator Author

In draft for now. There are no mainnet P2P nodes to test this with, and the verifier functionality might move into the client itself

@yorickdowne

Copy link
Copy Markdown
Collaborator Author

Lighthouse will add this into the client itself. Also it’ll seed proofs to P2P. At that point I can create a fresh PR from this one, adjust to using Lighthouse without a zkProof sidecar, and close this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant