We will work with the RNode v0.8.2 release. See RNode-0.8.2 release plan for more details. During this session we will help you get started with v2 of RDoctor and give a refresher on how to use the DAG visualization tool. Then we will launch a network and introduce some changes and play with contract deployment and validation.
Please read the RChain Doctor documentation. We will use this software and tools to support collecting logs from nodes participating in today's testing session. This is a v2 version of RDoctor that does not require Docker.
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.2 (9430de7e818e46c0c2a535d5c704cab3fca6bae5)
- RNode supports ed25519 keys
- Generate an ed25519 key set:
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.