...
...
...
...
...
...
...
...
...
...
...
...
Date
Attendees
Medha Parlikar (Unlicensed) (Scribe)
- Michael Stay (Unlicensed)
- Henry Till
- Pawel Szulc (Unlicensed)
- Nash Foster
Goals
- Get on the same page on what is needed for the April release.
- Discuss at a high level what needs to be done in order to support message passing via Rholang
- Do all messages to and from the Communications module go through the tuplespace? - Are there any exceptions to this? -
- What is the format of these messages?
- Are there any messages that we can see that would use the data structures implemented for Rholang (Rholang ADT & Kent's protos) that would ultimately wind up in communications?
- Do we have a Protobuf primitive in Rholang?
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
Overview |
| ||
Where does Comms Fit in? |
| ||
Where does the Tuplespace fit in? | Michael Stay (Unlicensed) |
| |
Is it written in Scala? | Henry Till |
| |
Handling failure? |
| ||
Sending Rholang Terms |
| ||
Communications stack & messages |
| ||
Node.03 April Milestone | A node user should be to create a smart contract that creates some trivial message (e.g. "Hello, world!"), produce this message on a system channel at a specified which will serialize/sign/encrypt the message and send it out over network. This message should be able to message is encrypted and received by another node. (Comm Resolver & STDOUT) |
Action items
- Pawel Szulc (Unlicensed): Figure out how to wire up communications to a Rholang channel. Keep it simple. Then go back and improve.
- Medha Parlikar (Unlicensed): Schedule a discussion to talk about Communications in depth.