Each week we invite community members to help test RNode.
We look forward to introducing use of vdag to visualize the blockchain. Having these visualizations supports debugging efforts. We will spend time to introduce this tool and help everyone on the call get started.
We would like to walk through a simple scenario to look at how validators in this testing network build the blockchain.
Please read the RDoctor documentation. We will use this software and tools to support collecting logs from nodes participating in today's testing session. We're still using the Docker installation for this tool. If you are able to use, please do. If not, no worries . We'll have a new option available next week.
The session key for today is
tuesday20181218-j5dllaxo
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.
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.
Today's version RChain Node 0.8.1 (345b5d43cd2c8824cf14343e4ac8e698cd383343)
Binary packages (.deb, .rpm, and .tgz) https://build.rchain-dev.tk/testing/ (NOTE: look for RNode 8.1)
Docker image
docker pull rchain/rnode:testing |
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
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.
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
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.
not available