docs: add withdrawal lifecycle monitoring guide - #3489
Open
Gowtham118 wants to merge 3 commits into
Open
Conversation
Adds a developer-facing how-to for chain operators and integration partners to monitor child-to-parent withdrawals programmatically: lifecycle stages mapped to bridge UI phases and SDK statuses, expected timelines per chain type, the L3 two-leg case with delay-reduction options, tested @arbitrum/sdk and raw contract snippets, a stuck- withdrawal diagnosis table, and a historical data availability caveat. All code snippets were run end to end against a local nitro-testnode (BoLD rollup) and technical claims verified against nitro/nitro-contracts sources and live mainnet contracts. Closes TW-771 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
pete-vielhaber
left a comment
pete-vielhaber
left a comment
Contributor
There was a problem hiding this comment.
Added minor nits; quicklooks. Will wait for SME review before signoff.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a developer-facing how-to for chain operators and integration partners to monitor child-to-parent withdrawals programmatically: lifecycle stages mapped to bridge UI phases and SDK statuses, expected timelines per chain type, the L3 two-leg case with delay-reduction options, tested @arbitrum/sdk and raw contract snippets, a stuck- withdrawal diagnosis table, and a historical data availability caveat.
All code snippets were run end to end against a local nitro-testnode (BoLD rollup) and technical claims verified against nitro/nitro-contracts sources and live mainnet contracts.
Closes TW-771
Thank you for contributing to our docs!
Please fill out the form below to ensure your doc gets quickly approved and merged.
Description
Document type
Checklist
yarn startoryarn buildAdditional Notes