[Core Protocol] How to decode Optimism blob data? #881
Replies: 1 comment
-
|
Changed the category to Application Development: #882 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Did you check the documentation and specs?
Was there anything unclear or missing?
No response
Did you check for duplicate questions?
Similar Questions or Issues Found
There is a discussion for calldata, but not blobs: #98
There is this similar question but doesn't answer my question for how to decode the blobs: #627
No response
Please select the type of request
Steps to Reproduce
No response
Expected vs. Actual Behaviour
No response
Software Versions
No response
Operating System
No response
Hardware Resources
No response
Configuration Files, Startup Flags & Environment Variables
No response
Error Messages / Logs
No response
Feature Description
I'm trying to figure out the L1 tx (ie tx on Ethereum mainnet) that corresponds to my L2 tx (ie tx on Optimism). I understand txs are posted in batches, and so I need to find the batch that included the l2 tx hash. I'm thinking of doing this by correlating the time range my tx was submitted (not sure if there's a better way).
The part I'm stuck at now is how to decode the tx data from the raw blob data. How can I go about decoding the blob data? I don't see any tools either I can use
Purpose and Benefits
No response
Relevant Context or Examples
No response
Beta Was this translation helpful? Give feedback.
All reactions