docs: Add "Mastering Cross-Chain State" Deep Dive to Cookbook #789
Conversation
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
This PR adds a production-grade guide to handling cross-chain state on Base. It addresses high-frequency developer/user confusion regarding bridge delays and address derivation. ### Key Additions * **Visualizing the 7-Day Challenge:** A detailed timeline breakdown of the Optimistic Rollup withdrawal process (Initiate -> Prove -> Finalize). * **Bridge Architecture Comparison:** A decision matrix for developers choosing between Native (Canonical) and Third-Party (Liquidity) bridges. * **The "Stuck Funds" Recovery Protocol:** A technical guide to recovering assets sent to mismatched addresses, distinguishing between EOA (simple) and Smart Contract (CREATE/CREATE2) recovery paths. ### File Changes * 🆕 Created: `apps/base-docs/docs/cookbook/mastering-cross-chain-state.mdx` ### Checklist - [x] Technical examples (Nonce Replay, CREATE2) verified for accuracy. - [x] Tone is educational yet authoritative. - [x] Frontmatter included.
Collaborator
🟡 Heimdall Review Status
|
Removed the guidelines section to streamline the document.
This PR adds a production-grade guide to handling cross-chain state on Base. It addresses high-frequency developer/user confusion regarding bridge delays and address derivation. ### Key Additions * **Visualizing the 7-Day Challenge:** A detailed timeline breakdown of the Optimistic Rollup withdrawal process (Initiate -> Prove -> Finalize). * **Bridge Architecture Comparison:** A decision matrix for developers choosing between Native (Canonical) and Third-Party (Liquidity) bridges. * **The "Stuck Funds" Recovery Protocol:** A technical guide to recovering assets sent to mismatched addresses, distinguishing between EOA (simple) and Smart Contract (CREATE/CREATE2) recovery paths. ### File Changes * 🆕 Created: `apps/base-docs/docs/cookbook/mastering-cross-chain-state.mdx` ### Checklist - [x] Technical examples (Nonce Replay, CREATE2) verified for accuracy. - [x] Tone is educational yet authoritative. - [x] Frontmatter included.
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.
This PR adds a production-grade guide to handling cross-chain state on Base. It addresses high-frequency developer/user confusion regarding bridge delays and address derivation.
Key Additions
File Changes
apps/base-docs/docs/cookbook/mastering-cross-chain-state.mdxChecklist
What changed? Why?
Notes to reviewers
How has it been tested?