Table of contents


Overview

Each week we invite community members to help test RNode.

  • When - Tuesdays at 14:00 UTC
  • Where - This meeting takes place online using Zoom
    • Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/134156866
    • 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.


What you can expect this week

This week we plan to test items featured in the testing plan featured in the node-0.7 release plan

Bug fixes since last session

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

New features since last session

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh


Prepare to participate

Install RNode

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.

RNode version for this session

Today's version RChain Node 0.7.1 (73f2c30ded8519835dee5de714825fea56c057ec)

Get the bootstrap address

Connect to the network via the RChain bootstrap-v0-7  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.

Select a validator key - or generate one!

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.

./bin/rnode generateFaucetBondingDeploys --amount <bond amount> --private-key <private key > --public-key <public key > -s ed25519


Step 3 - Deploy the forward file to a bonded validator.  

./bin/rnode --grpc-host IP.AD.DR.ESS:PORT deploy --phlo-limit 10000000000 --phlo-price 1 <forward_filename.rho>

You can deploy to Kelly's node at 52.119.8.64


Wait for a block to be proposed. 


Step 4 - Deploy the bond file to a bonded validator.

./bin/rnode --grpc-host IP.AD.DR.ESS:PORT deploy --phlo-limit 1000000000 --phlo-price 1 <bond_filename.rho>


Wait for a block to be proposed.


Step 5 - Confirm you are bonded.

Either run with the hash of the block proposed after your deployment in step 4

./bin/rnode show-block <block hash>

In the the block info section either search for your <public key>, or your <bond amount> - 1 (ex If your bond amount was 500, it will be 499 reflecting the reduction of 1 REV for the joining fees).


Or, grep or search for your public key in the block contents.  If you see your public key & bond amount - you are bonded!


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.

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).

If you want to try implementing the faucet and validator bonding on your own network, please see a draft tutorial at Tutorial on bonding through the faucet.


Bugs filed

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

Chat log

Kelly forgot to capture.

Participants

  • Medha Parlikar
  • Paolo D.
  • Phil
  • Anson
  • Coin Interview
  • Dariusz
  • David
  • Dror Dayan
  • (2 on the phone)
  • Jake
  • Jack Mills
  • Jeremy Beal
  • Joshy 
  • Karen Moskowitz
  • Keith McQueen
  • Kyle Connolly 2
  • Lawrence Lerner
  • Luigi (Proof)
  • Mario Cao
  • Mervyn Chng
  • Navneet Suman
  • Rita Allen
  • Shaun
  • Steve Henley
  • Tom Vasile
  • Vadim
  • xuqzab