⚠️ 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.
Start from scratch
One party and a deadline. Add your own conditions and rules.
custom v1Who enforces what
- Condition
signedASignature presentCryptographically verifiable - Action
doneRecord the outcomeApplication-enforced
- 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
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. | fulfilled | done: update contract state (execute) |
Signed happens The least that makes rule “Signed” true happens at block 24500005. | fulfilled | done: update contract state (execute) |
Data unavailable The rule conditions are met, but every outside data source is unreachable. Nothing irreversible may happen. | fulfilled | done: update contract state (execute) |
Rules
1. Signed
When “signedA”
- → Record the outcome: fulfilled. The contract ends.Application-enforcedIrreversible
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
signedASignature presentCryptographically verifiableThe party-a has signed this version.
A DigiByte message signature. Anyone can verify it without trusting Contracts.
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
Irreversible once done
- Signed: Record the outcome: fulfilled. The contract ends.
These run only when every condition they depend on is known. Missing or unconfirmed data never triggers them.
Use it from code
The same template is available from the API (GET /api/contracts/v1/templates/custom) and the TypeScript SDK:
const { draft } = await client.templates.get("custom");
// fill in addresses, asset ids and amounts, then:
const { id } = await client.contracts.create(draft, { idempotencyKey: crypto.randomUUID() });