Posture, not promises.
Hive is engineered to support the record-keeping, residency, and disclosure requirements emerging across the EU, U.S., and major Asian jurisdictions. We describe what the system does mechanically. We do not assert legal conclusions on behalf of your counsel.
What Hive is designed to support.
For each regime below, we describe the mechanical capability Hive provides and the field-level evidence available in the receipt envelope. We do not claim legal conformance on your behalf.
EU AI Act
Designed to support Article 12 record-keeping for high-risk systems: per-call automatic logging, cross-border inference disclosure, training-region declaration, and post-market monitoring evidence.
MiCA
Settlement of AI transactions in USDC on Base produces a settlement-hash-bound receipt, designed to support the transaction-record obligations placed on entities operating in or with the EU under MiCA.
EU Data Act
Provenance fields and ViewKey-gated inspection are designed to support data-access, data-portability, and third-party-access obligations under the Data Act, without granting platform-level plaintext access.
U.S. export controls
Hardware-class attestation is co-signed by the operator into every receipt. Restricted-destination rules (RU, CN, IR, KP, SY, CU, BY) are enforced at routing time, before compute.
Sanctions screening
Restricted-geography routing rules are evaluated against the requester’s identity anchor, the operator’s region, and the settlement counterparty before any compute or settlement event begins.
Audit posture & residency
SOC 2 Type I and ISO 27001 readiness are in progress. SOC 2 Type II, ISO 27001 certification, and FedRAMP are not yet held. Status is reported live on /trust.
Restricted-geography routing
Hive does not operate in, route to, or accept settlement from jurisdictions subject to comprehensive U.S. or allied sanctions. The active list reflects current OFAC, EU Council, and UK Treasury designations and is updated as those designations change. Exclusion is enforced at the routing layer, before any operator quote is solicited and before any escrow is locked. Receipts for blocked attempts are still written — for audit — and clearly marked blocked_by_policy.
Cryptographic attestation of the receipt-signing layer is provided by Wave-Lattice — ML-DSA-65 · ML-KEM-768 · 6-axis MAPET, CAVP self-test PASS — for transactions where post-quantum-ready signature provenance is required by the applicable regulatory posture.
What we do not claim.
Hive supports compliance work. Hive is not:
- not legal advice
- not a regulatory authorization
- not a substitute for counsel
- not a guarantee of conformance
- not a custodian of your data
- not a recommendation engine
We describe the mechanical behaviour of the system. Your counsel determines applicability to your obligations.
Request a private compliance briefing.
The briefing includes the receipt schema, ViewKey access model, restricted-geography routing rules, audit posture, and a counsel-reviewed mapping to EU AI Act, MiCA, EU Data Act, and U.S. export-control regimes — sealed to your organization, modeled on Hive’s live infrastructure.