-
Notifications
You must be signed in to change notification settings - Fork 201
[Feature] Encodable and Decodable for Signature
#938
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
Comments
I can do that if maintainers allow it |
those were removed to avoid footguns as encoding for signatures may differ depending on context (e.g legacy and non-legacy transactions are using different rlp) |
yeah Signature encoding depends on the transaction type, there is e.g. |
makes sense, thanks for the answer! |
leaving this as reference:
|
Component
primitives
Describe the feature you would like
The
alloy_rlp::Encodable
andalloy_rlp::Decodable
implementations were removed in this commit. I propose to reintroduce the implementations behind therlp
flag as was done before.Additional context
No response
The text was updated successfully, but these errors were encountered: