Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Which industries are expressing interest & we should target?
    • What are the use cases that are the most compelling for these industries?
    • Which markets are we going to go after in these industries (Enterprise, mid-market, SMB, VSB)
    • What is the TAM (Total Addressable Market) 
    • What is the story we can tell if these industries solve the use cases with blockchain?
    • What are the applications do we see evolving as a result

...

  • Lay out namespacing, How is the set of the namespaces going to be defined
  • Who gets to say what a valid url is
  • Is there a registry, what does it look like, when do we need to have it in place, how is it maintained
  • Can we specify statically the form of name in a namespace, so we can check it at compile time
  • How do we introduce new formats for names?  urls are great but dont cover everything we might want
  • How do we allow nodes to define their own grammar for names?


Day 2 Location 1: Rholang Lab (Greg, Timm, Alex, Ian, Navneet, Medha)

  • TBD


Day 2 : Location 2 - Block formats, types and messaging (Mike, Chris, Griff, Vlad, Kent, Rolland)

  • 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"?

Node:

  • Kent says that at the moment there is no use of asynchrony by the output of the compiler.  Is there a layer between the grey JVM and the orange Rosette VM stuff that wakes up an idle Rosette VM and adds new strands?

Consensus:

Rholang:

  • There is no sort of import or include statement to provide a jar file - FFI is available at the rbl level but not at the Rholang level.  
  • OCaps model - supply of physical capabilities provided to the interface - everything that is needed by a contract is provided on a channel.

Mercury

...


...

Day 2 Location 3: Business Requirements (Ed, Lawrence, Nash, Joe)

  • Are there special requirements for the wallet application for Mercury?
  • Based on the industries and applications from Day 1 - define business requirements for the applications.


Day 3: Location 1: Go to Market Strategy (Ed, Lawrence, Nash, Medha, Rolland)

  • How will we reach our target Market?
  • What is the message?


Day 3: Location 2: CASPER (Vlad, Greg, Chris, Alex, Navneet, Ian)

  • TBD


Day 3: Location 3: Type Checker Design (Mike, Kent, Griff, Joe, Timm)


Day 4: Location 1: Rholang Lab (Mike, Kent, Griff, Joe, Timm)

  • TBD


Day 4: Location 2: Documentation (Timm, Alex, Mike, Joe, Kent, Navneet)

  • Who will need documentation
  • What portions of the system need documentation
  • Who will complete the documentation, what is the timeline.


Day 4: Location 3: Release Management and OSS Relations (Nash, Ian, Rolland, Medha, Lawrence)