Using a market similar to current asks in the storage market, DataPayer can learn price /terms, and then pay into a fund for retrievals.

agreement is a negotiation for:

• Price
• Allocated bandwidth for this pool
• Amount
• set of agreed auditor 3rd parties.
• Agreed validated fraud rate (e.g 10%)

Payment is agreed with SP. result of payment protocol is:

• Escrow held with client money, matched (at some rate) with collateral from the SP as it’s commitment to honor those retrievals
• DataPayer is issued a set of ‘passes’ that can be redeemed for downloads.
  • (I’m imagining these passes look somewhat like ‘privacy pass’ blinded tokens)
  • 1 option: data payer generates the passes, and commits at this point to the merkel root of them
  • 2nd option: SP generates the passes, gives them to the data payer, data payer signs each one, and it’s the re-collection of the signatures that the SP uses to redeem payment later.

Later, a Client has a pass and wants to use it to download a unit of data from the SP.

It requests from SP, gets back data.

SP can collect passes. can periodically redeem collected passes to collect money back from escrow.

If SP isn’t serving with agreed upon characteristics / not serving.

Client forwards bad pass to auditor.

Auditor makes fall-back request. if it doesn’t work in agreed characteristics, auditor can ‘slash’ SP.

If failure rate is high (sp is failing) per auditors - then auditors continue, SP looses it’s staked money.