Skip to content

fix(bb-prover): replace a dead pooled bb verifier (port aztec-labs-eng/aztec-node#354 to v6) - #25590

Closed
charlielye wants to merge 1 commit into
v6from
cl/port-aztec-node-354-to-v6
Closed

charlielye wants to merge 1 commit into
v6from
cl/port-aztec-node-354-to-v6

Conversation

@charlielye

Copy link
Copy Markdown
Contributor

Ports aztec-labs-eng/aztec-node#354 to v6 as a labs patch, labs-patches/0011-….

#354 fixes the RPC proof verifier's pool. When a pooled bb died, the pool kept handing out the dead handle for the life of the node, and verifyProof reported the failure as { valid: false }, so valid transactions were rejected as having invalid proofs until restart. With the fix:

  • A pooled instance replaces its own bb process when it dies, using bb.js's respawn.
  • A verification whose bb died or could not start is retried once, then fails as ProofVerifierUnavailableError instead of as an invalid proof.
  • The pool is a queue of slots, each starting its bb on first use.

The bb.js half it relies on, #25548, is already on v6 via the rolling port in #25565. v6 builds labs against its own bb.js, so no pin change is needed.

How

labs stays at a0d73c0aed. #354's squash commit (aztec-labs-eng/aztec-node@8556dfb6a6) is cherry-picked onto the existing series and exported, with no conflicts. The existing patches 0001 and 0010 are unchanged; the new one is numbered 0011 so it sorts after them.

The patch drops out at the next labs bump past aztec-node main at 8556dfb6a6.

Verification

🤖 Generated with Claude Code

https://claude.ai/code/session_01NuUzj3qpkpJor6GMpWB4T4

…g/aztec-node#354 to v6)

Carries aztec-labs-eng/aztec-node#354 as a labs patch on v6. The bb.js side it
relies on, #25548, is already on v6 via the rolling port in #25565.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NuUzj3qpkpJor6GMpWB4T4
@charlielye charlielye closed this Oct 5, 2026
@charlielye
charlielye deleted the cl/port-aztec-node-354-to-v6 branch October 5, 2026 10:54
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