TODA gives any digital asset — a payment, a credential, a license — integrity that travels with it. The asset's full, tamper-proof history is sealed inside the file and verifiable by anyone, instantly and offline. No database to query. No ledger to join. With ADOT, the file carries not just proof but meaning: what it is, what it's worth, and what it can do.
A cryptographic signature proves a specific party vouched for a specific set of bytes and that nothing has changed since. For most things that is enough. But once an asset has real value, a signature is silent on three questions:
The usual workaround keeps the authoritative state on a server consulted at verification time — a database or a blockchain. It works, but the asset's integrity now lives on someone else's always-online infrastructure. If that server is unreachable or retired, so is the proof.
TODA closes those gaps and keeps the answer inside the file. Every asset carries its own complete history plus a guarantee that the history is unique, so the proof goes wherever the file goes.
TODA proves a file is genuine and one-of-a-kind. ADOT is the second half of the technology: the layer that stamps meaning into the verified file — a value, an ownership right, a capability — enforced by the same cryptography that secures the file, so it can't be forged or inflated any more than the file itself can. TODAQ calls these self-contained units of meaning abjects. They turn a trustworthy file into a working asset: a banknote, a share, a ticket, a deed, a licence.
An agent twin (buyer) transfers a 1.00 USD-TDN TODA file to an API twin for a NAV lookup on Ivanhoe Mines. On receipt the file splits into two TODA files — one worth $0.90 (net revenue), one worth $0.10 (supply chain) — which always sum back to the original 1.00. Value is conserved, settled atomically, with no invoice to reconcile. USD-TDN redeems 1:1 for US dollars.
| Property | Signature alone | Blockchain / ledger | TODA|ADOT |
|---|---|---|---|
| Proves it's authentic & unaltered | Yes | Yes | Yes |
| Proves it's the only copy | No — copies are equally valid | Yes, via global consensus into the chain | Yes, proof of uniqueness sealed in the file |
| Establishes one canonical history | No — a key can sign forks | Yes | Yes |
| Verifies with no network | Partly — can't prove uniqueness | No — needs a node or query | Yes — fully offline |
| No shared ledger to join or sync | Yes | No | Yes |
| Cost to transact | Negligible | Gas fees | Negligible |
| Settlement | Instant but incomplete | Block time | Instant |
| Where integrity lives | In the bytes (only partly) | In the global chain | In the file itself |
| Carries what it's worth (value conserved on transfer) | No | Partly — needs a token standard / contract | Yes — quantity sealed in the asset |
| Owner can grant or sub-license rights | No | Partly — via smart contract | Yes — delegation built in |
| Self-describing meaning any app reads alike | No | Partly — off-chain metadata | Yes — typed fields inside the file |
TODA and ADOT run live products. Twin provides the hosted machinery, Qatom puts ADOT's value layer to work for agent payments, and the stack is commercialized across entertainment, finance, and healthcare.
TODA's guarantees only hold if an asset's proof stays current as it is issued and changes hands. A Twin is a hosted, contained environment that manages TODA assets and maintains their proofs on your behalf, with no infrastructure to run. A Twin can be configured as a paywall: paid content unlocks only on receipt of payment in TODA assets, where the asset is both the payment and the receipt — single-use, verifiable, and impossible to double-spend, with nothing to reconcile afterward.
Agents and APIs need to pay each other per call, instantly, with no accounts, no gas, and no pre-funded relationship. Qatom carries TODA payment in the request itself, so an endpoint can be metered and settled per call, atomically. The payment verifies locally; there are no invoices, chargebacks, or minimums.
A blockchain is one enormous chain that everyone shares; to trust any single entry you rely on the whole network agreeing about all of them. TODA inverts that. Each asset is its own small, linear chain — a private history of just that one thing, from creation to the present.
A lone chain could be forged or forked, so its integrity is ensured by a hierarchy of aggregating chains above it. Each higher chain periodically gathers many asset-chains and seals their current state into a single entry, the way a notary's logbook fixes a document in time. Layer binds to layer, up to a root.
Because an asset's latest state is bound upward into that hierarchy, it cannot be quietly rewritten or duplicated: doing so would force an authority above it to contradict itself, which the structure makes detectable and the mathematics makes provable. Because the slice of the hierarchy covering the asset is bundled into the file, anyone can replay the proof offline without contacting the issuing authority.
The services that run these aggregating chains are called relays. A relay's only job is to keep its chain honest and append-only; it never holds the asset or sees its contents. You verify against what a relay has published; you do not trust the relay with anything. Structurally: many assets (one chain each) aggregate through relays up to a single root that anchors all of them, and the slice from an asset up to the root rides inside the file.
Co-developed with Cambridge CRDC, UCL, and ARM. The protocol's specifications are maintained as living documents, with formal proofs behind the no-double-spend guarantee. Papers are co-authored by Dann Toliver (TODAQ CSO, CRDC co-founder) and Adam Gravitis (TODAQ CTO). The ADOT meaning layer is defined in "ADOT Objects: Units of meaning in the world of rigging" (Gravitis).
Primary sources: