/
Project Planning June 27, 2018

Project Planning June 27, 2018

Jun 29, 2018

Date

Attendees

Goals

  • Status on Node 5 - Blockers / Dependencies
  • Review Node 6 - clarify undefined items / what we will demo
  • Review Roadmap & Discuss Risks in the project

Discussion items

TimeItemWhoNotes
15 min
Everyone
  • Node 5 Open item review - are we on track?  What is blocked / waiting on others
    • Merge to master on Monday.
  • Report on Node testing results
    • Good turn out ~10 participants
    • Revealed an issue related to block deploy and propose that we met to investigate today and will do a working session tomorrow to attempt to recreate and debug
  • Networking issue status update
    • Node 5 closes this week - do we have the right fix in place before release?
  • Discussion of timeout in RNode
    • Pawel recommends the node functioning as both a client and a server to be allowed to join network
      • This is an initiation check. 
      • Is there a periodic check after initiation? Yes, this is in Kademlia.
    • Recommendation for Node team to look at documentation on Whisper from Ethereum on gossip networks - Whisper 
      • Validators will function as a gossip network
    • Kyle - we want some assurance we have some connectivity before fire and forget - need to use fire and forget.  
10 minNode 6Medha
  • Finalize what we will demo for rewards and mint by Thursday of this week.
  • RNode features for this release?
  • Storage of blockchain - what will we offer given our plan for data retrieval?
  • Engagement with exchanges (JSON API)
    • We have limited capacity to engage and provide deliverables at this time
    • We will ramp up this engagement coinciding with RCon3
  • Questions
    • Should the registry be ambiently available - This is scoped for RNode v0.7
35Review Roadmap & discuss Risk 


  • Review Roadmap
    • Venus planning to start at RCon3
    • Mainnet to coincide with RCon4 
      • This will happen in Dec (before Dec. 19)
      • This will happen in the US
  • Lots of questions around Cost models
  • We need to put Consensus under pressure.
  • No performance metrics yet.  Initial tests revealed bugs, need for runtime version of tuplespace in casper.
  • Communications is not yet stable
  • Limited pressure on Rholang language
  • Lykke and Bittrex integrations work not started

Risk Mitigations
  • RISKS
    • Validator rewards
      • What's in the release plan is stubbed in (demo rewards being split evenly among validators in a shard, implemented as a parameter that can be changed later)
      • Greg agrees to this
      • How will it be parameterized? 
        • Original design is for it to be in Rholang
        • For this consider it being written in Scala and exposed to Rholang
    • Validator slashing
      • Is not yet specified
      • At least - demo slashing for equivocations
    • Sharding of the blockchain
      • At risk because of delay in deterministic and unforgeable names.
      • At risk because of timeline and delays with locking down the architecture.
      • Needs to generate Rholang code in the Genesis block.
      • Suggestion to write in Scala




Action items