refactor(engine-api): remove engine_appendBatchSignature and BatchSignature#105
refactor(engine-api): remove engine_appendBatchSignature and BatchSignature#105
Conversation
…nature The consensus layer (tendermint/morphnode) no longer calls engine_appendBatchSignature after the batch generation is moved out of the consensus path to the tx-submitter. Remove the no-op stub and its associated BatchSignature type. Corresponds to morph-l2/go-ethereum#319, morph-l2/tendermint#35, and morph-l2/morph#939.
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis PR removes the batch signature feature from the Engine API, eliminating the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Review rate limit: 0/1 reviews remaining, refill in 56 minutes and 57 seconds.Comment |
Summary
Remove the
engine_appendBatchSignatureRPC stub and theBatchSignaturetype. The consensus layer (tendermint / morphnode) no longer calls this method after batch generation is moved out of the consensus path to thetx-submitter.Cross-repo coordination
This PR is the morph-reth counterpart of:
NewL2Blockbatch hashScope
morph-reth only ever carried a no-op stub for
engine_appendBatchSignature(added in #93 to prevent morphnode's retry loop from hanging the tendermint goroutine). morph-reth never implemented the geth-side batch write paths (CommitBatch,RollupBatchDB accessors,batch.Handlerlifecycle), so there is no equivalent cleanup needed here — only the stub goes away.batch_hashwas already removed fromMorphHeaderin #31, andnewL2Blockalready has nobatchHashparameter in reth.Changes
append_batch_signaturedefault method fromMorphL2EngineApitrait (crates/engine-api/src/api.rs)append_batch_signaturemethod fromMorphL2EngineRpctrait +MorphL2EngineRpcHandlerimpl (crates/engine-api/src/rpc.rs)BatchSignaturestruct (crates/payload/types/src/params.rs)BatchSignaturere-export (crates/payload/types/src/lib.rs)engine_appendBatchSignaturerow from README Engine API tableNet diff: 5 files, +4 / -68.
Deployment ordering
This PR should land together with (or after) the coordinated PRs in go-ethereum / tendermint / morph. Running a newer morph-reth without the
engine_appendBatchSignatureendpoint against an older morphnode that still calls it would trigger the same "Method not found" retry storm that #93 originally fixed.Test plan
cargo check --workspacecargo clippy --all --all-targets -- -D warningscargo nextest run --workspaceSummary by CodeRabbit
appendBatchSignatureAPI method from the Engine API along with its type definitions and JSON-RPC endpoint.