Joshy Orndorff JoshOrndorff

RNode Log Message Guide

RNode version 0.6.4

The RNode software is quickly developing a reputation for being verbose. All that output is helpful for developers debugging and also for validators and node operators monitoring the health of their node. But it isn't valuable if you don't know how to read it.

Here I'll summarize the main interactions your node has, and translate the most common and useful log messages.

Starting up

At startup your node generates any necessary files that don't already exist, gets familiar with your network configuration, and reports some useful information about itself.

A project plan for Joshy's first 90 days with the RChain marketing team.

Deliverables

Rholang tutorial
- Intermediate skill-level audience
- Example motivated
- Includes exercises and questions
- Possible integration with rchain.cloud
Rnode installation and use videos
One overview of what RNode can do

	new seq in {

	// Take a cons list of contracts, run them sequentially
	contract seq(@[head, tail], @ack) = {
	new return in {
	@head!(*return)
	\|
	for (_ <- return){
	seq!(tail, ack)
	}

	pragma solidity ^0.4.24;

	// WARNING: This code is intended for brainstorming purposes. No effort has been
	// made to use safe math, write tests, or pen test. I haven't really even
	// thought about function access.



	contract RHoursProject {

	module PI-SYNTAX
	imports DOMAINS

	// Processes
	syntax Proc ::= Norm // Normal processes are still processes
	\| Proc "\|" Proc // Parallel
	\| "!" Proc // Replication
	\| "(" "v" Id ")" Proc // New name
	\| "(" Proc ")" // Allow parens for grouping

	new stdout(`rho:io:stdout`) in {
	@"tenthCaller"!("Joshy", *stdout)
	}