20190108 RNode community testing

Table of contents


Each week we invite community members to help test RNode.

  • When - Tuesdays at 15: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

We will work with the RNode v0.8.2 release. See RNode-0.8.2 release plan for more details. During this session we will help you get started with v2 of RDoctor and give a refresher on how to use the DAG visualization tool. Then we will launch a network and introduce some changes and play with contract deployment and validation. 

Work completed since the last testing session

key summary type updated assignee reporter priority status resolution

Instructions for testing today

Read documentation for RChain Doctor

Please read the RChain Doctor documentation. We will use this software and tools to support collecting logs from nodes participating in today's testing session. This is a v2 version of RDoctor that does not require Docker. 

Read the documentation for visualizing the blockchain

One of the challenges of debugging is seeing what's happening when validators propose new blocks. We now have the ability to ask RNode to generate a text file that when pasted to Graphviz can generate an image. Please see 'visualizing the blockchain' in User guide for running RNode.

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.8.2 (9430de7e818e46c0c2a535d5c704cab3fca6bae5)

Select a validator key or generate one 

To select a key set

To generate a key set

Report your public key

We would like everyone to join today's network as a known validator. We need to know your public key to update the bonds file. Please report your public key in this form.

Only deploy these Rholang contracts

We've learned recently there is a bug related to Rholang contracts attempting to use the same channel and creating conflicts when deployed simultaneously. For this testing session we will only use the following, non-conflicting contracts: Simple-test-channel.rho (attached) or Dupe.rho

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

Thirteen participants, ten RNode operators. RNode operators successfully installed and used RDoctor (log aggregator) during the session. Brought up a network with validators known at genesis. Some validators saw  RCHAIN-2806 - Getting issue details... STATUS . The PR to address had just merged to dev and was not in the version we tested with. Most validators were successful staying in sync with the state of the blockchain and adding blocks. RNode operators that killed notes and restarted were not stalled in catching up to the state of the blockchain after restart. Bugs observed and filed during the session shown below.

Bugs filed

key summary type created updated due assignee reporter priority status resolution

Chat log