revised running a node #476
Conversation
|
Your Render PR Server URL is https://docs-pr-476.onrender.com. Follow its progress at https://dashboard.render.com/static/srv-bth8ppf93em2ahr0ar30. |
|
|
||
| You may decide to run a node of your own for a few reasons: | ||
|
|
||
| - To view, process, and validate transactions on `MainNet`, `TestNet` or `BetaNet` (†) |
There was a problem hiding this comment.
I think some reasons for running a regular node include:
- serve rpc for your own use cases. This includes transaction submission, queries, view calls etc.
- to index data from the network (running indexer on top of it for example)
docs/concepts/nodes.md
Outdated
| <blockquote class="warning"> | ||
| <strong>Note</strong><br><br> | ||
|
|
||
| Non-block producing nodes still validate every block and are very important to the network. This network of nodes, that view all transactions taking place, help us to be certain that the chain is correct and no invalid state transitions / forks are occurring. |
There was a problem hiding this comment.
Before we have challenges, non block producing nodes cannot really prevent invalid state transition from happening. Even with challenges you have to become a fisherman to challenge.
There was a problem hiding this comment.
I should clarify that this is referring to raising alarms within the community, not actually preventing realtime issues.
| _( † ) `TestNet` is intended to operate as closely (similarly) to `MainNet` as possible with only stable releases while `BetaNet` follows a weekly release cycle._ | ||
| 4) Run the following command replacing the paths & networkId: | ||
| ```bash | ||
| neard --home=<absolute_path_to_the_desired_location> init --chain-id=<networkId> --genesis=<absolute_path_to_the_downloaded_genesis_file> |
There was a problem hiding this comment.
--genesis argument only applies to betanet and testnet. For mainnet, genesis is built into the binary
There was a problem hiding this comment.
This PR was to add running a node without using nearup to this document. Existing instructions on running nearup were not checked for accuracy. Thank you for the update.
| ```bash | ||
| nearup betanet --nodocker --binary-path path/to/nearcore/target/release | ||
| nearup betanet --nodocker --binary-path <path_to_nearcore_target_release> |
There was a problem hiding this comment.
this is outdated. The new version of nearup doesn't have an option to run docker inside. You can run the entire nearup from docker. https://github.com/near/nearup/tree/nearup_v2
There was a problem hiding this comment.
Same as above... existing instructions on nearup were not checked for accuracy. I will carve out some time to run through them and update.
|
|
||
| ```text | ||
| Enter your account ID (leave empty if not going to be a validator): | ||
| Enter your account ID: (leave empty if not going to be a validator) |
There was a problem hiding this comment.
this doesn't exists any more, you have to pass the flag --account-id
|
|
||
|
|
||
| ### Block producing node ("validator node") | ||
| ### Producing node ("validator node") |
There was a problem hiding this comment.
Why? Producing node makes no sense
There was a problem hiding this comment.
This was discussed in a thread on slack. @SkidanovAlex was concerned that calling a node "block producing" would be incorrect in the future when chunk producing begins. Do you have a suggestion?
There was a problem hiding this comment.
No but let's not call them "producing node". For now block producing node is fine
|
closed this stale PR as #739 was recently merged covering this topic. |
nearuprunning-testnet.mdtorunning-a-node.mdto reflect its actual contentrunning-a-node.mdnodes.mdunder/docs/conceptsand moved information about nodes into it fromrunning-a-node.mdnodes.mdfixes near/node-docs#8