2018-10-17 Project Planning Meeting notes

Mercury release plan

• Work in progress

• (deprecated) Mercury release plan - please review.

  • Node team is working on updates this week

  • Suggestion that the plan should be user-focused (deliverable features) rather than specification or implementation details

  • Rita is available to pair with Pawel to walk through Mercury deliverables. @Pawel Szulc (Unlicensed) please coordinate with Rita to find a time for this walkthrough

5 minutes

node-0.7 release plan   

• 10/22 (Testnet)     

@Medha Parlikar (Unlicensed)

• Name Registry - Done

  • Porting of Contracts will roll over.

  • Removing the ability to listen on forgeable names will be on hold until contracts are ported.

• Validator Bonding - Done

  • Includes Faucet contract - to support bonding with Rev

  • Block adding bug fix in dev

• Threading - needs testing & integration with the other teams.

• Message chunking - on track, Casper integration done

• Interpreter hardening - coming along nicely, still at least 1 more sprint of work remains.

• Test net refresh to take place 10/22 per the plan described in 2018-10-02 Meeting notes: release planning and test net updates

 10 minutes

RNode-0.8.1 release plan

• 11/12 (Testnet)

 @Medha Parlikar (Unlicensed)

• Testnet Faucet

  • Jack Mills will build a generic web service that will talk to the faucet & return data. 

• Short leash deploy

• Block Store

• Security review of contracts

  • Would involve looking at the contracts carefully and assess whether they could be hacked. 

  • Limited to our imagination.  Tools to formally verify are not available yet.  

• Remove unforgeable names + contracts Ported

• Slashing & Unbonding

• Design for Peek - Kyle & Lukasz

• Client Interface (https://rchain.atlassian.net/browse/CORE-1162)

  • Discussion on what this is and why it's needed

  • Working on the stub of the application by the end of the sprint, which gives us and initial idea of the design and UX.

  • Plans to update the ticket with what he has learned.

• Block compression needs a do-over.  

10 minutes

node-0.9 release plan

•  12/10 (Testnet)

@Medha Parlikar (Unlicensed)

• Peek & block merging

• Checkpoints

• Sharding client software → We need to assess.  

  • Request for team to review Shards in RChain

  • Kyle projects 4 sprints to get this done.

  • Registry took longer to complete.

  • 10-17-2018 as of today, no spec for issuance

• Lazy Validator Hedge

• Governance outcomes - Economics

Peek

@Medha Parlikar (Unlicensed)

• @Michael Birch (Unlicensed) - without merging we are not making a DAG.  We need it. MUST HAVE to support Merge

• Implementing this requires the following

  • Updating the tuplespace 

    • Needs a spec @Łukasz Gołębiewski (Unlicensed) reviewed by @Kyle Butt

  • Update the language

  • Spec, implementation, testing - 2 sprints at least

Performance

@Medha Parlikar (Unlicensed)

• @Łukasz Gołębiewski (Unlicensed) - in RSpace - we have to fix to remove the syncVar if we can live with a mixed store. Keep hot store in memory, concurrent trie map and HistoryTrie in LMDB.  

  • Dom is working on it, should know by the end of this week, benchmark & see if it is correct.  

  • Need to check how it behaves wrt to memory utilization and consumption.

  • It's the single writer thread - that is causing the bottleneck.  Keeping data in memory will help us avoid serialization.

  • RSpace also needs to use a new threading model.

  • Planning on this work right away.  (this or next sprint)

Dev Done date

@Medha Parlikar (Unlicensed)

• Jira shows me end of January

  • Medha showed a graph from Jira showing a projection of feature complete in Jan.

• This is based off of story point estimates + velocity

• January release would be updating of shard parameters + economics finalization.

• Requirement to release in Q1 relates to contractual obligations between the Coop and Pithia

• Extra-protocol sharding must precede in-protocol (level II) sharding 

  • Question of when which gets delivered when.

• We added Peek to Mercury.  

Performance of the system

• Concerned about the following items relating to performance

  • Our Grafana dashboards are still not working after the switch of how we report metrics. @Medha Parlikar (Unlicensed) confirm this is ticketed so it can be done next sprint.

  • We don't have baselines yet for performance that are socialized amongst the team

  • We don't have a person or team in charge of performance.  Yet this is the most important deliverable we have.

  • https://rchain.atlassian.net/browse/CORE-1054