search

codex-storage / codex-research

Codex durability engine research
35 stars 14 forks source link

Fast, lightweight and cheap consensus interactions #39

Closed markspanbroek closed 3 years ago

markspanbroek commented 3 years ago

There are three parts of Dagger that require consensus, with different performance requirements.

  1. Storage contracts that are enforced by of proofs of retrievabiity
  2. Micropayments for bandwidth
  3. Allow buy/sell of coins to pay for the above

Of these three, the second one is the most demanding in terms of tx/sec.

markspanbroek commented 3 years ago

Conclusions:

For (1) storage contracts we expect both rollups and newer consensus engines such as Avalanche (and in the future Glacier) to give sufficient speed (~5000 tx/sec) to support the Dagger network. The same holds for (3) buying/selling of coins.

For (2) bandwidth micropayments we require payment channels. We prefer simple uni-directional channels based on a consensus layer that is able to open and close these channels quickly, over a complex channel routing algorithm that is based on a slow consensus layer. It is likely that a UTXO DAG based approach (such as in ABC and Cardano) can offer horizontal scalability through parallelization in the DAG.

Next steps: