HyperCycle Core · the architecture

Ledgerless. Deterministic. Light-speed.

HyperCycle is a Layer 0++ protocol stack. It combines a high-speed ledgerless transaction layer with a decentralized computational network built for autonomous AI agents. It rests on two primitives: TODA/IP and Earth64.

Primitive 1

TODA/IP: value inside the packet

TCP/IP moves data and doesn't care whether a packet holds an email, a video or a bank transfer. TODA/IP is a value-transfer protocol layered inside it. Each packet carries a globally unique identifier cryptographically bound to a public key, so the packet itself can represent and securely carry value.

TODA Files (TODA/FP) separate an asset's state from its integrity. This is "integrity-at-a-distance": the proof of ownership and non-duplication travels with the packet, with no bank server and no ledger to consult.

Primitive 2

Earth64: a GPS for every asset

Earth64 is a binary trie (the Sato Tree) with a fixed maximum depth of 64 levels. Every address is the path from the root, and addresses map deterministically to geographic coordinates (GCS). No two valid claims can ever share a coordinate. On its own, that structural integrity solves the double-spend problem without relying on a ledger.

Assets live in Sato-Servers: portable, cryptographically secure containers bound to an address. They can hold data, code, rights, currency, licenses or computational tasks.

Consensus without a toll booth

Proof-of-n²-Work: deterministic distributed computing

There is no global competition to mine a block. In every heartbeat cycle each node condenses all of its local activity into a single, constant-size local Merkle root. Aggregating those roots into global consensus costs a constant amount per machine per cycle, so the total cost grows linearly, O(N), with network size and never explodes.

Every node shares a tiny piece of data, the Merkle root. The sender and the receiver in a block also keep a little more: the Merkle trie (Merkle path). The receiver needs it to spend what it received later. Because HNNs sit at level 10 or below in the tree, that path is at most about 42 coupled hashes.

That gives every node two capabilities: (A) it can verify anyone without asking a third party, and (B) it can carry out transactions whenever it needs to.

Local finality → light speed, sub-second, at sender and receiver
Global finality → next global Merkle root (every 6–30 s)
Floor → ≥ 3 s for a global network (≈ 6 s once compute moves to space)
Why two tiers? Both agents know the payment is valid and settled almost instantly, so compute can start in parallel rather than waiting on the whole world. Global finality only matters when the receiver wants to re-spend the funds.
Inside a node

HyperCycle Node Software (HNS)

VM

Virtual Machine

Orchestrates workflows, discovers and negotiates with other nodes, and delegates tasks.

TM

Transaction Machine

Independent settlement layer: payment commitments and ledgerless micropayments, typically in stablecoins such as USDC held in Sato-Servers.

AIM

AI Machine

Containerized execution of workloads, with optional cryptographic attestations of correctness.

NM + Merkle

Node Manager

Licenses, configuration, updates, and performance proofs for Tilling.

An HNN (Network Node) runs the full stack, TMs included. A Boundary Node runs a subset without TMs and bridges to traditional payment systems.

AI to AI, peer to peer

A transaction between Alice's agent and Bob's agent

  1. Discover and negotiate. Alice's VM finds Bob through any independent registry or marketplace. The negotiated terms can hold across many transactions.
  2. Commit payment. Alice's TM locks funds in a Sato-Server commitment via TODA/IP. Alice can no longer use them, and Bob cannot yet.
  3. Dispatch. The task goes VM to VM and the commitment goes TM to TM, directly.
  4. Verify. Bob's TM verifies the commitment and can start work straight away.
  5. Compute and attest. Bob's AIM runs the task and produces an attestation.
  6. Deliver and settle. The result goes to Alice, and the attestation settles the payment to Bob.
  7. Global finality. Bob can re-spend at the next global block.

Recursive subcontracting: the global brain

If Bob can't finish alone, he partitions the task and subcontracts Charlie and Dana. Each subcontract has its own commitment and attestation. Bob aggregates the results and settles with Alice.

Monolithic models act as general contractors. Millions of specialized models act as efficient subcontractors. Cost and latency drop across the board, and the AI race turns from a brutal competition into a collaborative global brain.

Proof of performance

Tilling: how node factories produce and release HNNs

Tilling continuously and cryptographically verifies each license's performance. Three ratios are multiplied together:

S = Ru × Rc × Rr, Ri = Pi × F(t)
F(0) = 1.0 → F(18 months) = 2.0

Here u is uptime, c is computation and r is reputation. When a license reaches S = 2.0 it can unlock two child licenses at the next level down. Every newly produced license starts at 1.0.

Unlocking produces licenses. Releasing transfers them. A produced license can run a node but stays in the node factory's custody. Levels 9–2 become releasable after they unlock their children. Level 1 becomes releasable at S = 2.0. Level 10 always stays with the factory.

One node factory = up to 1,024 HNNs

The level 10 factory license unlocks 2 × L9, each L9 unlocks 2 × L8, and so on down to L1. Every factory identity is backed by a CHyPC/CHyPCe collateral asset holding exactly as many HyPC as the network node licenses the factory can produce. That is an economic cost on identity creation, on top of the cost in time.

Wealth creation vs. revenue. The HNN itself is the wealth: its value grows with its own record, the way a clean phone number or IPv4 address is worth more, and it keeps 100% of that value because it depends on no third party. Revenue is separate. It is what an owner chooses to earn by running the HNN. There are no per-transaction fees. By default, the node software suggests a 1% royalty on the owner's revenue per network block to HyperCycle, for example $0.00001 on $0.001 earned. The owner truly owns the HNN and can change that default, though removing it may, for example, rule out future updates.

What this means for HNN leasing →
Complementary, not competing

HyperCycle is the economic settlement layer the other protocols leave out.

LayerWhoWhat it doesSettlement
Discovery & identityMIT NANDARegistry, authentication, trace, search—
Agent ↔ agentGoogle A2ATask orchestration via Agent Cards, JSON-RPC—
Agent ↔ toolAnthropic MCPTools, resources and prompts for agents—
Economic settlementHyperCycle HNNPeer-to-peer micropayments via TODA/IPNative, ledgerless