Project Planning July 11, 2018

5 min

Storage Prioritization

Henry

• Block storage

• Introspection - obtaining data from the blockchain

• Cost Accounting in the Tuplespace - accounting for the cost of the matcher in RSpace.  Depends on Mateusz completing his work.

5 min

Consensus Priorization

Michael

• Bonding/Unbonding for next sprint

• Slashing rules

• Economics and Incentives

• Performance 

  • We can isolate network latency by using local Docker networks.  

  • We haven't let a network run for days and run hundreds of blocks.

  • Can we have a tool that combines testing and orchestration written in Scala?  

5 min

Rholang Prioritization

Kyle

• Cost Accounting

• Variable references around locally free - small, important bug

• More feature completeness around built in data types. 

5 min

Communications & Node

Pawel

• Clean up circular references in Communications between Kademlia & RChain protocol & transport 

• Node usability features

5 mins

Virtual Machine

Timm

• Test cases around actors

• Parallel execution - testing comes next. 

5 min

News from Greg

Greg

• Immersive technologies, audio encoding & delivery, planning to go to market

• We need a demo of audio data on chain.  People have access to a player that writes the play count back to the blockchain

• Smart Contract that distributes the funds to the artist.

• What needs to be done:

  • Smart contract that stores the content & distributes funds to artists.

35

Review 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 Validator Economics - Georgious will be joining the project. He is working on the problem.   

• We need to put Consensus under pressure. - Hacker One has been engaged + planning performance tests as well.

• No performance metrics yet.  Initial tests revealed bugs, need for runtime version of tuplespace in casper. - Storage team has delivered COMM metrics + dashboard.

• Communications is not yet stable - Supported network configurations defined. 

• 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 - we will be writing this in Scala for Mercury.

  • Validator slashing

    • Is not yet specified - addressed.  Specified & ticketed in Sprint 13.

  • Sharding of the blockchain

    • At risk because we have not started implementation

    • Less risk because we have simplified what we are building. 

    • Mounting and unmounting operations need specification

    • Shard transfers may need to be written in Scala.