Updates documentation on how to run a full node #175
Merged
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 ↗︎
|
BrendanChou
reviewed
Apr 29, 2024
jiajames
approved these changes
May 2, 2024
| 1. From https://github.com/dydxprotocol/v4-chain/releases/ | Look for the `protocol` assets. | ||
| 2. For example, as of `10/19/2023`, this was the correct binary to use: | ||
|
|
||
| 2. For example, as of `04/26/2024`, this was the correct binary to use: |
There was a problem hiding this comment.
Can we provide instructions on how to figure out which version to use at any given time?
|  | ||
| 3. Download, extract, and rename the binary to `dydxprotocold`. Move it to a directory in your `$PATH`. Now, initialize the data directory (create the directory first if it doesn’t exist). | ||
| 3. Download, extract, and rename the binary to `dydxprotocold`. Move it to a directory in your `$PATH`. Now, initialize the dydx home directory (create the directory first if it doesn’t exist). | ||
| ```bash | ||
| CHAIN_ID=dydx-mainnet-1 |
There was a problem hiding this comment.
CHAIN_ID=dydx-testnet-4 # or dydx-mainnet-1 for the deployment by DYDX token holders
| DYDX_HOME=/home/vmware/.dydx-mainnet-1 | ||
| sudo tee /etc/systemd/system/dydxprotocold.service > /dev/null << EOF | ||
| [Unit] | ||
| Description=osmosis node service |
There was a problem hiding this comment.
nit: dydxprotocol node service
Comment on lines
115
to
117
| ```bash | ||
| sudo systemctl start dydxprotocold | ||
| ``` |
There was a problem hiding this comment.
also add command on how to stop the service
| ``` | ||
| 3. The full node is now syncing. To determine whether the full node is caught up with the chain head, please check the applicable block explorer to determine when it reaches the current block – an example block explorer is shown on https://www.mintscan.io/dydx | ||
| The full node is now syncing. To determine whether the full node is caught up with the chain head, please check the applicable block explorer to determine when it reaches the current block – an example block explorer is shown on https://www.mintscan.io/dydx |
There was a problem hiding this comment.
I would also add a small section on different interesting queries you can run. for ex, command to see how much the node has synced rather than parsing through logs
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.
Updating documentation on full node setup to include cosmovisor being included in