TODA/IP

P2P Protocol

Ledgerless P2P communication and value-transmission protocol operating at the network packet level. Each TODA packet (Sato-Server) is a self-contained cryptographic unit embedding proof of ownership, enabling serverless asset transfer without miners, global ledgers, or third-party dependencies. Uses deterministic distributed computing (DDC) as proof-of-work and achieves global consensus via periodic Merkle root publication every 6–30 seconds. Primary infrastructure for HyperCycle.ai's Internet of AI (IoAI).

Company
Links
Visit Community

Details

License Partial — whitepaper public (CC BY-SA 4.0); core implementation proprietary; HyperCycle components on GitHub
Dev Status 🟢 Active
Dev Status Detail Production — V1.0 deployed across TodaQ, Land32, YouBase, Records.OT and others; V2.0 in academic research collaboration; V3.0 being implemented by HyperCycle.ai
Owner Toda.Network Corp; co-authored by Toufi Saliba and Dann Toliver
Country USA
Start Year 2017
Stack Rust (HyperCycle V3.0 implementation); C/C++ (early implementations)
Funding Unfunded / bootstrapped
Last Investigated Jan 15, 2026

Use Case Domains

Platform Evolution & Sovereignty Identity & Trust Group Formation & Governance

Affordances

Sovereign identity

P2P Protocol Attributes

Origins Organically emerged from research into eliminating third-party dependencies in P2P communication; protocol name coined from co-authors Toufi & Dann (To-Da); no initial intent to create a formal protocol
Database N/A — ledgerless; state managed locally per participant device
Query Language N/A
Data Formats TODA File (Sato-Server packets); Earth64 hierarchical binary tree data structure
Collaborative Live Editing No
Rich Text Editing No
Mobile Support No (device/server-native)
Web Support No (device/server-native)
Native Apps Yes (native node implementations)
Terms CC BY-SA 4.0 (whitepaper); proprietary (core implementation)
Funds N/A
Based On UDP (TODA/IP adds value-transmission layer on top of UDP) ; Earth64 data structure
P2P Architecture Ledgerless P2P — each node maintains local state; geographic distribution of devices required for consensus
Overlay Network Device-local per participant; no global overlay — geographic distribution across the network serves as the distribution model
Content Addressing Yes — each TODA packet has unique global identifier derived from hierarchical binary search-tree (Earth64)
Local-First Yes — no server dependencies; operates entirely from participant devices
E2EE Yes — cryptographic proof of ownership embedded in each packet
CRDTs Lib N/A
Byzantine Fault Tolerance Yes — attack cost exceeds benefit by design; geographic distribution prevents power concentration
Signature Yes — ownership proof cryptographically bound to public key within each packet
Permissions Key-based (ownership proof embedded in packet; bound to single public key)
Semantic Web Compatibility No
Smart Contract No (protocol layer; smart contracts can be built on top via HyperCycle)
Protocol Stack Position Transport-equivalent (packet-level) — designed to coexist alongside TCP/IP as a parallel value-transmission layer, not built on top of it
Asset / Value Embedding Native (packet-level) — each TODA packet IS the asset; cryptographic ownership proof embedded directly in packet structure
Protocol Maturity / Standardization Production / Proprietary Standard — V1.0 in production; not submitted to external standards body