⚠️ 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.
Software licensing agreement
When the licensee's payment, carrying this contract's reference, is confirmed, a DigiLicense is activated for them on DigiStamp Assets under the signed licence terms.
license-on-payment v2Who enforces what
- Condition
paidDGB payment confirmedApplication-enforced - Action
licenseActivate a utilityApplication-enforcedpreview - Action
licenseRecord 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
- the licence DigiAsset id
- the Assets DigiLicense definition id
- the address the licensee pays
- the fee
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 |
Paid: activate the licence happens The least that makes rule “Paid: activate the licence” true happens at block 24500005. | stops: failed | license: activate utility (preview) license: update contract state (cancelled) |
Data unavailable The rule conditions are met, but every outside data source is unreachable. Nothing irreversible may happen. | none | none |
Rules
1. Paid: activate the licence
When “paid”
- → Activate the DIGILICENSE on Example license for the licensee.Application-enforcedIrreversiblePreview
- → 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
paidDGB payment confirmedApplication-enforcedThe licensee pays at least 1 DGB to DFPGZBBY…8wwkND, carrying this contract's reference, 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.
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
- DigiStamp Assets' Utility Engine
Irreversible once done
- Paid: activate the licence: Activate the DIGILICENSE on Example license for the licensee.
- Paid: activate the licence: 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.
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/license-on-payment) and the TypeScript SDK:
const { draft } = await client.templates.get("license-on-payment");
// fill in addresses, asset ids and amounts, then:
const { id } = await client.contracts.create(draft, { idempotencyKey: crypto.randomUUID() });