This repository has been archived by the owner on Apr 13, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 299
Checking if a new node is valid
Javier Aguirre edited this page May 27, 2020
·
6 revisions
- Check if the new node appears on netstats:
- Is red, has 0 peers.
- Is the IP public
- Is located in Europe within the map (execute command: whois -h whois.ripe.net node-ip)
- Node IDENTITY and geth/quorum versions are correct
- (OPTIONAL) Verify constellation-nodes.json is valid JSON (You can check it on https://jsonlint.com).
- Verify regular-nodes.json is valid JSON (You can check it on https://jsonlint.com).
- Verify validator-nodes.json is valid JSON (You can check it on https://jsonlint.com).
- Verify DIRECTORY_REGULAR.md:
- enode and ip are the same as the enode added in constellation-nodes.json and in regular-nodes.json.
- Contact name and email are correct.
- Ask for administrative verification.
- If necesary resolve conflicts and merge.
- Update at least one bootnode.
- Go to netstats and check that the added node(s) have peers and have synchronized.
1. How to set up:
- A regular node in Red T using Docker
- A validator node in Red T using Docker
- A bootnode in Red T using Docker
- Private Smart Contracts in Red T
- Deployment of Smart Contracts in Red T
2. F.A.Q.
3. Netstats and Block explorers