⚠️ 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.
Verify a contract
Check one exact contract version: its hash, every party's signature, and what has happened since. No sign-in needed.
Verify without trusting Contracts
- Download the evidence bundle from the verification page (or
GET /api/contracts/v1/verify/<hash>/evidence). - Check it on your own computer with the original Contracts standalone verifier (
verify-evidence, built from the original Contracts source; it uses the same verification code as this site), optionally against your own DigiByte node:node verify-evidence.mjs bundle.json --rpc http://127.0.0.1:14022
- The verifier recomputes the document hash (RFC 8785 canonical JSON), re-checks every signature and approval, the agreement statement, anchors on your node, drand reveals, and the hash-chained event and evaluation logs. It does not ask Contracts anything.
- 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.