Market 2.0

Market 2.0 is Curio’s unified, extensible deal interface between clients and storage providers.

It exists to abstract away deal-type-specific integration. A client can request PoRep-style storage, PDP operations, or future specialized services through one consistent model and one consistent API surface.

Deal Model

Every deal is expressed as:

• id: deal reference

• client: requester identity

• products: requested services

• data source (optional): operation input data when required

This model reflects real deal-making: who is asking, what they want, how it is referenced, and what inputs are needed.

Clients

Use these guides to submit and manage deals:

1. HTTP API: create, update, and query deals

2. Deal intake paths and upload ordering

3. Lifecycle and status tracking

4. Data model and source/format requirements

5. Error codes and troubleshooting

Contact your storage provider when:

1. You receive repeated 500 or 503 responses.

2. A deal stays non-terminal longer than expected.

3. A contract-related rejection needs provider policy confirmation.

Storage Providers

Use these guides to operate and support Market 2.0:

1. Lifecycle and operational behavior

2. Contract integration and provider allowlisting

3. DDO contract review and allowlisting

4. Error codes for support triage

Operational note:

1. Product/source controls and contract allowlisting are provider policy decisions managed through the Curio GUI.

2. DDO contracts must be vetted before allowlisting.

Developers

SDK and Client Library Developers

1. HTTP interaction model

2. Lifecycle semantics

3. Error handling contract

4. Data model and validation context

5. Data source and format constraints

Contract Integrators

1. Contract integration guide

2. Current DDO contract interface (CurioDealView v1)

3. DDO contract review and builder guide

Current integration surface:

1. DDO uses CurioDealViewV1 today.

2. Additional interfaces may be introduced in future product/version evolution without changing the top-level Market 2.0 deal model.

Curio Product Developers

1. Extending products

2. DDO product behavior

3. Retrieval product behavior

4. PDP product behavior

Design rule:

1. Extend an existing product when behavior remains backward compatible and JSON evolution is safe.

2. Introduce a new product when behavior, lifecycle, or compatibility contracts diverge.