Repository navigation
devnet-1: recover frame traffic and record Nimbus onboarding blocker - #10
Merged
Merged
Conversation
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.
Pin Spamoor to the tested
e9b66bebuild so bogota-devnet-1 keeps the upstream nonce fix and gains correct frame RPC decoding plus one pending transaction per sender (ethpandaops/spamoor#306). The existing scenario configuration and client endpoints are preserved. Regenerated the Helm values from Ansible.Use
ethpandaops/nimbus-eth1:bogota-devnet-1for Nimbus EL. Live onboarding is held: the tested8747b0e8image requires blob wrappers for non-blob frames, returnstxErrorInvalidBlob, and disconnects Geth on gossip. It imports the same transactions in blocks and reached matching finality, so this is a client pool/gossip blocker, not a Spamoor workaround. No new node is provisioned.The incident register records all findings, including the existing Besu stall. Nimbus reproduction data includes the rejected raw transaction, both clients' eventual receipts, source locations, test configuration and matching chain samples.
Validation: full Spamoor CI passes. The separate live canary verified 1,330 receipts in three minutes with no mismatches, missing receipts or submission warnings; sampled pending peaked at 51 with 100 wallets. The local 1,000 tx/block / 500-wallet run verified 9,475 receipts without mismatches or missing receipts, while preserving Nimbus errors. Helm lint/render and Ansible generation pass. The live canary is a short test, not a long soak; monitor the main scenario after rollout.