In anticipation of RCNET launch, we need YOU to join our testnet.
What we need :
A group of community members to step through the process of setting & running a node for a limited time.
Why do we need it ?
To find any issues with our documentation
Uncover and undiscovered technical issues
How to join :
Spin up a server -
If you need hosting use digitalocean.com / vultr.com / hetzner.com (or any other provider).
Server must be AMD64 / INTEL86x architecture.
Just to be dificult i set it up on a Almalinux 9 instance… not much different in terms of install, only thing is docker is installed using dnf as the bash file won’t support Almalinux, docker-compose is the same in my instance i’m using version 2.12.2 not 1.29.2 as per your document.
Only think now is the log is incomatible peers (expecting testnet-5 getting testnet-6)
1|cometbft | I[2024-09-06|04:45:02.253] Saving AddrBook to file module=p2p book=/root/.cometbft/config/addrbook.json size=0
1|cometbft | I[2024-09-06|04:45:02.267] Ensure peers module=pex numOutPeers=0 numInPeers=0 numDialing=0 numToDial=10
1|cometbft | I[2024-09-06|04:45:02.273] No addresses to dial. Falling back to seeds module=pex
1|cometbft | E[2024-09-06|04:45:02.284] Error dialing seed module=p2p err="incompatible: peer is on a different network. Got xian-testnet-6, expected xian-testnet-5" [email protected]:26656
1|cometbft | E[2024-09-06|04:45:02.284] Couldn't connect to any seeds module=p2p
Just editting this post with more info:
I updated the testnet.json to use testnet-6, removed .cometbtf deleted the containers and re-run the build because i like testing stuff. Its no longer getting those errors in the cometbft log file.
Thanks to all who stepped through the process of setting up a node - it was a valuable help ironing out any setup issues along the way. Stay tuned for info on joining RCNet.