Move migrate state from classic to node running and autogenerate node running how-tos #658
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
symbolpunk
reviewed
Oct 10, 2023
| sidebar_position: 10 | ||
| --- | ||
|
|
||
| When running a Nitro node for the first time on a chain that produced [classic blocks](/for-devs/concepts/public-chains#classic-deprecated) in the past (like Arbitrum One), you need to initialize its database to, at least, the state of the chain after executing the last classic block. The common, and recommended, way of doing that is to provide a database snapshot using the `--init.url` option (as mentioned in [How to run a full node (Nitro)](/node-running/how-tos/running-a-full-node.mdx)). In this how-to we show you an alternative way for doing that, migrating the state and history of the chain from a fully synced classic node. |
symbolpunk
reviewed
Oct 10, 2023
arbitrum-docs/node-running/how-tos/migrate-state-and-history-from-classic.mdx
Outdated
Show resolved
Hide resolved
symbolpunk
reviewed
Oct 10, 2023
arbitrum-docs/node-running/how-tos/migrate-state-and-history-from-classic.mdx
Outdated
Show resolved
Hide resolved
mahsamoosavi
requested changes
Oct 10, 2023
|
|
||
| ### Block & transaction history | ||
|
|
||
| These are block-headers, transactions and receipts executed in the classic node. Nitro node uses the history to be able to answer simple requests, like `eth_getTransactionReceipt`, from the classic history. The last block in the chain is the only one that affects the genesis block: timestamp is copied from the last block, and parentHash is taken from the last block's blockHash. |
There was a problem hiding this comment.
Suggested change
| These are block-headers, transactions and receipts executed in the classic node. Nitro node uses the history to be able to answer simple requests, like `eth_getTransactionReceipt`, from the classic history. The last block in the chain is the only one that affects the genesis block: timestamp is copied from the last block, and parentHash is taken from the last block's blockHash. | |
| These are block headers, transactions and receipts executed in the classic node. Nitro node uses the history to be able to answer simple requests, like `eth_getTransactionReceipt`, from the classic history. The last block in the chain is the only one that affects the genesis block: timestamp is copied from the last block, and parentHash is taken from the last block's blockHash. |
I think?
|
|
||
| ### Outbox messages (optional) | ||
|
|
||
| This data does not impact consensus and is optional. It allows a Nitro node to provide the information required when redeeming a withdrawal made on the classic rollup. |
There was a problem hiding this comment.
should we use the word executing rather than redeeming?
|
|
||
| :::caution Caution | ||
|
|
||
| This state import operation requires more resources than a regular run of a nitro node. |
There was a problem hiding this comment.
Suggested change
| This state import operation requires more resources than a regular run of a nitro node. | |
| This state import operation requires more resources than a regular run of a Nitro node. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is part of the clean-up process of the "Ethereum vs Arbitrum" + "Classic vs Nitro" sections, and does two main things:
Redirections have been set for the two relocated files.