2018-03-14 Messaging Meeting notes

Mar 14, 2018

• @Henry Till

• @Pawel Szulc (Unlicensed)

• @Nash Foster

• Interfacing Comms, Storage, and Rholang Meeting notes

• http://rchain-architecture.readthedocs.io/en/latest/introduction/architecture-overview.html

• http://mobile-process-calculi-for-programming-the-new-blockchain.readthedocs.io/en/latest/

• System Processes

• Object Capabilities: 

  • http://erights.org/elib/capability/overview.html

  • http://erights.org/talks/thesis/index.html

A node user (at a "sending" node) should be to create a smart contract that creates some trivial message (e.g. "Hello, world!"), produce this message on a system channel with a specified destination channel. 

A system process at the aforementioned channel will serialize the message and pass it to the comms layer.

The comms layer of the "sending" node will sign/encrypt the message and send it out over network. 

Other "receiving" nodes will receive the message, and if they are running a smart contract that is consumes from the destination channel with a matching pattern, the message will appear in the match bindings. 

The receiving node should then be able to produce the message on the STDOUT system channel, effectively printing that message to STDOUT.