The first rail where the receipt and the transfer are the same object. 11.71 ms median, post-quantum signed, 4 compliance controls audited per message.
Raw finality was won years ago. The question for regulated flows is which rail delivers finality with cryptographically signed compliance proof attached. No other rail does this.
| Rail | Finality | Cost / tx | Compliance attached | Provenance | Post-quantum | Jurisdiction-aware | Per-message audit |
|---|---|---|---|---|---|---|---|
| SWIFT MT103 | T+1 to T+3 | $40+ | None (perimeter) | None | No | Manual | Manual, days |
| XRP / Ripple | 3–5 sec | ~$0.0002 | None | None | No | No | None |
| Solana | ~400 ms | ~$0.00025 | None | None | No | No | None |
| Stellar | 3–5 sec | ~$0.00001 | None (perimeter) | None | No | Memo only | None |
| Base L2 (raw) | ~2 sec | ~$0.0001 | None | None | No | No | None |
| Hive CNS |
11.71 ms off-chain
+ Base L2 anchor (pending)
|
$0.0001–$0.0768 receipt | Per-message bundle (4 controls) | MAPET-X 24-axis | Yes (ML-DSA-65) | Yes (per-control) | 6.5 ms / 158-control fleet 460 ms |
From submission to settled receipt: one request, 4 compliance controls audited in parallel, SHA3-256 hashed, dual-signed with Ed25519 and ML-DSA-65, and Sphere-tiered. The full pipeline in milliseconds, not days.
A real settled transfer with its full compliance bundle. Four compliance controls audited, all passed, dual-signed, Sphere-tiered, verifier URL attached. This is not a mock.
Nine Sphere tiers auto-selected by transfer amount. Receipt cost is always negligible relative to transfer value. The compliance proof is free at any scale that matters.
"Receipt cost is always negligible vs transfer value. A $5B settlement pays $0.0768. That is 0.0000000015 percent."
| Sphere | Transfer threshold | Receipt cost (USD) |
|---|---|---|
| Whisper | < $50 | $0.0001 |
| Echo | $50 – $500 | $0.0008 |
| Cipher | $500 – $5,000 | $0.0012 |
| Thunder | $5,000 – $50,000 | $0.0024 |
| Cathedral | $50,000 – $500,000 | $0.0048 |
| Constellation | $500,000 – $5M | $0.0096 |
| Nebula | $5M – $50M | $0.0192 |
| Galaxy | $50M – $500M | $0.0384 |
| Genesis | > $500M | $0.0768 |
Frame: a treasury running $1B/month in cross-border transfers moves 5 percent — $50M/month at an average ticket of $250K — to Hive CNS. Here is the arithmetic.
The Hive flow has cryptographic compliance proof attached to every message, versus SWIFT's no-proof-until-bank-perimeter. The audit cost is not just lower — the audit quality is structurally superior.
The problem with every settlement rail that came before Hive CNS is the same: compliance is separated from the transaction. In SWIFT, compliance happens at the bank perimeter. A human reviews the transfer — usually days after it cleared — against a set of manually updated rules. If something was wrong, the audit reconstruction happens retroactively, against logs, against memory, against a trail that was never designed to be inspected. SWIFT moves money. It does not move proof.
This is not a criticism of SWIFT as a network. It is an architectural observation. The MT103 message format was designed in the 1970s. Compliance as a discipline did not look the way it does now. The assumption built into every correspondent-banking message standard is that compliance is a bank function performed by people, not a message attribute computed at send time.
The consequence is a bifurcated world: fast rails with no compliance, slow rails with compliance at the perimeter. Treasury teams, market-makers, and cross-border B2B operators are stuck choosing between speed and auditability. They cannot have both.
Hive CNS is the first rail to make that choice unnecessary. The compliance proof does not happen after the transfer. It happens in the message. When a transfer request hits the CNS endpoint, the AEGIS engine runs four compliance controls in parallel: CC6.2 (KYC/AML identity check), CC9.2 (sanctions and counterparty screening), A.5.31 (jurisdiction pair validation), and A.5.34 (privacy and data minimization). Each control produces a signed evidence envelope. The four envelopes are bundled. The bundle is hashed with SHA3-256. The hash is signed with Ed25519 and then signed again with ML-DSA-65, the NIST-standardized post-quantum signature algorithm. The result is a settlement receipt that contains, inside itself, the proof that it passed compliance.
This matters for the auditor. Under the SWIFT model, an auditor who needs to verify a transfer's compliance posture submits a request, waits for a bank to reconstruct the evidence from logs, and receives a document that was assembled after the fact by a human. Under the Hive CNS model, the auditor receives the bundle that was produced at the moment of settlement. There is no reconstruction. The evidence is the message.
This is also the rail for agent-to-agent commerce. An AI agent paying another AI agent — for compute, for data, for services in an agentic supply chain — should never have to wait 24 to 72 hours for a compliance review. The latency is not just expensive. It is architecturally wrong. Agentic systems are designed to act in near-real-time. Inserting a human compliance review into an agent payment loop breaks the loop. Hive CNS dissolves the problem at the message level: compliance is computed at the moment of transfer, signed into the envelope, and verifiable by any downstream agent or auditor without any human intermediary.
The 11.71 ms median is not the point, though it is a good number. The point is that 11.71 ms is also the time it takes to produce signed compliance proof. In the time it takes a SWIFT-grade bank perimeter to detect that a wire cleared, Hive CNS has submitted, audited, signed, tiered, and settled the transfer — with the receipt already in the auditor's hands.
The Hive CNS position is not that this rail is faster than SWIFT. It is faster than SWIFT with compliance attached. It is faster than XRP with compliance attached. It is faster than Solana with compliance attached. No other rail can make that claim because no other rail attaches the compliance to the message.
That is what the Sphere tier system represents. The receipt cost scales with transfer value because the compliance burden, the provenance requirement, and the post-quantum signature durability requirement scale with transfer value. A $50 transfer does not require Genesis-tier provenance. A $5B settlement does. The Sphere ladder ensures the receipt always costs a negligible fraction of the transfer, while guaranteeing the compliance posture matches the risk profile of the amount moved.
The architecture was designed by Steve Rotzin, an attorney and inventor with thirty years in legal and IP strategy. The insight that drove the design was legal, not technical: if compliance evidence has to be reconstructed after the fact, it is not evidence. It is a narrative. Hive CNS replaces the narrative with a signed object. The signed object is the receipt. The receipt is the transfer. That is what settlement that audits itself means.
Three curl commands. Health check, benchmark, and a full transfer request with compliance bundle. The live backend is at hivemorph.onrender.com/v1/cns/.
curl -s https://hivemorph.onrender.com/v1/cns/health | jq
curl -s https://hivemorph.onrender.com/v1/cns/benchmark | jq
curl -X POST https://hivemorph.onrender.com/v1/cns/transfer \ -H 'Content-Type: application/json' \ -d '{ "from_did": "did:hive:treasury:0x15184Bf50B3d3F52b60434f8942b7D52F2eB436E", "to_did": "did:hive:counterparty:0xabc123", "asset": "USDC", "chain": "base-8453", "amount": "250000.00", "purpose": "trade-settlement", "jurisdiction_pair": ["US", "SG"] }' | jq
{
"transfer_id": "cns_49bb822f53c94e7a94ca9896d609aca2",
"status": "settled",
"wall_clock_ms": 11.73,
"off_chain_ms": 11.73,
"compliance_bundle": {
"controls_audited": 4,
"all_passed": true,
"score": 75.0,
"envelopes": [ /* CC6.2, CC9.2, A.5.31, A.5.34 — each with sha3, ed25519, ml_dsa_65 */ ]
},
"settlement_envelope": {
"sha3_256": "2009b21ea2dcc92cf45c5a09411d6a07...",
"ed25519_signature": "zEjn/lJWH9DHABJRNbmUhHgG5MAwX5TT...",
"mldsa65_signature": "RFNBLVNUVUItOWQ3YmFlMWZhOWE5Yjc4...",
"sphere_tier": "Cathedral",
"sphere_cost_usd": 0.0048,
"anchor_chain": "base-8453",
"verifier_url": "https://thehiveryiq.com/verifier/?tx=cns_49bb822f53c94e7a94ca9896d609aca2"
}
}
Hive Civilization believes in disclosing the current state of every system accurately. Here is the full picture for CNS as of Build #39.
The benchmark endpoint is public, live, and runs a real signed transfer every minute. Hit it and see the numbers for yourself. No registration, no rate limit on benchmark reads.
Every Hive surface signs its own evidence with the same primitives: SHA3-256 canonical hashing, Ed25519 + ML-DSA-65 dual signatures, and a published Merkle Mountain Range root. The receipt is the audit evidence. The envelope is the universal generalization — every transaction, every framework, every surface.