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 test validator bonding and validation.

Work completed since the last testing session

key	summary	type	updated	assignee	reporter	priority	status	resolution

Loading...

Refresh

Instructions for testing today

Read documentation for RChain Doctor

Please read the RChain Doctor documentation and install RChain Doctor (v0.3.3). We will use this software and tools to support collecting logs from nodes participating in today's testing session.

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.3.git57ae9723 (57ae9723f67fc16824c56942545808672cfb8c6c)

Binary packages

rnode-0.8.3.git57ae9723.tgz	81.9 MiB	2019-Feb-26 12:32
rnode_0.8.3.git57ae9723_all.deb	88.0 MiB	2019-Feb-26 12:32
rnode-0.8.3.gitf1c424c2-1.noarch.rpm	82.1 MiB	2019-Feb-26 12:35
rnode-0.8.3.git57ae9723-1.noarch.rpm	82.0 MiB	2019-Feb-26 12:40

Docker image
```
rchain/rnode:dev
```

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
If you use this key, you will join the network as a validator.

To generate a key set

RNode supports ed25519 keys
Generate an ed25519 key set:
- Follow instructions from the Genesis protocol guide
- If you're using Docker and have Python installed, the rchain-keys-generator

Get the bootstrap address

Please use this bootstrap address

"rnode://f4f20286feebc89d36d11b9e6ad726b6dd3d1490@35.243.229.81?protocol=40400&discovery=40404"

Follow instructions for validator bonding

Instructions for validator bonding are in the User guide for running RNode.

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

Today's goal was to bond new validators to an existing network. We were successful creating a network and adding peers. We were successful completing the protocol for bonding (two deployments and proposals with the bond requests). We were not successful having a bonded node validate. During the testing session we also observed challenges with peering, catching up to the blockchain state, and streaming errors. See tickets above.

Vdag at the end of the session from Kelly's node

Text file for vdag

Bugs filed

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution