Project Planning: April 4, 2018

Node 0.3

@Medha Parlikar (Unlicensed)

• What is planned - Review release plan.

• What is done

  • Ambient channels for STDOUT

• Rholang - 

  • Flesh out the matcher

    • Robustness focus

  • Error handling model - will be needed on the blockchain

    • Spec'd out by Node 0.3 - 

Roscala /Rosette C++

• Compiler separation seems to work.  Keith is still fighting with it.  

• Plumbing will be needed with the node.

• Impediments to running OpCodes as a CodeVec

  • This is what they are doing in the tests right now.  Parser is in place to accept OpCodes, it just isn't interesting.

  • Compilation of Rholang has to be a JIT thing (Just in time) - because we need to keep the code around.

  • Matching has yet to be done between Opcodes and Roscala.

• Lower risk to compiler to OpCodes→ Kyle - we can start testing in April.  With RBL we can't start until August or maybe later.

  • Use patterns → Greg - 

• Submit a CodeVec to the transition function

5 min

Dependencies Discussion

• Lay out any dependencies that you may have on other teams work.

  • Capture the explicit work item that Node main function needs to implement to instantiate the interpreter on startup.

  • Dependencies between Storage and Interpreter