Last week's testing session (20180710 RNode community testing) revealed bugs related to consensus. This week we will tests the fixes the team implented
- Establish Medha's node as a server
- Other node operator deploys a contract via that server
- Server proposes block
- View content of the contract
- Call the contract
Configure your network
See RNode supported network configuration for information on how to configure your network to connect to other nodes.
Please install RNode prior to the start of the testing session. We will be using the version of RNode in the dev branch of the project on the rchain/rchain repo on GitHub.
# TARBALL INSTRUCTIONS
rm -r ~/.rnode
tar xvzf rnode-0.5.1.tgz
# macOS users only
# debian/ubuntu users only
sudo apt-get install libsodium
# fedora users only
sudo dnf install libsodium
# run the node
./bin/rnode run --host 126.96.36.199 -b rnode://firstname.lastname@example.org:40400 --validator-private-key <YOUR PRIVATE KEY HERE>
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:dev
Download and save the bonds.txt file
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
Empty the var/lib/rnode directory
Please see User guide for running RNode for run instructions. For this testing session we will use public bootstrap node for dev branch shown in the user guide. Other run instructions may be provided during the session.
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.