Or iPhone one-tap : US: +16468769923,,134156866# or +16699006833,,134156866#
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: 134 156 866 International numbers available: https://zoom.us/u/rDfBtpt
Additional communications are posted in #node-testing on the RChain Discord.
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
RNode supports ed25519 keys.
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
Create your bonding request
You need to have both the public and private keys for bonding. Make sure you use private key that matches the one you used in your RNode run command.
Step 1 - Run RNode and connect to the bootstrap node
./bin/rnode run --default-timeout 6000 -b "<bootstrap address>9?protocol=40400&discovery=40404" --validator-private-key <private key>
Step 2 - Generate the deploy files. There now exists a command within RNode to handle the deploy request generation. When this command is complete there will be 2 new .rho files in your directory: forward_filename.rho and bond_filename.rho.
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.
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
Participants 30. Limited success in. bonding new validators to the network. Error: UNKNOWN observed (RHOL-917). Challenges with nodes restarting and catching up to the state. Issues related to block passing (RHOL-953).