We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When I search an L2 transaction hash that has already been relayed, I see a status "Status at index 0: Message is ready to be relayed"
This leads to some confusion when I'm not sure what the last message I relayed was (this requires checking finalized withdrawals on L1).
it would be helpful to have a status "This message was relayed in has: 0x.... on xyz date"
The text was updated successfully, but these errors were encountered:
Can you share an example tx hash so we can repro?
Sorry, something went wrong.
This one may be unique. It's a pre-Bedrock withdrawal that was relayed post-Bedrock: L2 Tx: https://optimistic.etherscan.io/tx/0x1fc22af4d0bf1a0358c1679b77aefb95bab09de1c153d98a5d5b2539d149c591 L1 Relay Tx: https://etherscan.io/tx/0x126e629f9235854e551f8a9bf22b186e2d12c2c68c07bffd65b0ccf41ad41752
Very odd - we'll get this triaged and investigate.
https://github.com/ethereum-optimism/ecopod/issues/335
No branches or pull requests
When I search an L2 transaction hash that has already been relayed, I see a status "Status at index 0: Message is ready to be relayed"
This leads to some confusion when I'm not sure what the last message I relayed was (this requires checking finalized withdrawals on L1).
it would be helpful to have a status "This message was relayed in has: 0x.... on xyz date"
The text was updated successfully, but these errors were encountered: