Network nodes - RPC & Archive #228
Draft
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
augustocollado
added
A1 - Maintenance Major
albertov19
reviewed
Jan 21, 2025
| --state-pruning=archive \ | ||
| --blocks-pruning=archive \ | ||
| --database=paritydb \ | ||
| --unsafe-rpc-external \ |
There was a problem hiding this comment.
Normally we don't recommend --unsafe-rpc-external or is this a flag that OpsLayer confirmed can be used? I think this is not a great security practice, so if we were to add this it should be under a note or a warning.
There was a problem hiding this comment.
It's a flag opslayer is actually using on stagelight. Atm, we only have a line explaining what it is for, but I'll also add a warning
albertov19
requested changes
Jan 21, 2025
| @@ -129,21 +129,18 @@ docker run -ti moondancelabs/dancebox-container-chain-evm-templates \ | |||
| --name=para \ | |||
| --state-pruning=archive \ | |||
| --blocks-pruning=archive \ | |||
| --database=paritydb \ | |||
| --unsafe-rpc-external \ | |||
There was a problem hiding this comment.
Same comment with unsafe-rpc-external
ernestosperanza
approved these changes
Feb 25, 2025
| @@ -160,7 +157,7 @@ docker run -ti moondancelabs/dancebox-container-chain-evm-templates \ | |||
|
|
|||
| ## Syncing Your Node {: #syncing-your-node } | |||
|
|
|||
| Once your node spins up, the syncing process displays lots of log information from the node configuration, the relay chain, and the node itself. Some errors are expected to be displayed at the beginning of the process, disappearing once the chain gets synced to the last block. | |||
| Once your node spins up, the syncing process displays lots of log information from the node itself and the Tanssi network. Some errors are expected to be displayed at the beginning of the process, disappearing once the chain gets synced to the last block. | |||
There was a problem hiding this comment.
Suggested change
| Once your node spins up, the syncing process displays lots of log information from the node itself and the Tanssi network. Some errors are expected to be displayed at the beginning of the process, disappearing once the chain gets synced to the last block. | |
| Once your node spins up, the syncing process displays a lot of log information from both the node and the Tanssi network. Some errors are expected to be displayed at the beginning of the process, disappearing once the chain gets synced to the last block. |
0xlukem
reviewed
Mar 11, 2025
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.
Description
This PR updates wording.
It's a draft, as it still needs a live testnet to update and test the instructions (chain specs, bootnodes, etc) against.
Checklist
tanssi-mkdocsto update redirects