Tusculum uses the open-source TODA protocol to move the trust boundary from the network to the data object itself. The first defense application is logistics: replacing paper hand receipts, fuel logs, and supply-chain records with tamper-evident digital assets that remain verifiable without connectivity.
Every TODA object carries its own cryptographic proof of integrity, provenance, and authorization, enabling local verification and policy enforcement without dependence on centralized infrastructure.
The drop zone below demonstrates the TODA verification workflow — the same process that would apply to any TODA-wrapped document in a production deployment. Drop any file to see an illustrative verification result. Nothing is transmitted. No connectivity required.
TODA's offline-first architecture was engineered for environments where connectivity cannot be assumed. Logistics is the first application; the same object-centric controls extend to documents, mission data, and other operational assets.
Zero Trust means never trusting something because of where it sits. Conventional implementations pursue that by gating the network — every request routed to a policy server that decides who may connect. That model assumes the policy server is reachable. In denied and degraded environments, it isn't.
TODA reaches the same objective from the opposite direction. Every capability described above already operates on a Zero Trust basis, because the trust boundary sits on the data object rather than on the network. A TODA hand receipt does not trust the device holding it, the network that carried it, or the person presenting it. It carries its own proof, and any recipient verifies that proof locally — offline, on any device, with no server to ask. Logistics integrity in denied environments and Zero Trust data control turn out to be the same engineering problem, and TODA was built to solve it from the asset side.
Reference information about Tusculum Technology and the TODA protocol, stated directly for evaluators, partners, and anyone verifying claims made elsewhere.
The following scenarios illustrate how TODA would function across common defense logistics and accountability challenges. These are representative use cases, not deployed implementations. Tusculum is seeking qualified evaluation partners.
| Cryptographic Digest | SHA-2 (SHA-256) |
| Signing Algorithm | ECDSA · curve configurable (P-256 / P-384 for federal use) |
| Transfer Cost | < $0.01 per transaction |
| Settlement Time | < 60 seconds |
| Connectivity Required | None · fully offline capable |
| Verification Method | Local · device-only · no server |
| Transfer Modes | IP · Bluetooth · USB · SD card |
| File Size (proof) | < 10 kb per transfer |
| Throughput (design capacity) | 1M transactions / hour |
| Fragmentation | Native · sum always equals original |
| Tamper Detection | Immediate · any field alteration |
| Database Required | No · asset is the record |
| Blockchain Required | No · ledgerless file protocol |
| Hardware Requirement | Any device · GFE compatible |
| Research Origins | Cambridge CRDC · UCL · ARM · 2017 |
| Classification | UNCLASSIFIED · CUI capable |
Tusculum builds on the open-source TODA protocol, whose mathematics originated in published research at Cambridge CRDC, UCL, and ARM. We are seeking qualified defense and government organizations to participate in evaluation and pilot programs. Contact us to discuss your operational requirements.