⚠️ NOTICE: Deployment Testing in Progress We have recently deployed a major platform update and are currently performing post-deployment testing and validation. Please do not use this website or submit any transactions until testing is complete. Some features may be unavailable or behave unexpectedly. Thank you for your patience as we work to ensure everything is functioning correctly.

DigiAsset sale (observed)

The buyer pays DGB and the seller delivers a DigiAsset themselves. Fulfilled when both have happened; the seller is notified once paid. Nothing is transferred by Contracts.

Use this template

Commercedigiassetpaymentsaleasset-sale v1

Who enforces what

Condition paid DGB payment confirmedApplication-enforced
Condition delivered Asset heldDigiAsset-indexer-enforcedpreview
Action notifySeller Send a notificationApplication-enforcedpreview
Action complete Record the outcomeApplication-enforced
Action complete Issue a certificateApplication-enforcedpreview

Consensus-enforced: Every DigiByte node enforces it. Nobody can override it, including Contracts.
DigiAsset-indexer-enforced: DigiAsset indexers apply it after a transaction confirms. It is not DigiByte consensus: a valid DigiByte transaction can still be treated as burning assets.
Application-enforced: Contracts decides it in its own application, from data you can check. You trust Contracts' nodes, records and evaluation.
Cryptographically verifiable: Anyone can check it from public data and mathematics alone (wallet signatures, drand). Contracts records it; you need not trust Contracts to verify it.

Before it can be signed, fill in

a DigiByte address for every party
the DigiAsset id
the address the buyer pays
the price

Simulation

The standard scenarios, run through the same rule engine the live service uses, with example values in every blank (addresses nobody holds keys for, and a format-valid example asset).

Scenario	Outcome	Actions
Nothing happens Everyone signs, then nobody does anything until expiry.	lapsed	none
Tell the seller to deliver happens The least that makes rule “Tell the seller to deliver” true happens at block 24500005.	lapsed	notifySeller: send notification (preview)
Paid and delivered happens The least that makes rule “Paid and delivered” true happens at block 24500005.	fulfilled	notifySeller: send notification (preview) complete: update contract state (execute) complete: issue certificate (preview)
Data unavailable The rule conditions are met, but every outside data source is unreachable. Nothing irreversible may happen.	none	none

Rules

1. Tell the seller to deliver
When “paid”
- → Notify the seller (action required).Application-enforcedPreview
2. Paid and delivered
When “paid” AND “delivered”
- → Record the outcome: fulfilled. The contract ends.Application-enforcedIrreversible
- → Issue a completion certificate to the seller and buyer.Application-enforcedIrreversiblePreview
Expiry
At DigiByte block 24,540,320 (20 confirmations), if no outcome has been recorded, the contract ends as lapsed. Nothing that happens at or after expiry counts.

Conditions

paidDGB payment confirmedApplication-enforced
The buyer pays at least 1 DGB to DMw9JXBp…zyuDPz, with 20 confirmations.
The payment is an ordinary DigiByte transaction between the parties. Contracts observes it on the chain and decides whether it counts.
- Without a payment reference, any payment of the amount to the address counts. Use an address reserved for this contract.
- Contracts never holds or forwards the funds.
deliveredAsset heldDigiAsset-indexer-enforcedPreview: monitored in a later release
The buyer holds at least 1 units of Example item, with 20 confirmations.
Ownership is decided by DigiAsset indexers; Contracts reads it from its own DigiAsset Core and decides whether the condition holds.
- A confirmed DigiByte transaction is not always a valid DigiAsset transfer: indexers burn assets when an asset's rules are broken.
- Assets that carry on-chain rules (royalties, approvals, KYC, expiry) are treated as UNKNOWN until those rules are modelled.

What you are trusting

DigiByte itself does not enforce these rules. Contracts evaluates them from public data and records the outcome; the parties’ signatures and any anchors can be checked by anyone.

Contracts' evaluation and records
Contracts' DigiByte node
Contracts' evaluation
Contracts' DigiAsset Core indexer

Irreversible once done

Paid and delivered: Record the outcome: fulfilled. The contract ends.
Paid and delivered: Issue a completion certificate to the seller and buyer.

These run only when every condition they depend on is known. Missing or unconfirmed data never triggers them.

Some parts are in preview: they are part of the agreement, but Contracts will monitor or perform them only once that feature launches.

Use it from code

The same template is available from the API (GET /api/contracts/v1/templates/asset-sale) and the TypeScript SDK:

const { draft } = await client.templates.get("asset-sale");
// fill in addresses, asset ids and amounts, then:
const { id } = await client.contracts.create(draft, { idempotencyKey: crypto.randomUUID() });