Checking if a new node is valid

1. 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

2. (OPTIONAL) Verify constellation-nodes.json:
   • Last enode has no comma at the end
   • and the penultimate enode has comma at the end.
3. Verify regular-nodes.json:
   • Every row has a comma at the end.

• No empty row in the file (neither in the middle or at the end)

4. 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.
5. Ask for administrative verification.
6. If necesary resolve conflicts and merge.
7. Update at least one bootnode.
8. Go to netstats and check that the added node(s) have peers and have synchronized. Validator
9. Check if the new node appears on netstats:

• Is red, has 0 peers.
  • Is located in Europe within the map (execute command: whois -h whois.ripe.net node-ip)
• Node IDENTITY and geth/quorum versions are correct

2. (OPTIONAL) Verify constellation-nodes.json:
   • Last enode has no comma at the end
   • and the penultimate enode has comma at the end.
3. Verify validator-nodes.json:
   • Every row has a comma at the end.

• No empty row in the file (neither in the middle or at the end)

4. Verify DIRECTORY_VALIDATOR.md:
   • enode and ip are the same as the enode added in constellation-nodes.json and in validator-nodes.json.
   • Contact name and email are correct.
5. Ask for administrative verification.
6. If necesary resolve conflicts and merge.
7. Update at least one bootnode.
8. Go to netstats and check that the added node(s) have peers and have synchronized. Bootnode
9. Check if the new node appears on netstats:

• Is red, has 0 peers.
• Is located in Europe within the map (execute command: whois -h whois.ripe.net node-ip)
• Node IDENTITY and geth/quorum versions are correct

2. Verify boot-nodes.json:
   • Every row has a comma at the end.

• No empty row in the file (neither in the middle or at the end)

3. Verify DIRECTORY_BOOTNODES.md:
   • enode and ip are the same as the enode added in boot-nodes.json.
   • Contact name and email are correct.
4. Ask for administrative verification.
5. If necesary resolve conflicts and merge.
6. Update at least one bootnode.
7. Go to netstats and check that the added node(s) have peers and have synchronized.