| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
📝 Walkthrough
WalkthroughAdds AWS KMS-backed ECDSA secp256k1 transaction signing to the rollup sender, including configuration, address validation, transaction integration, tests, documentation, and dependency wiring. The version tag is updated to v4.7.17. ChangesAWS KMS Signer Integration
Version Bump
Estimated code review effort: 4 (Complex) | ~60 minutes Sequence Diagram(s)sequenceDiagram
participant NewSender
participant NewTransactionSigner
participant kmsSigner
participant AWSKMS
NewSender->>NewTransactionSigner: context, AWS KMS config, chain ID
NewTransactionSigner->>kmsSigner: initialize signer
kmsSigner->>AWSKMS: GetPublicKey
AWSKMS-->>kmsSigner: DER SPKI public key
kmsSigner->>kmsSigner: derive and validate signer address
NewTransactionSigner->>kmsSigner: sign transaction
kmsSigner->>AWSKMS: Sign digest
AWSKMS-->>kmsSigner: DER ECDSA signature
kmsSigner-->>NewTransactionSigner: apply Ethereum signature
Possibly related PRs
Suggested labels: bump-version Suggested reviewers: kchangn, georgehao, johnsonjie 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
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. ❤️ ShareComment @coderabbitai help to get the list of available commands. |
Sorry, something went wrong.
Codecov Report❌ Patch coverage is 55.26316% with 68 lines in your changes missing coverage. Please review. @@ Coverage Diff @@
## develop #1808 +/- ##
===========================================
+ Coverage 35.44% 35.47% +0.02%
===========================================
Files 262 261 -1
Lines 22596 22642 +46
===========================================
+ Hits 8010 8032 +22
- Misses 13748 13764 +16
- Partials 838 846 +8
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness.
|
Sorry, something went wrong.
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)rollup/internal/controller/relayer/l2_relayer.go (1)226-228: 🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win
Log when the committed batch’s end chunk is missing.
If GetChunkByIndex returns nil, the gauge remains at zero without any diagnostic, defeating this initialization and potentially triggering a false commit-lag alert. Emit a warning for this inconsistent database state, or fail startup if it must be treated as fatal.
🤖 Prompt for AI AgentsVerify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@rollup/internal/controller/relayer/l2_relayer.go` around lines 226 - 228, Update the initialization flow around GetChunkByIndex and the endChunk check to emit a warning when endChunk is nil, including enough context to identify the missing committed batch end chunk; preserve the existing gauge update when endChunk is present.
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. Outside diff comments: In `@rollup/internal/controller/relayer/l2_relayer.go`: - Around line 226-228: Update the initialization flow around GetChunkByIndex and the endChunk check to emit a warning when endChunk is nil, including enough context to identify the missing committed batch end chunk; preserve the existing gauge update when endChunk is present.
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 27e150cf-14d6-464f-a016-a3e94905ca5c
📥 CommitsReviewing files that changed from the base of the PR and between 3a22fc9 and 58ebdeb.
📒 Files selected for processing (2)
Sorry, something went wrong.
There was a problem hiding this comment.
rollup/internal/controller/sender/transaction_signer.go (1)🤖 Prompt for all review comments with AI agents69-77: 📐 Maintainability & Code Quality | 🔵 Trivial | 🏗️ Heavy lift
Cover the NewTransactionSigner KMS branch directly.
The existing KMS test constructs TransactionSigner with kmsSigner: ks, so it bypasses this constructor path. Add a constructor-level test using an injectable KMS client/factory, or at least cover its validation/error paths, so regressions in initialization and address wiring are detected.
🤖 Prompt for AI AgentsVerify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@rollup/internal/controller/sender/transaction_signer.go` around lines 69 - 77, Add a direct test for the AWSKMSSignerType branch in NewTransactionSigner, using an injectable KMS client or factory to exercise newKMSSigner, initialization, and address wiring; if injection is unavailable, cover the constructor’s validation and error paths instead. Keep the existing TransactionSigner-based KMS test, but ensure the new test invokes NewTransactionSigner itself and verifies successful signer creation or the expected error.
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. Nitpick comments: In `@rollup/internal/controller/sender/transaction_signer.go`: - Around line 69-77: Add a direct test for the AWSKMSSignerType branch in NewTransactionSigner, using an injectable KMS client or factory to exercise newKMSSigner, initialization, and address wiring; if injection is unavailable, cover the constructor’s validation and error paths instead. Keep the existing TransactionSigner-based KMS test, but ensure the new test invokes NewTransactionSigner itself and verifies successful signer creation or the expected error.
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 6a9da4be-7519-46fa-85cb-39baa850226a
📥 CommitsReviewing files that changed from the base of the PR and between 58ebdeb and f8401ed.
📒 Files selected for processing (6)
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Purpose or design rationale of this PR
Adds a third signer_type, AWSKMS, alongside PrivateKey and RemoteSigner.
Deployment checklist
Summary by CodeRabbit
Summary by CodeRabbit
Release Notes
New Features
Bug Fixes
Documentation
Chores