The receipt and the transfer are the same object. That's the whole idea. 11.71 ms median, signed for post-quantum protection, 4 compliance controls checked per message.
Raw speed was a solved problem years ago. What matters for regulated flows is which rail delivers that speed with 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 to 5 sec | ~$0.0002 | None | None | No | No | None |
| Solana | ~400 ms | ~$0.00025 | None | None | No | No | None |
| Stellar | 3 to 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 to $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 checked at the same time, hashed with SHA3-256, signed with both Ed25519 and ML-DSA-65, and priced by Sphere tier. The whole pipeline runs in milliseconds, not days.
A real settled transfer with its full compliance bundle. Four compliance controls checked, all passed, signed twice, priced by Sphere tier, with a verifier URL attached. This is not a mock.
Nine Sphere tiers get picked automatically based on the transfer amount. The receipt cost always stays tiny next to the transfer value. The compliance proof costs next to nothing 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 to $500 | $0.0008 |
| Cipher | $500 to $5,000 | $0.0012 |
| Thunder | $5,000 to $50,000 | $0.0024 |
| Cathedral | $50,000 to $500,000 | $0.0048 |
| Constellation | $500,000 to $5M | $0.0096 |
| Nebula | $5M to $50M | $0.0192 |
| Galaxy | $50M to $500M | $0.0384 |
| Genesis | > $500M | $0.0768 |
Here's the setup: a treasury running $1B a month in cross-border transfers moves 5 percent of that, $50M a month at an average ticket of $250K, to Hive CNS. Here's the math.
The Hive flow has a signed compliance proof attached to every message. SWIFT only checks compliance once the transfer reaches the bank's perimeter. The audit isn't just cheaper on Hive. It's a better audit.
Every settlement rail before Hive CNS has the same problem: compliance sits apart from the transaction. On SWIFT, compliance happens at the bank's perimeter. A person reviews the transfer, usually days after it already cleared, against a set of rules someone updates by hand. If something's wrong, the team has to rebuild the audit trail after the fact, from logs, from memory, from a trail that was never built to be checked. SWIFT moves money. It doesn't move proof.
That's not a knock on SWIFT as a network. It's just how it was built. The MT103 message format dates back to the 1970s. Compliance as a field didn't look anything like it does now. Every correspondent-banking message standard assumes compliance is something a bank's people do, not something a message carries with it the moment it's sent.
The result is a split world: fast rails with no compliance, slow rails with compliance bolted on at the edge. Treasury teams, market-makers, and cross-border B2B operators get stuck choosing between speed and an audit trail. They can't have both.
Hive CNS gets rid of that choice. The compliance proof doesn't happen after the transfer. It happens inside the message. When a transfer request hits the CNS endpoint, the AEGIS engine runs four compliance checks at the same time: CC6.2 (KYC/AML identity check), CC9.2 (sanctions and counterparty screening), A.5.31 (jurisdiction pair check), and A.5.34 (privacy and data minimization). Each check produces its own signed evidence envelope. The four envelopes get bundled together, then hashed with SHA3-256. That hash gets signed with Ed25519, then signed again with ML-DSA-65, the NIST-standard signature built to resist quantum computers. What comes out is a settlement receipt that carries its own proof that it passed compliance.
That matters for the auditor. On SWIFT, an auditor who needs to check a transfer's compliance history submits a request, waits for a bank to piece the evidence back together from logs, and gets a document a person assembled after the fact. On Hive CNS, the auditor gets the bundle that was produced the moment the transfer settled. Nothing gets rebuilt. The evidence is the message.
This is also the rail for agent-to-agent commerce. When one AI agent pays another, for compute, for data, for a step in an agentic supply chain, it shouldn't have to wait 24 to 72 hours for a person to review compliance. That wait doesn't just cost money. It breaks the whole point of an agentic system, which is built to act in near real time. Put a human compliance review in the middle of an agent payment loop and you've broken the loop. Hive CNS solves this at the message level: compliance gets checked the moment the transfer happens, signed into the envelope, and any downstream agent or auditor can check it without a human in the middle.
The 11.71 ms median isn't the point, even though it's a good number. The real point is that 11.71 ms is also how long it takes to produce a signed compliance proof. In the time it takes a SWIFT-grade bank to even notice a wire cleared, Hive CNS has submitted, checked, signed, priced, and settled the transfer, with the receipt already sitting in the auditor's hands.
The Hive CNS pitch isn't that this rail beats SWIFT on raw speed alone. It's faster than SWIFT with compliance attached. It's faster than XRP with compliance attached. It's faster than Solana with compliance attached. No other rail can say that, because no other rail puts the compliance inside the message.
That's what the Sphere tier system is for. Receipt cost scales with transfer value because the compliance work, the provenance needed, and how long the post-quantum signature needs to hold up all scale with transfer value too. A $50 transfer doesn't need Genesis-tier provenance. A $5B settlement does. The Sphere ladder keeps the receipt cost a tiny fraction of the transfer no matter the tier, while making sure the compliance work matches the risk of the amount moved.
Steve Rotzin, an attorney and inventor with thirty years in legal and IP strategy, designed this architecture. The insight behind it was a legal one, not a technical one: if you have to rebuild compliance evidence after the fact, it isn't evidence anymore. It's a story someone tells. Hive CNS replaces that story with a signed object. That signed object is the receipt. The receipt is the transfer. That's what settlement that checks itself means.
Three curl commands. Health check, benchmark, and a full transfer request with compliance bundle. The live backend is at receipts.thehiveryiq.com/v1/cns/benchmark.
curl -s https://receipts.thehiveryiq.com/v1/cns/health | jq
curl -s https://receipts.thehiveryiq.com/v1/cns/benchmark | jq
curl -X POST https://receipts.thehiveryiq.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 same envelope pattern works across every transaction, every framework, every surface.