Each week we invite community members to help test RNode.
This we we plan to test validator bonding, bug fixes, and new features.
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 relate to content in the directory from a previous version.
Updated 13:28 UTC
Today's version RChain Node 0.6.4 (ae42cceb5ec4a3f87467ba38e317052eefca407b)
Binary packages (.deb, .rpm, and .tgz) https://repo.pyr8.io/rchain/downloads/testing/
Docker image
Docker pull rchain/rnode:testing |
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.
You can now check your version of RNode via the gRPC server.
curl -s localhost:40403/version |
With the merge of https://github.com/rchain/rchain/pull/1555, the deploy command for RNode changed. Now deploy commands need values for phlo-limit and phlo-price that are greater than 0.
rnode deploy --phlo-limit <value> --phlo-price <value> <path to .rho file> |
After the deployment is successful users might see a message like CostAccount(__some_value__, Cost(__some_value__))
. The first __some_value__
represents number of steps it took to reduce/execute their code, second __some_value__
means how much it cost. I said "users might see" because it depends on how they execute programs. We will make the message more user-friendly in the near future.
java -jar bonding-helper-assembly-0.1.0-SNAPSHOT.jar <validator public key> <wallet address> <amount> <wallet private key> <wallet public key> |
After you have done this you should see 3 new rholang source files have been created. These files will be deployed by you as part of the bonding process. Additional instructions will be provided during the testing session.
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
47 participants. Demonstration of the process to bond validators to today's testing network. Block length 26. Peers 21. Bonding process didn't work.
https://drive.google.com/file/d/1hHSif-46uFWLKXr3VTPS9QH_eGF5qTFS/view?usp=sharing