Or iPhone one-tap : US: +16468769923,,261325582# or +16699006833,,261325582#
Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 646 876 9923 or +1 669 900 6833 Meeting ID: 261 325 582 International numbers available: https://zoom.us/u/acxByNFCVq
Additional communications are posted in #node-testing on the RChain Discord.
What you can expect this week
This we we plan to test validator bonding, bug fixes, and new features.
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.
Pick out a an unclaimed row with a validator key pair
Specify your node if you want. You can wipe your information after testing
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.
Check your version
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)
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.
Instructions for volunteers who will help test the validator bonding process
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.
Share your experience
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
19 participants. Created a network. Troubleshooting work to address bonding issues. Found the bootstrap node did not have the correct wallets file. When we fixed with correct wallets file, bonding was successful.