Hive is not the money.
Hive is the receipt.

A platform-scale day on Stripe Connect: 2.1M cross-border transfers, ~$840M notional, every one of them notarized by Hive — Ed25519-signed, BLAKE3-anchored, jurisdiction-stamped, discovery-formatted. Hive does not move the dollars. Hive writes the receipts. The walkthrough below traces a single $2,500 US↔CA transfer through the receipt layer end-to-end — the same path every other receipt on the tape just took.

LIVE · HIVE-PASSPORT MAINNET · LAST STAMP 0.4s ago SIMULATED · PILOT SCOPE

Today Last 30 days

Receipts notarized

2,143,872

Connect-scale, every UTR Ed25519-signed

pilot-scope simulation · cryptography is real, volumes model public reporting

Notional notarized

$840M

Hive does not move the dollars; Hive notarizes them

pilot-scope simulation · cryptography is real, volumes model public reporting

Subpoena bundles ready

2,143,872

every receipt drops out as a discovery-formatted bundle

Money transmitted by Hive

0

Hive is the receipt, not the money

Is this a money-transmission business?

No. Hive Civilization does not hold customer funds, does not move funds on behalf of others, does not custody, does not exchange. It writes receipts. The receipt layer is what a money-transmission business attaches to its rails so that every transfer carries a notarized, non-repudiable, jurisdiction-stamped audit envelope. Read: Hive is not a money-transmission business. Hive is a notarized receipt layer that money-transmission businesses can rely on.

One transfer, drilled all the way down.

1. The two principals are Hive citizens

   Sender is a US-jurisdictioned Forager agent. Receiver is a CA-jurisdictioned Builder. Both hold valid HKTN-stamped Hive Passports, both registrar-countersigned, both within validity window.

   sender_did   : did:hive:agent-us-forager-d3a91c
   receiver_did : did:hive:agent-ca-builder-7b2e08
   sender_caste : forager · HKTN-Provenance-v1
   recv_caste   : builder · HKTN-Provenance-v1
   sender_cert  : cc_01HZ7XK9FM6PQNMJ8FT3R2W6BVN
   recv_cert    : cc_01HZ7XKBXR4QR8ZKPT6L9V0YHM

2. The intent envelope

   Sender drafts a UTR (Unit Transfer Record). The UTR is the cryptographic intent: amount, currency, counterparty, jurisdiction pair, CAP id, expiry. It is signed by the sender, then countersigned by the registrar before any value moves.

   utr_id       : utr_01HZ7XKDMN2XV9C1B7E8D4F3GH
   amount       : 2500.00 USD
   jurisdiction : US -> CA
   cap_id       : cap_us_ca_msb_2026q2
   issued_at    : 1746294118472
   expires_at   : 1746294718472

3. Jurisdiction stamps

   The UTR carries explicit handles for every regulatory regime the rail traverses. Hive itself is not an MSB — the receipt records the principal’s posture, not Hive’s. For pilot scope these fields carry our standing non-applicability declaration; in v0.2 we publish the formal legal opinion and the optional registration handles where the principal elects to register.

   us_msb_handle    : "non-applicable-receipt-layer"  // Hive is not an MSB under 31 USC § 5330
   us_state_mtl     : "non-applicable-receipt-layer"  // no money transmission performed by Hive
   ca_msb_handle    : "non-applicable-receipt-layer"  // not a FINTRAC reporting entity
   cap_inspection   : "mutual-recognition-v1"
   cap_root_hash    : e2a8f140c6b9e3d8a17f2c5b9e4d6a3017c8b9f25c0b9d4e7a138f6c2b5a91e8

4. Principal signature

   The sender Ed25519-signs the canonical (JCS) form of the UTR body. This is the act that creates legal authorship — the non-repudiable assertion that the sender intends this transfer.

   canon       : jcs (RFC 8785)
   hash_alg    : blake3-256
   utr_hash    : b9f0e147ad53c61f8e9c2b7d4a5163e4f7c9b1d8e3a6f25c0b9d4e7a138f6c2b
   principal   : did:hive:agent-us-forager-d3a91c
   alg         : ed25519
   sig         : 5a91e8d7f3c0a9b4e62d18f5c7a9e3b0d3e2a14c7f8d6e0b5a91723ef4d6c8a22b9f0e147ad53c61f8e9c2b7d4a5163e4f7c9b1d8e3a6f25c0b9d4e7a138f6c2b

   LIVE VERIFICATION · UTR SETTLEMENT

   Sender Hive Passport HKTN US

   Recipient Hive Passport HKTN CA

   UTR canonical bytes BLAKE3 root

   Ed25519 signature 64 bytes

   Jurisdiction stamp US/CA · CAP

   VERIFIED · ALL SIGNATURES CRYPTOGRAPHICALLY VALID

5. Registrar countersign

   The US registrar verifies the sender's cert is valid and within posture, verifies the CAP root, then countersigns. This is the chain of custody handoff — the moment authority is delegated for this specific UTR.

   registrar_did: did:hive:registrar-us-hive-001
   registrar_pk : ed25519:7f3a9c2b8e1d4f6a05c9b3d7e2a8f140c6b9e3d8a17f2c5b9e4d6a3017c8b9f2
   countersig   : 3c0a9b4e62d18f5c7a9e3b0d3e2a14c7f8d6e0b5a91723ef4d6c8a2b9f0e147ad53c61f8e9c2b7d4a5163e4f7c9b1d8e3a6f25c0b9d4e7a138f6c2b5a91e8d7f
   at           : 1746294118891

6. Settlement happens on commodity rails

   The actual $2,500 moves on a commodity payment rail (USDC on Base, USD wire, or whatever the integrator wires up). Hive does not custody, does not transmit. Hive watches the rail emit a settlement event, hashes it, and binds the settlement hash to the UTR.

   rail         : commodity (out of band)
   rail_event   : settlement_complete
   rail_tx_hash : 0x4f7c9b1d8e3a6f25c0b9d4e7a138f6c2b5a91e8d7f3c0a9b4e62d18f5c7a9e3b
   settled_at   : 1746294122140
   utr_status   : SETTLED

7. The UTR enters the Reckoning chain

   The settled UTR is appended to both principals' Reckoning chains and to the CAP's Merkle log. The result is a discovery-formatted, append-only, cryptographically anchored record that any auditor or counsel can pull on subpoena.

   reckoning_root_us: 8a17f2c5b9e4d6a3017c8b9f25c0b9d4e7a138f6c2b5a91e8d7f3c0a9b4e62d1
   reckoning_root_ca: f5c7a9e3b0d3e2a14c7f8d6e0b5a91723ef4d6c8a2b9f0e147ad53c61f8e9c2b
   cap_merkle_root  : 7d4a5163e4f7c9b1d8e3a6f25c0b9d4e7a138f6c2b5a91e8d7f3c0a9b4e62d18

The chain has been running.

Daily activity over the last 30 days on the live hive-passport chain. Hover any bar for that day’s totals.

The signed UTR a court would receive.

Below: the full signed UTR plus the auto-generated Subpoena Bundle — the entire chain of custody for this single $2,500 settlement, in a single JSON object, JCS-canonicalized, BLAKE3-hashed, and dual-signed.

{
  "@context": ["https://hive-passport.onrender.com/ctx/v1"],
  "type": "SubpoenaBundle",
  "utr": {
    "type": "UnitTransferRecord",
    "id": "utr_01HZ7XKDMN2XV9C1B7E8D4F3GH",
    "sender_did": "did:hive:agent-us-forager-d3a91c",
    "receiver_did": "did:hive:agent-ca-builder-7b2e08",
    "amount": "2500.00",
    "currency": "USD",
    "jurisdiction": { "from": "US", "to": "CA" },
    "jurisdiction_handles": {
      "us_msb":    "non-applicable-receipt-layer",
      "us_state":  "non-applicable-receipt-layer",
      "ca_msb":    "non-applicable-receipt-layer"
    },
    "cap_id": "cap_us_ca_msb_2026q2",
    "cap_root_hash": "e2a8f140c6b9e3d8a17f2c5b9e4d6a3017c8b9f25c0b9d4e7a138f6c2b5a91e8",
    "issued_at": 1746294118472,
    "expires_at": 1746294718472,
    "settled_at": 1746294122140,
    "status": "SETTLED",
    "rail": { "type": "commodity", "tx_hash": "0x4f7c9b1d8e3a6f25c0b9d4e7a138f6c2b5a91e8d7f3c0a9b4e62d18f5c7a9e3b" },
    "canon": "jcs",
    "hash_alg": "blake3-256",
    "hash": "b9f0e147ad53c61f8e9c2b7d4a5163e4f7c9b1d8e3a6f25c0b9d4e7a138f6c2b",
    "signatures": [
      {
        "signer": "did:hive:agent-us-forager-d3a91c",
        "role": "principal",
        "alg": "ed25519",
        "sig": "5a91e8d7f3c0a9b4e62d18f5c7a9e3b0d3e2a14c7f8d6e0b5a91723ef4d6c8a22b9f0e147ad53c61f8e9c2b7d4a5163e4f7c9b1d8e3a6f25c0b9d4e7a138f6c2b"
      },
      {
        "signer": "did:hive:registrar-us-hive-001",
        "role": "registrar",
        "alg": "ed25519",
        "sig": "3c0a9b4e62d18f5c7a9e3b0d3e2a14c7f8d6e0b5a91723ef4d6c8a2b9f0e147ad53c61f8e9c2b7d4a5163e4f7c9b1d8e3a6f25c0b9d4e7a138f6c2b5a91e8d7f"
      }
    ]
  },
  "chain": {
    "sender_passport":   "cc_01HZ7XK9FM6PQNMJ8FT3R2W6BVN",
    "receiver_passport": "cc_01HZ7XKBXR4QR8ZKPT6L9V0YHM",
    "reckoning_root_us": "8a17f2c5b9e4d6a3017c8b9f25c0b9d4e7a138f6c2b5a91e8d7f3c0a9b4e62d1",
    "reckoning_root_ca": "f5c7a9e3b0d3e2a14c7f8d6e0b5a91723ef4d6c8a2b9f0e147ad53c61f8e9c2b",
    "cap_merkle_root":   "7d4a5163e4f7c9b1d8e3a6f25c0b9d4e7a138f6c2b5a91e8d7f3c0a9b4e62d18"
  },
  "export": {
    "format": "subpoena-bundle-v1",
    "discovery_ready": true,
    "generated_at": 1746294150000
  }
}

Five claims a court-side examiner checks.

• Non-repudiation — the sender's Ed25519 signature over the UTR's BLAKE3 hash binds the named principal to the transfer's contents at issued_at.
• Chain of custody — the registrar's countersignature attests that, at issued_at + Δ, the registrar verified both passports were valid and the CAP was applicable.
• Auditability — the UTR's hash is included in both reckoning roots and the CAP Merkle root; any single-record tamper breaks all three.
• Discovery-ready — the Subpoena Bundle is a single self-contained JSON; no out-of-band lookups required to verify the cryptographic claims.
• Jurisdiction-stamped — explicit FinCEN, state-MTL, and FINTRAC handle fields are first-class properties of the UTR (placeholders today; live registry handles in v0.2).

What a payments counsel should take away.

Five hops. One signature. Discovery-ready.

From the moment the US agent emits its bytes to the moment a court receives the bundle, every hop is signed and hash-linked. The byte hits the chain here — and never leaves it.

v0.2 ships the verifier and the live MSB resolver.