20181120 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 would like your help using a new log aggregation tool for nodes running on the network. We will use time in this session to help you get started using RDoctor. Then we will join a test network and walk through a few scenarios. 

Work completed since Nov. 13

key summary type updated assignee reporter priority status resolution

Instructions for testing today

Read documentation for RChain Doctor

Please read the RDoctor documentation. We will use this software and tools to support collecting logs from nodes participating in today's testing session.

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 (8b27e1209b744e30e32dd2099ab5be307d0d5afd)

Select a validator key or generate one 

To select a key set

To generate a key set

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

RNode Doctor

We did have success collecting logs from some participants. We know the aggregation works. We also observed difficulties running the tool on the user side. We will work to improve the configuration and operation of the tool for next week's testing.


We did have success bonding 2 node operators. Two other node operators were not successful. Ticket created to investigate why. We did not observe the UNKNOWN error during the session. We did observe the creation of 2 distinct DAGs and did not observe coming to consensus on one.

Bugs filed

key summary type created updated due assignee reporter priority status resolution

Chat log


  • Adam
  • Deanna
  • Dom
  • Jeremy Beal
  • Joshy
  • Navneet
  • Ned
  • Nutzipper
  • Paolo
  • Pawel
  • Phil
  • Shaun
  • Steve
  • Tomislav
  • Tomáš
  • Łukasz