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 and look at the fix found in RHOL-975.

Bug fixes since last session

New features since last session

Prepare to participate

Install RNode

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 (e747f905e7b8b92b8fde1686507cce3faf252b16)

• Binary packages (.deb, .rpm, and .tgz) https://repo.pyr8.io/rchain/downloads/testing/

• Docker image 

  Docker pull rchain/rnode:testing

Get the bootstrap address

Bootstrap address https://rchain.atlassian.net/wiki/spaces/CORE/pages/501842019/RNode+bootstrap+addresses

Select a validator key or generate one 

To select a key set

• Go to 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

To generate a key set

• RNode supports ed25519 keys

• Generate an ed25519 key set

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.

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

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.

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

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.

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

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

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.

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

We attempted to launch a network, create a blockchain, have read only nodes catch up on the state of the blockchain, and people join as validators. We observed stream errors and challenges catching up to the blockchain state. We did see people successfully bond, but because they were not up to date on the state, they were not able to validate. Bug filed and plan to investigate with the dev team later today created.

Bugs filed

Chat log

Participants

• Jake

• Medha

• Paolo

• Coin Interview

• David

• Dror

• Enzo

• Gautham Peddibhotla

• Jeremy Beal

• Jim Whitescarver

• Joshy Orndorff

• Karen Moskowitz

• Kyle Connolly

• Lee Carter

• Luigi Demeo

• Navneet Suman

• Ned Robinson

• Pawel

• Per Bergman

• Rita

• Allen

• Shaun Schutte

• Steve Henley

• Tom Vasilie

• Tomislav Grospic

• Vadim

• Will Qiu

• Xuqzab