Trust is what is provable, not what is promised.
Hive’s trust model is mechanical. Every claim on this page is implemented in code that produces an artifact you can verify yourself — most of them in under a minute, offline, with no Hive endpoint involved.
Six things you can verify without us.
Each block below maps to a specific cryptographic primitive and a specific surface in the platform. There is no honor system.
Receipt verification
Ed25519 signatures from requester, operator, and Hive are verified against SHA-256 anchors of the request and response. Tampering, forgery, or substitution is detected offline. Run it now →
Sealed inspection
Sensitive payloads are sealed at the operator with AES-256-GCM. ViewKey grants are time-bound, scope-bound, and themselves signed receipts. The platform never sees plaintext. Wrong-key authentication fails closed.
Settlement
USDC on Base. Circle-issued contract 0x833589f…A02913. Settlement hash is co-signed into the receipt at close. Hive does not operate this contract and does not custody balances. Treasury receipt: 0x15184Bf…B436E.
Operator attestation
Operators co-sign region, training-region, and hardware-class fields with their own keys. If the operator cannot sign, the route is denied before compute begins. There is no fall-through.
Independence
Hive is neutral by charter. Hive is not a model lab, not a cloud provider, not an exchange, not a recommendation engine. Routing decisions are determined by the requester’s signed policy, not by Hive.
Continuity
Receipts are portable, offline-verifiable artifacts. Verification does not require a Hive endpoint. If Hive is unavailable, every receipt ever issued remains independently verifiable using public keys you have already pinned.
Failure mode. If any primitive above fails to verify — signature, hash, seal, attestation, or settlement — the receipt is treated as invalid and the call is rejected at routing time, before settlement. There is no silent fallback.
Status. Reported plainly.
We will not tag a control as held until it is held. We will not tag a track as live until it is.
| Control | Status | Notes |
|---|---|---|
| Ed25519 signing · 3-of-3 | LIVE | Receipts in production |
| AES-256-GCM payload sealing | LIVE | Operator-side sealing, ViewKey access |
| USDC on Base settlement | LIVE | Circle-issued contract |
| Operator co-signature | LIVE | Region · training · hardware |
| SOC 2 Type I | IN PROGRESS | Readiness assessment under way |
| ISO 27001 readiness | IN PROGRESS | Pre-cert scoping |
| SOC 2 Type II | NOT YET HELD | Will follow Type I |
| ISO 27001 certification | NOT YET HELD | Will follow readiness |
| FedRAMP | NOT YET HELD | Roadmap only |
Hive Standard ships today. Hive-PQ is a pilot premium evidence profile.
Hive Standard uses live classical verification rails today. Hive-PQ is a pilot premium evidence profile for regulated, high-retention workflows. We separate what is shipping from what is in pilot from what is on the roadmap. We do not relabel pilot work as live.
| Capability | Status | Notes |
|---|---|---|
| Ed25519 signed receipts | LIVE | Hive Standard rail, in production |
| SHA-256 / BLAKE3 hash commitments | LIVE | As applicable per receipt profile |
| AES-256-GCM sealed inspection | LIVE | Operator-side sealing, ViewKey access |
| Offline verifier | LIVE | Browser-side, five round-trips |
| USDC on Base settlement reference | LIVE | Circle-issued contract |
| Hive-PQ receipt profile | PILOT | Premium evidence mode for regulated workflows |
| Crypto-agile receipt metadata | PILOT | Algorithm-agnostic envelope structure |
| Dual-signature receipt posture | PILOT | Classical + post-quantum-ready signature metadata |
| SMSH-PQ sealed evidence profile | PILOT | Designed to support ML-KEM / Kyber-class envelopes |
| SHOD-PQ declaration profile | PILOT | Ed25519 today; ML-DSA-ready posture |
| RubricMesh proof-tier selection | PILOT | Per-transaction Standard / Pro / PQ |
| Formal ML-DSA / Dilithium-class signatures | ROADMAP | Not yet implemented |
| Formal ML-KEM / Kyber-class sealed envelopes | ROADMAP | Not yet implemented |
| Independent cryptographic review | ROADMAP | Third-party assessment of PQ profile |
| Post-quantum verifier compatibility testing | ROADMAP | Cross-implementation verifier suite |
Verify a receipt now.
The reference verifier runs in your browser. Five round-trips: valid receipt, tampered receipt, forged signature, sealed-valid AES-GCM, wrong-key authentication failure. Roughly sixty seconds end to end.