Create a deal schedule

Time to make some deals with storage providers. Start with running the deal pusher service

singularity run deal-pusher

For PDP (--deal-type pdp) schedules, run deal pusher with FEVM RPC configured:

singularity run deal-pusher --eth-rpc "$ETH_RPC_URL"

For DDO (--deal-type ddo) schedules, run deal pusher with DDO contract configuration and run deal tracker with DDO tracking enabled:

singularity run deal-pusher \
  --eth-rpc "$ETH_RPC_URL" \
  --ddo-contract "$DDO_CONTRACT_ADDRESS" \
  --ddo-payments-contract "$DDO_PAYMENTS_CONTRACT_ADDRESS" \
  --ddo-payment-token "$DDO_PAYMENT_TOKEN"

singularity run deal-tracker \
  --eth-rpc "$ETH_RPC_URL" \
  --ddo-contract "$DDO_CONTRACT_ADDRESS"

Send all deals at once

With smaller dataset, you could send all deals to your storage providers all at once. To achieve this, you can use below command

singularity deal schedule create <preparation> <provider_id>

However, if the dataset is large, it may be too much for storage providers to ingest that many deals before the deal proposal expiration, so you can create a schedule

Send deals with schedule

With the same command, you can create your own schedule to control how fast and how often should the deals be made to storage providers

singularity deal schedule create -h

Batch schedule creation

When you need to replicate multiple preparations across multiple storage providers, use create-batch to generate all schedules in one command:

# Cold DDO copies to 2 providers
singularity deal schedule create-batch \
  --group dataset-a-cold \
  --preparation prep-a --preparation prep-b \
  --provider f01000 --provider f02000 \
  --deal-type ddo

# Warm + cold to 1 provider
singularity deal schedule create-batch \
  --group dataset-a-warm \
  --preparation prep-a \
  --provider f03000 \
  --deal-type ddo --deal-type pdp

This creates the full cross-product: for each preparation, for each deal type, a schedule is created for every provider. The first example produces 4 schedules (2 preparations x 1 deal type x 2 providers). The second produces 2 schedules (1 preparation x 2 deal types x 1 provider).

Deal types

The --deal-type flag specifies which deal types to create. Repeat for multiple types:

• market — legacy f05 market deal (default)

• pdp — PDP (Proof of Data Possession) deal

• ddo — DDO (Decentralized Data Onboarding) allocation

To express per-provider differentiation (e.g., some providers get cold copies only, one gets warm + cold), run separate create-batch commands with different groups.

Group labels

The --group flag is required for create-batch and tags all generated schedules with a shared label. This makes it easy to identify and manage related schedules together. You can also set --group on individual schedule create commands.

When to use create-batch vs individual schedules

• create-batch: best for one-shot setup when you know the full set of preparations, providers, and deal types upfront

• schedule create: best for adding individual schedules or when different preparations need different parameters per provider

PDP caveats

• Accepted PDP piece CID formats: legacy CommP and CommPv2.

• Current PDP proofset piece-size cap: 1 GiB minus FR32 overhead (1,065,353,216 bytes).

• On calibnet/devnet, createDataSet path requires sybil-fee value and uses compatibility listener handling.

For a full real-network walkthrough with concrete transactions, see:

• PDP Calibnet End-to-End Runbook

DDO caveats

• DDO schedules use deal type ddo.

• DDO schedules require a non-empty urlTemplate.

• The provider must be active in the DDO contract and support the configured payment token.

• DDO deals stay in proposed state until deal-tracker observes allocation activation on-chain.

For a full DDO setup guide, see:

• DDO Contract Deal Guide