Goals
- Common understanding of Mercury and its requirements. Every one of us should be able to answer "what about... " questions with respect to Mercury if cornered.
- Identify major gaps in Documentation and make sure someone is assigned to resolve it.
- Do some coding together in Rholang. Write contracts.
...
- Addressing shell games that amount to finding consensus assuming you have already got consensus...
- Betting requires fungibility between forks. How do we solve this in POS Consensus - what is the asset external to the system to create consensus?
- If we define consensus inductively, there is a time window over which a network split absolutely cannot happen. There is no value for this time window that makes network splits not happen.
- What happens when a validator leaves for several months and then returns - how is trust re-established without opening the network to attack?
- How do we address the problem with the first induction window, in which you cannot possibly have bonded validators, and you must fall back to centralized selection.
- Will increasing the induction time to 7 days resolve the problem.
- Do we have a solution to the Prisoner's dilemma? reference:
- Transaction receipts (in lieu of every validator validating every shard that shares cross-shard state) create a Prisoner’s dilemma. It doesn’t matter if you model the self-referential consensus-by-betting with the Pi calculus, because such a process model does not model such economically driven externalities.
- How does one identify the list of validators at any given time? (It's not clear to it will work as described, may simply need clarification)
How do we address double spend?
For the Mercury release do we plan to have our staking token implemented "natively" - specifically, such that we can do the equivalent of msg.sender.send(amount) in Ethereum? Or are we just going to use the token.rho contract for our staking tokens too?
...
- How will we reach our target Market?
- What is the message?
- What are we doing to create buzz?
- What is the value prop?
Action Items:
- Lawrence & Navneet: Provide a list of conferences that are targeted, dates and expected outcome
- Lawrence: Timeline for blog posts that are needed from Development
- Medha Parlikar (Unlicensed): Publish this information to the wiki
Day 3 : Location 3 - Block formats, types and messaging (Greg, Chris, Griff, Vlad, Michael, Dan, Navneet)
What hashes are there, and what do they look like?
What data is common to all blocks?
- Are there types of blocks, if so, how many types, and what is the specification of each type?
What is the size of a block? Can block sizes vary?
Are there "light blocks" constructable for "light clients".
- Chris Kirkwood-Watts: Document messaging & communications requirements
- Griff McClellan (Unlicensed): Document storage requirements
- Michael Birch (Unlicensed): Document Consensus requirements
Day 3: Location 4: Compiler Design & Economics (Mike, Kent, Eitan, Timm, Joe, Kyle)
...
- Who will need documentation
- What portions of the system need documentation
- Who will complete the documentation, what is the timeline.
Action Items:
- Michael Stay (Unlicensed): Compile the list of documents
- Medha Parlikar (Unlicensed): Assign out documentation tasks & create timeline
Day 4: Location 4: Release Management and Open Source Software Relations (Nash, Ian, Rolland, Medha)
- Communicating releases to the Open Source Software Community
Action items:
- Daniel Grachanin (Unlicensed): Design developer.rchain.coop site, including content.
- Medha Parlikar (Unlicensed): finalize getting started page & provide to Dan