Creator

Alex North

Created

May 23, 2023 1:31 AM

Project

Storage Programmability

Interaction diagrams illustrating current and proposed flows for onboarding data.

Assumptions and simplifications:

• Basic, common interactions such as fetching/updating network statistics, checking actor authority, burning funds are omitted.
• The client already has sufficient datacap balance from a verifier.
• Sector activation is synchronous (as for aggregated proofs).

Current flow

Direct FIL+ flow

With data termination penalty , free CommD, and upgraded miner onboarding API similar to #298.

• No market actor is needed at all so this consumes far less gas both publishing and activating.
• Exactly the same flow can support efficient multi-sector FIL+ allocations with no extra messages (not even one per sector).
• Max duration is up to 5 years immediately.
• Minimum term enforced is limited by sector commitments, currently 1.5y (soon 3.5y).

Custom market flow

As above, but assuming a user smart contract is enforcing some additional deal terms (e.g. a client payment). If the user market supports multi-sector deals, this flow needs no additional messages to handle them.

Differences from the current flow:

• Client publishes the deal proposal
• Market doesn’t need to check client datacap balance before allocating it (because client is empowered to ensure there’s enough).

Many variants on this flow are possible (e.g. SP publishes deal instead of client). “Market” is just one type of data application. Others might include data DAO, automated replication/repair etc.