How TODA works.

TODA is a ledgerless file protocol: the file itself is the proof. No chain to consult, no database round-trip, no batch reconciliation. ADOT, its application-layer companion, gives the objects inside TODA files their meaning.

Co-developed with Cambridge CRDC, UCL, and Arm.

twintwintwinthe proof travels with the file

Two protocols.

TODA keeps the file whole. ADOT says what is inside it.

01File layer

TODAThe file protocol.

Rigging gives a file portable integrity at a distance. A TODA file carries its own proof, so its integrity holds wherever its state is managed.

02Application layer

ADOTThe application-layer protocol.

Just as HTTP is an application-layer protocol, ADOT defines how to create, update, serialize and interpret ADOT objects, called abjects. Abjects provide the meaning inside TODA files.

ADOT objects live inside TODA files: the meaning travels with the proof.

We solved what blockchain couldn't.

Five properties, built into the file layer.

01

Digital ownership without intermediaries

Bearer files, transferable like cash, recoverable via delegated custody.

With blockchainLose the seed phrase, lose the asset.

02

Instant settlement

Atomic in the request. Under 100 ms.

With blockchainBlock time plus confirmations. Seconds, not milliseconds.

03

Cheap micropayments

Settle amounts as small as $0.001. No minimum, no gas.

With blockchainGas can exceed the payment itself.

04

Self-verifying assets

The file is the proof. Offline-verifiable.

With blockchainVerification needs a live chain to query.

05

Audit and compliance

Cryptographic lineage in the file itself.

With blockchainAudit by scraping every onchain transaction.

A rail for software, in three moves.

All at the file layer: no blockchain, no card rail, no billing cycle.

01Move 1 of 3

Twin micro-apps power APIs, AIs, and agents.

Every wallet, API, AI, and agent gets its own dedicated Twin, handling payments, payouts, verification, access, records, and banking, all in one HTTP container.

wallettwinAPItwinAItwinagenttwinpayments · payouts · verification · access · records · banking
02Move 2 of 3

Six operations, one round-trip.

Inside the Twin: price the call, sign the request, verify the payment, split the proceeds, settle the recipients, bind the proof in the file. No external service runs in between.

buyertwinsellertwinpricesignverifysplitsettlebindone round-trip
03Move 3 of 3

Payouts to up to 200 recipients.

The split branches into a real distribution graph: providers, platforms, creators, treasuries, charities. Splits inside splits. Every recipient paid in the same network round-trip. No escrow, no payout queue, no reconciliation job.

Platform and creatorOne payment splits to provider, platform and creator, with splits inside splits.
paymentsplitproviderplatformcreatorsplits inside splits
Supply chainOne payment is paid down a supply chain, with a programmable split at every hop.
paymenthop 1hop 2hop 3hop 4buyerretailerbrandmanufacturerlogisticscomponentsassemblyraw materialspackagingprogrammable split
Data partnersA company builds a tailored service on its partners' data APIs. Each sale is split among the companies whose data contributed.
customercompany atailored serviceapicompany bapicompany capicompany d1 · the service pings partner data apis2 · customer pays for the augmented service3 · each sale is split among the data partners
Beyond payments

Trace physical goods, end to end.

A physical good can carry its own TODA file. Every handover, from source to factory, shipping, warehouse and store, adds a record to that file, so anyone downstream can verify where a product came from and who held it along the way.

sourcefactoryshippingwarehousestoreitem fileone record per handoverprovenance verified
Verify any transaction.
The file is the proof.

Every TODAQ transaction carries its full cryptographic lineage in the file itself. Paste a hash and verify integrity offline. No chain, no database round-trip.

lineage, checked link by linkverified offline