Each week we invite community members to help test RNode.
We will test deploy and propose across the network. Testing will be similar to this demo.
Steps:
Connect to the bootstrap and find your peers.
Deploy a contract to your local node.
Propose a block and observe the fork choice rule.
Configure your network
See RNode supported network configuration for information on how to configure your network to connect to other nodes.
Installation instructions
Updated 7/10/18, 12:53 UTC
Please install RNode prior to the start of the testing session.
Binary packages (.deb, .rpm, and .tgz) are available https://repo.pyr8.io/rchain/downloads/testing/
Docker image - tag is 'testing'
NOTE - At this time RNode does not run successfully in Docker on MacOSX. This is because you must run Docker with the host networking option. By default, Docker runs in network bridge mode. To use the host networking option, you must include the 'network=host' option in your Docker run command. This flag does not work on MacOSX.
docker pull rchain/rnode:testing |
Download and save the bonds.txt file
Download the file from https://repo.pyr8.io/rnode-test-sessions/bonds.txt
Save the file in a /genesis directory
Note - If you previously downloaded and save the bonds file for a different testing session, you need to make a change. Previously the system looked for the bonds file in the /validators directory. Changes in the software now supports looking for the bonds file in the /genesis directory. Please make sure the bonds file is stored in the correct directory.
Select a validator key
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
Empty the var/lib/rnode directory
If you have previously run RNode, we advise you empty this directory.
Connect to the bootstrap node rnode://c61769b39d368cbcbc9499634e030386c79d5b02@52.119.8.108:40400
rnode run -b rnode://c61769b39d368cbcbc9499634e030386c79d5b02@52.119.8.108:40400 |
Note the port is different than what is described in the network configuration dock.
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
Fix is clearing the data directory
Node assumes you're starting with a clear tuplespace. If you didn't shut down with an empty tuplespace, then node thinks the tuplespace is empty when it's not.