Quicksilver

type:

mainnet

chain id:

quicksilver-2

rpc:

https://rpc.quicksilver.citizenweb3.com

rest:

https://api.quicksilver.citizenweb3.com

grpc:

https://grpc.quicksilver.citizenweb3.com

grpcweb:

https://grpcweb.quicksilver.citizenweb3.com

seed/peer:

719ddc260d5bbd17a7c6ed4219bdbad60d423d96@mainnet.seednode.citizenweb3.com:28656

peers
snapshot
public goods
relayers

Live Peers for Quicksilver

Add this peers, from the registry, to your config.toml:


[email protected]:25656,[email protected]:11156,[email protected]:11156,[email protected]:11156,ebc272824924ea1a27ea3183dd0b9ba713494f83@quicksilver-mainnet-seed.autostake.com:27026,[email protected]:26656,400f3d9e30b69e78a7fb891f60d76fa3c73f0ecc@quicksilver.rpc.kjnodes.com:11159,a85a651a3cf1746694560c5b6f76d566c04ca581@quicksilver-seed.takeshi.team:10456,559e316b30830ddd5e93617592ef70330ecce86d@seed-quicksilver.ibs.team:16668,[email protected]:27656,20783f43c3b574e9020d22be3415f8a545f0617f@seed.quicksilver.validatus.com:4000

Update persistent_peers setting in config.toml. Stale peers can cause node inefficiency over time. This script selects up to 5 random live peers:


PEERS=ebc272824924ea1a27ea3183dd0b9ba713494f83@quicksilver-mainnet-peer.autostake.com:27026,3461638afd470034067392e5dba8dcf6de49f81f@rpc.quicksilver.indonode.net:28656,[email protected]:16656,[email protected]:21026,[email protected]:31126,[email protected]:26656,8200b77d075f2634e6f9dab11fd56726a2e6d75b@quicksilver-seed.theamsolutions.info:31656,82b49e6cc0826642e745b7a7a621aecbf8083af7@peer-quicksilver.mms.team:56103,[email protected]:50656,66a0cd5eff87ec7b1ea2e3b41032c1c2d22aa284@mainnet-quicksilver.konsortech.xyz:46657
sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \"$PEERS\"/" $HOME/.quicksilverd/config/config.toml

Add Citizen Web3 state-sync peer to persistent_peers in config.toml:


<seed-node>