⚠️ 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.
Template gallery
Starting points for common agreements. Each shows who enforces every condition and action, and how it behaves in simulation, before you fill anything in.
Eight starter templates
- Agreements
Two-party signed agreement
Both parties sign the same terms with their own DigiByte wallets. The agreement is fulfilled when both confirm completion, and lapses at expiry if they do not.
Cryptographically verifiableApplication-enforced - AccessUses preview features
DigiAsset holder-gated access
While the member holds a pass DigiAsset (as DigiAsset indexers see it), a DigiPass on DigiStamp Assets grants them access.
DigiAsset-indexer-enforcedApplication-enforced - Content
Time-locked content release
Content sealed with a drand timelock (Signal's format) cannot be opened by anyone before its round. When the time comes it is revealed, checked against the signed commitment, and the contract is fulfilled.
Cryptographically verifiableApplication-enforced - CommerceSimulation only
DigiAsset delivery after verified payment
Once the buyer's DGB payment is confirmed and verified, the seller's DigiAsset is transferred to the buyer. The transfer is simulated against DigiAsset indexer rules before anyone signs it.
DigiAsset-indexer-enforcedApplication-enforced - WorkUses preview features
Milestone-based approval
The client approves each milestone by signing an approval with their wallet. Both parties are told as each one is approved; the contract is fulfilled when all are, or breached at the deadline.
Cryptographically verifiableApplication-enforced - EventsUses preview features
Event pass and redemption
An attendee holding the event pass DigiAsset gets a DigiPass for entry. The pass is redeemed when the attendee burns it or the organiser checks them in; either fulfils the agreement.
DigiAsset-indexer-enforcedCryptographically verifiableApplication-enforced - LicensingUses preview features
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.
Application-enforced - Governance
Multi-party approval agreement
A proposal is approved when any two of three approvers sign an approval with their own wallets. It lapses if not approved by the deadline.
Cryptographically verifiableApplication-enforced
More templates
- Commerce
Payment by deadline
The payer pays at least an amount of DGB to an address named in the terms before the contract expires.
Application-enforced - CommerceUses preview features
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.
DigiAsset-indexer-enforcedApplication-enforced - WorkUses preview features
Proof of delivery
The supplier anchors a delivery document's fingerprint; on proof the contract is fulfilled and both get a certificate.
Application-enforced - Other
Start from scratch
One party and a deadline. Add your own conditions and rules.
Cryptographically verifiableApplication-enforced
What the badges mean
- 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.
Simulation only: the template moves value (a DigiAsset or DGB transfer). Financial execution has no production approval, so on mainnet such a contract can be drafted and simulated but never executed. Preview: part of the agreement and simulated, but monitored or performed in a later release; parties are told before signing.