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 Oct. 4 at 13:23 UTC - RChain Node 0.6.4 (a8ef56d0678c18adede05b735d603dd72fc1f8df)
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.
Create your run command
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
New deploy command
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. A wallet address needs to be stubbed in as well k(--from)
rnode deploy --from "0x1" --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.
- Install RNode as instructed above.
- Plan to use the public/private key set you claimed from https://docs.google.com/spreadsheets/d/18merD3OzaDk7nmxQ78SUZBzWLbxA-aOnmcdxpXrp_U0/edit?usp=sharing
- Confirm you claimed: walletAddress, amount, walletPrivateKey, and walletPublicKey from the Google Sheet shared with you via email.
- Run the node with the arguments shown below
rnode generateBondingDeploys -a <amount> -b <validatorPublicKey> -e <walletAddress> -p <walletPublicKey> --private-key <walletPrivateKey>
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.