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 RChaing Discord.
What you can expect this week
We have a fix to address the issues experienced last week. We will use this time to test the fix to demonstrate nodes connecting to both bootstrap as well as to other nodes on the network.
Ability to build and run RNode using one of the following:
These packages will be available in the #node-testing channel in the RChain Discord.
*Note - We do not yet have a Docker image that supports the fix. We may by the start of the session, however at this time (18 June 19:00 UTC) we do not.
If if you are a Mac user, you will need the following:
Configuration to learn IP address and manually update using --host
You can manually open port on a router
RNode guessed Jake's IP address incorrectly
Exposing your node to the network behind a router or VPN allows you to see nodes, but not send message across the network (RNode v0.5)
Joshy and Jake were trying to send deploys and did not receive confirmation of send/receive
Glen did not get Libsodium installed with deb. Had to manually install. Glen to follow up with Pawel.
--diagnostics destroys terminal, best to run in a separate window. Bug captured in CORE-666.
Update documentation to support users. Work captured in Sprint 11.
Today's testers, if you need configuration support, please contact Pawel (firstname.lastname@example.org) to work through configuration issues.
Follow up on idea to have repo set up for binaries that works like docker hub. Work captured in CORE-692
This fix version of RNode does support network connection to bootstrap and connection to other peers on the network. Most participants were able to connect and see 10+ peers. Participants that were not successful experienced either issues building and running RNode, or configuration issues related to opening a port behind a router or VPN.