Skip to content

Milestones

List view

  • No due date
    0/7 issues closed
  • First phase of docs pre-state channel. Encompassing Architecture and operational walkthroughs

    No due date
    2/12 issues closed
  • No due date
    3/4 issues closed
  • The goal of our architecture is to allow the verification and validation of heterogeneous data, or data types that are more complex that financial information (Int/Long) as in the $DAG network. State channels serve as a way notarize typed data and to add extra validation steps in consensus. $DAG could really be though of as a financial state channel that can connect various state channels in a wider network that forms a decentralized data marketplace. Given our monadic executions context (validation) we can extend validation to include user defined functions (UDF) for extra validation logic on the specific data notarized by a state channel. We can further allow for state channels to be defined as the composition of existing state channels by creating an interface on top of the Hylomorphic and Metamorphic recursion schemes. By defining an associating algebra and coalgebra to the data types that be composed within a compositional state channel, we can create functional interface with familiar Map/Reduce/Stream common in distributed architectures.

    No due date
    0/17 issues closed
  • As a first order scaling technique we can enable Light nodes, or nodes who's responsibility when acting as a facilitator is limited to transactions that are closest to their address based on XOR distance, allowing them to only keep track of a subset or 'partition' of the total address space. This allows nodes with smaller resources to participate in consensus and earn rewards. It also allows us to create 'topological' state channels, or state channels that can perform consensus according to a user defined topology. This allows for validation of state channel data directly at, or closer to the source, allowing for more complex validation (Topological Data Analysis) or reduction in latency for data consumers.

    Overdue by 6 year(s)
    Due by July 29, 2020
    0/9 issues closed
  • Overdue by 6 year(s)
    Due by June 4, 2020
    27/33 issues closed