-
Notifications
You must be signed in to change notification settings - Fork 199
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
[Feature] encodable/decodable for Signed transaction #398
Comments
@prestwich I think what we want is alloy/crates/eips/src/eip2718.rs Line 124 in f7333c4
for we could either do this manually for all alloy/crates/consensus/src/transaction/envelope.rs Lines 230 to 243 in f7333c4
part of a trait, so we can do: alloy/crates/consensus/src/signed.rs Line 34 in f7333c4
|
You can do this by wrapping it in an envelope ( |
It was removed, because it is often incorrect to use it, in a way that is not obvious to users. If people are asking for it, we should push them towards |
Hmmm, okay! I'll take a look into the TxEnvelope |
Component
consensus, eips, genesis
Describe the feature you would like
alloy-consensus:
e.g: usual TxEip4844 implements Encodable/Decodable
But Signed doesn't
we should have the ability to encode/decode Signed transactions directly
Additional context
e.g at this moment we can't do this:
alloy/crates/consensus/src/signed.rs
Line 6 in f7333c4
we want the Encodable2718 trait, impl in TxEnvelope:
alloy/crates/consensus/src/transaction/envelope.rs
Line 216 in f7333c4
The text was updated successfully, but these errors were encountered: