Have a csv for peernodes

[okwme]

Previously here: https://github.com/cosmos/registry/issues/7

This would be to take the contents of the peernodes section of the JSON and put it into a place that is easy to copy and paste into a config file for node operators.

Alternatively (or in addition) this could be a github action that generated a markdown file like this: https://github.com/osmosis-labs/networks/blob/main/peers.md or https://hackmd.io/@KFEZk8oMTz6vBlwADz0M4A/BkKEUOsZu#

[sunnya97]

Here's the jq command to get the seeds from the json in a single string

cat {chain.json} | jq -r '.peers.seeds | map(.id + "@" + .address) | join(",")'

[ValarDragon]

I think the markdown as an intermediate step should be eliminated (its need feels removed by this), up to access control issues.

Fully agreed we should make an easy way for these peers to be easy to get copy/pasted for node operators. Maybe we make an auto-generated addrbook file, or one-line copy pastable string in the repo?

Ideally we can also have repos have a copy of their own chain.json kept somehow in sync with the one here, and ship with the same default seeds.

[vlamitin]

jq is good, and we can also have a github.io (github pages) html page with some JavaScript to dynamycally format seeds from chain.json to whatever format