Skip to content
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

Add example of moving across TX types / RLP serialization #86

Open
Tracked by #87
zerosnacks opened this issue May 30, 2024 · 0 comments
Open
Tracked by #87

Add example of moving across TX types / RLP serialization #86

zerosnacks opened this issue May 30, 2024 · 0 comments
Labels
advanced enhancement New feature or request

Comments

@zerosnacks
Copy link
Member

zerosnacks commented May 30, 2024

Add example of moving across the different TX types / RLP serialization for usage in i.e. Flashbots

From Telegram / Discord:

How can I go from a TxEnvelope to a more usable one like alloy_rpc_types::Transaction or similar? AFAIK TxEnvelope is the only type we're supposed to use when RLP decoding raw bytes

Users may want to serialize their things as RLP for usage in flashbots where they put a signed rlp transactions behind a txhash

regular users should only interact with TransactionRequest and TransactionEnvelope. they should never RLP anything

you should never decode raw rlp bytes, you should decode raw 2718 bytes. going from TxEnvelope to rpc::Transaction is not possible because rpc::Transaction contains more information

@zerosnacks zerosnacks added the enhancement New feature or request label May 30, 2024
@yash-atreya yash-atreya added this to the 0.1-rc.0 milestone Jun 5, 2024
@zerosnacks zerosnacks removed this from the 0.1-rc.0 milestone Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
advanced enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants