-
Notifications
You must be signed in to change notification settings - Fork 110
refactor(builder): replace custom Signer with Alloy's PrivateKeySigner #426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
🟡 Heimdall Review Status
|
| >, | ||
| ) -> Self { | ||
| let base_builder_tx = BuilderTxBase::new(Some(signer)); | ||
| let base_builder_tx = BuilderTxBase::new(Some(signer.clone())); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a huge fan of the .clone()s but it's not a big deal.
refcell
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me, would appreciate a second pair of eyes though.
refcell
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove clones
|
Review Error for refcell @ 2026-01-13 23:09:39 UTC |
Replace the custom secp256k1-based Signer implementation with Alloy's PrivateKeySigner. This simplifies the codebase by reusing well-tested cryptographic primitives from the alloy-signer crate. Changes: - Wrap PrivateKeySigner in Signer struct with cached address field - Update sign_message to use SignerSync::sign_hash_sync - Update sign_tx to use eyre::Result instead of secp256k1::Error - Remove secp256k1 direct dependencies from tx_signer module - Update test files to use .clone() where Signer is moved Closes base#390
1bd7a11 to
06fee44
Compare
Closes #390