Each week we invite community members to help test RNode.
We will test fixes for:
We will also play highCard.rho, a version of the card game in Rholang. Contracts for the game are at https://gist.github.com/dckc/82faeebb5b4d762a3bbecc0617b4e0c5.
Contract from Proof: https://gitlab.proofmediadev.com/open-source/rchain-network/raw/master/src/exchange.rho it use MakeMint implementation from genesis block.
Configure your network
See RNode supported network configuration for information on how to configure your network to connect to other nodes.
Installation packages
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.
We will work from the release-rnode-v0.6 branch in rchain/rchain on GitHub. The version is RNode v0.6.1 (acde1c1a2bc983838a38118653905b0c85ab9c58).
Binary packages (.deb, .rpm, and .tgz) are available from https://repo.pyr8.io/rchain/downloads/v0.6.1/
Docker image
docker pull rchain/rnode:latest |
Note - At this time RNode does not run successfully in Docker on MacOSX or Windows. See the User guide for running RNode for more information.
Please see User guide for running RNode for installation and running instructions.
Select a validator key
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
Deploy command
deploy --from "0x1" --phlo-limit 0 --phlo-price 0 --nonce 0 <path of file to be deployed> |
RNode bootstrap addresses shows all available bootstrap nodes. The bootstrap node for this session is bootstrap-v0-6.
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
73 participants. Mixed experience with connecting to peers and finding blocks. Existing bugs experienced. New bugs filed. See below. Also questions captured to help update the user guide.