Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated with outcomes of today's test

Table of contents

Table of Contents
minLevel2


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 RChaing RChain Discord.


What you can expect this week

We will be testing the network and blockchain with changes made with  

Jira Legacy
serverSystem JIRA
serverId50130123-f232-3df4-bccb-c16e7d83cd3e
keyRHOL-526

The Deploy call has been updated to now require a purse (containing payment for deployment), along with other parameters.  Michael Birch will demonstrate how the deploy call works now.  Node Operators should expect to attempt a deploy of tut-hello.rho, followed by a block proposal.

Also, this updated RNode now includes a configuration file with the completion of 

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId50130123-f232-3df4-bccb-c16e7d83cd3e
keyCORE-512
 .

Steps for testing

  • 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 

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId50130123-f232-3df4-bccb-c16e7d83cd3e
keyCORE-961
 and 
Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId50130123-f232-3df4-bccb-c16e7d83cd3e
keyCORE-963
 for support for resolving issues you may experience preventing the successful running of RNode today.

RNode version for this session

We plan to test RNode based on the master branch of https://github.com/rchain/rchain. This branch updated on Aug. 7 at 00:15 UTC.

Note - At this time RNode does not run successfully in Docker on MacOSX or Windows. See the User guide for running RNode for more information. 

Installation and running instructions

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

Other requirements

Select a validator key

Use new deploy command

This is an updated since last week's test.

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


Bootstrap node address

We are using the master bootstrap node today. Please use the shown on RNode bootstrap addresses.

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 tested block synchronization across the network. Success with this. Assertion errors emerged. Please see bug list below. Highest peer count = 22. Tested killing a node after a propose and restarting and proposing to observe equivocation.65 participants. Network of 32 nodes. Tested new deploy command. 15 blocks. Experienced again 

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId50130123-f232-3df4-bccb-c16e7d83cd3e
keyRHOL-568


Bugs filed

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQuerylabels="test_0807" ORDER BY created DESC
serverId50130123-f232-3df4-bccb-c16e7d83cd3e

Chat log

View file
namemeeting_saved_chat.txt
height250

Participants

  • andyliu
  • bebei.zhang
  • Helge Avam
  • Jeremy Busk
  • pdfinn
  • Steven Bezzio
  • xuqzab
  • Wang ZhePan
  • Enzo Zheng
  • nick fox
  • cndym
  • eddie
  • dusty
  • dash
  • kimberlykeller
  • Lawrence Lerner
  • Glen Braun
  • Greg Heuss
  • Hebei.zhang
  • J Leon Yeoh
  • Jake (Drone Energy)
  • Jamie Cook
  • Jonathan Kochmer
  • Karen Moskowitz
  • Lee Carter
  • Alex Begun
  • Tomáš Virtus
  • Seth Bailey
  • Shahan Khoshafian
  • Scott
  • Sasha
  • Rob Monster
  • Ramiro Moreira
  • pgrzesik
  • raj
  • aapk
  • anson
  • Chibuike David Asamonye
  • Vadim
  • Chidindu Ojimadu
  • cndym
  • Dror Dayan
  • Dubravko Golub
  • Fangwei He
  • Jacob Bassiri
  • Jim Whitescarver
  • Icywestbrook
  • Kimberlykeller
  • Luigi Demeo
  • LuJunJie
  • Mark Pui
  • Mateusz Probhachta
  • Matthew Kaye
  • Megan Knab
  • Mervynchng
  • Navneet Suman
  • Paolo DOnorio De Meo
  • perbergman
  • Rob Monster
  • Steve
  • ted barkov
  • Tomislav Grospić
  • Hungtran
  • Medha Parlikar
  • d
  • Kent
  • kencode