Each week we invite community members to help test RNode.
Updated 12:52 UTC This we we plan to test bug fixes and new features. We previously mentioned a plan to test validator bonding. Due to a late-breaking bug, this will be postponed until next week.
Prepare to participate
We will not be working on the RChain test net. To participate in this session, please see instructions below.
Note If you used a previous version of RNode, please delete your existing .rnode directory. Most errors experienced using RNode v0.6.1 relate to content in the directory from a previous version.
Please install RNode prior to the start of the testing session. If you have run RNode previously please see and for support for resolving issues you may experience preventing the successful running of RNode today.
Updated 12:52 UTC We will use RChain Node 0.6.4 (5d620e25b42f328d046cf4b1596446be7f55fe9d)
Binary packages (.deb, .rpm, and .tgz) https://repo.pyr8.io/rchain/downloads/testing/
Docker image
docker pull rchain/rnode:testing |
Updated 12:52 UTC Connect to the network via the RChain testing bootstrap node shown on RNode bootstrap addresses.
NOTE the format of the bootstrap address changed. The new format is in dev and will move to other supported bootstrap nodes over the next few weeks. Please see RNode bootstrap addresses for more information.
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
Now that you have your bootstrap address and validator key, you can run RNode. If you need more information, please see User guide for running RNode for running instructions.
New You can now check your version of RNode via the gRPC server.
curl -s localhost:40403/version |
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
43 participants. A network of 27 peers. Observed improvements with bug fixes and new features. Bugs and feature requests filed shown below.