Each week we invite community members to help test RNode.
This is a testing and educational session! We'll start by making sure everyone knows how to pull and add their RNode log to a Jira ticket. Then we'll perform a genesis ceremony to launch a network and debug from there.
Note If you used a previous version of RNode, please delete your existing .rnode directory. Most errors experienced using RNode relate to content in the directory from a previous version.
Today's version RChain Node 0.7.1 (fdf07ff25083152beda9a6a7b22f1c4350f3d7d0)
Binary packages (.deb, .rpm, and .tgz) https://repo.pyr8.io/rchain/downloads/testing/
Docker image
Docker pull rchain/rnode:testing |
Go to https://docs.google.com/spreadsheets/d/18merD3OzaDk7nmxQ78SUZBzWLbxA-aOnmcdxpXrp_U0/edit#gid=0
Pick out a an unclaimed row with a validator key pair
Specify your node if you want. You can wipe your information after testing
Blog on the ceremony at a conceptual level https://www.rchain.coop/blog/rchain-testnet-genesis-ceremony/
We'll work off instructions shown on the Genesis protocol guide
Unless you specified another location, your RNode log file is in .rnode/rnode.log
You best support the improvement and development of the RChain platform when you file a bug to report challenge you faced or unsuccessful outcomes. This will help us collect all relevant information to better understand your setup and experience.
Testing session summary
Instructions on pulling rnode log to support filing bugs. Instructions on key generation. Genesis ceremony. Issues related to networking since bootstrap's 40404 port wasn't open, and issue related to block passing from bootstrap to peers.