20180814 RNode community testing

Table of contents


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

We will be testing the network and blockchain with changes made in the comms layer related to  CORE-868 - Getting issue details... STATUS  and  CORE-770 - Getting issue details... STATUS  and recent bug fixes.

We will also try to reproduce  CORE-965 - Getting issue details... STATUS  and  RHOL-581 - Getting issue details... STATUS .

Node Operators should expect to attempt a deploy of tut-hello.rho, followed by a block proposal.

Steps for testing

  • Testers will install and run RNode
  • Testers will create a network of peers
  • Several testers will slowly deploy a hello world contract and propose a block
  • Testers will report on the number of blocks received
  • We will watch to see if the number of blocks received syncs and becomes common to all peers on the network.
  • If possible a node will join after some blocks have been proposed, and observe a more efficient mechanism of obtaining historical block data.

Configure your network

See RNode supported network configuration for information on how to configure your network to connect to other nodes.

Installation packages

Please install RNode prior to the start of the testing session. If you have run RNode previously please see  CORE-961 - Getting issue details... STATUS  and  CORE-963 - Getting issue details... STATUS  for support for resolving issues you may experience preventing the successful running of RNode today.

RNode version for this session

We will we working off RChain Node 0.5.3 (779c4963e7ae16dea4d247cdc0023616202d7ac3). This is a version of the software found in the dev branch of rchain/rchain.

Installation and running instructions

Please see User guide for running RNode for installation and running instructions.

Other requirements

Select a validator key

Deploy command

deploy --from "0x1" --phlo-limit 0 --phlo-price 0 --nonce 0 <path of file to be deployed>

Bootstrap node address

RNode bootstrap addresses. Please use the dev bootstrap address.

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

54 participants. Network of 75+. Block count of 26. See below for bugs filed.

Bugs filed

key summary type created updated due assignee reporter priority status resolution

Chat log


  • LuJunLie
  • Pan
  • Hebei.zhang
  • Peter Wallin
  • Andy Liu
  • Dubravko Golub
  • Glen Braun
  • J Leon Y
  • Jake Gadakian
  • Jeremy Busk
  • Andrew Apicello
  • Anon Forareason
  • Anson
  • Dror Dayan
  • Enzo Zheng
  • Greg Heuss
  • Jameson Bradfort
  • Jim Whitescarver
  • Karen Moskowitz
  • Kimberly Keller
  • Lawrence Lerner
  • Luigi Demeo
  • Matthew Kaye
  • Michael Birch
  • Mike Monohan
  • Pan
  • Paolo DOnorio De Meo
  • Pawel Szulc
  • perbergman
  • pgrzesik
  • Raleigh/ZetaHash
  • Raymond Fu
  • Scott Thomas
  • Seth Bailey
  • Shahan Khoshafian
  • Steven Bezzio
  • Tomislav Grospić
  • Vadim
  • Vick Manocha
  • Will Qiu
  • xuqzab
  • Go
  • Stoica Daniel
  • Sasha
  • Lyon Kwek
  • Kyle Connolly
  • Jacob Bassiri
  • hungtran
  • Erhan Kataltepe
  • Claire TOlan
  • David's iPhone
  • Chibuike David Asamonye
  • Jamie Cook