Format of peers.txt changes across testnets

[rootulp]

Problem

Some scripts downstream of this repo assume that peers.txt has trailing commas. Some scripts assume no trailing commas. Since this repo doesn't enforce a consistent format, it's not clear what scripts should assume.

networks/mocha-3/peers.txt

Lines 1 to 2 in 3758740

	[email protected]:26656,
	daf2cecee2bd7f1b3bf94839f993f807c6b15fbf@celestia-testnet-peer.itrocket.net:11656

contains trailing commas

networks/mocha-4/peers.txt

Lines 1 to 3 in 3758740

	[email protected]:26656
	43e9da043318a4ea0141259c17fcb06ecff816af@rpc-1.celestia.nodes.guru:43656
	f9e950870eccdb40e2386896d7b6a7687a103c99@rpc-2.celestia.nodes.guru:43656

does not.

Consequently, I expect a command in the docs https://docs.celestia.org/nodes/full-consensus-node/#setup-the-p2p-networks to fail because

sed -i.bak -e "s/^persistent_peers =./persistent_peers = "$PERSISTENT_PEERS"/" $HOME/.celestia-app/config/config.toml

assumes that there are trailing commas.

Proposal

Describe a format for peers.txt. Enforce it consistently for all peers.txt files. IMO no trailing commas.

[Bidon15]

Thanks again for the ping, we will take some homework at @celestiaorg/devops to make sure we have rules set and done in linter so folks are following the rules

[jcstein]

Due to celestiaorg/docs#1083 - I think it is best we pick one of these options and I will update docs accordingly from there:
(1) leave the standard without commas, implement a linter on this repo to enforce this
(2) make the standard with commas, and implement a linter on this repo that enforces this

[jcstein]

note: docs currently have the sed commands set to assume there are no commas in the peers.txt or seeds.txt files

[jcstein]

related comment regarding port formatting in seeds.txt and peers.txt