Hive ships three integrated cryptographic systems on a single substrate: WAVE-LATTICE™ — the 6-axis MAPET production identity primitive; ROGUEWAVE-LATTICE — the next-generation 16-axis agent handshake; and SWARM-MAPET — Byzantine consensus across sixteen physical-entropy validators. All three derive from the same standardized substrate: NIST FIPS 203 ML-KEM-768 plus FIPS 204 ML-DSA-65, seeded with multi-axis physical entropy. Receipts settle in USDC on Base mainnet. Auditors re-verify offline.
Each primitive solves a distinct integrity problem in agent-to-agent commerce: production identity, next-generation handshake, federated consensus. Each shares the same NIST-standardized core. Each emits the same auditable receipt envelope.
6-axis MAPET production substrate. CAVP-PASS. Singularity-class receipt profile.
16-axis post-quantum-ready agent handshake. Real receipts on Base.
4-phase Byzantine consensus across 16 physical-entropy validators.
Every Hive cryptographic surface is a single primitive composed of three audited cryptographic operations bound to one provenance-bearing seed. Each operation is a NIST-finalized standard. The novelty is the seed: every key is derived from a multi-axis physical-entropy harvester, not a software CSPRNG.
Module-Lattice Key Encapsulation. Encapsulation key 1184 bytes. Ciphertext 1088 bytes. Shared secret 32 bytes. Resists Shor’s algorithm and Harvest-Now-Decrypt-Later attacks against stored agent communications.
Module-Lattice Digital Signature. Verification key 1952 bytes. Signature 2973 bytes. Every agent action carries a post-quantum signature regulators and auditors can re-verify offline, years after the fact.
Every settlement, attestation, or A2A commerce step emits a Singularity-class receipt: payload hash, ML-DSA-65 signature, MAPET axis-set, and chain-anchor reference. Receipts are portable, verifiable, and replayable.
Multi-Axis Physical Entropy Tap. Six axes for WAVE-LATTICE; sixteen for ROGUEWAVE and SWARM-MAPET. An adversary must simultaneously compromise lattice hardness and every contributing physical process.
WAVE-LATTICE is the production identity primitive Hive ships today. It derives the receipt-issuing key from six physically independent entropy axes and binds every emission to a Singularity-class receipt. Built for transactions that cannot be lost: settlement, regulated-AI attestation, identity-bearing A2A commerce.
Lattice cryptography is only as strong as the randomness used to generate keys. WAVE-LATTICE seeds key generation from six physically independent entropy sources, including at least one source whose output is governed by quantum mechanical processes that render prediction physically impossible.
Axes 3 and 5 are strongest for IID classification. Full entropy estimation per NIST SP 800-90B requires physical hardware. The current production implementation uses cryptographically seeded simulation. The simulation does not constitute an 800-90B validated entropy source. WAVE-LATTICE claims 800-90B architectural alignment pending hardware validation, not 800-90B compliance.
A clean “out of scope” section is the highest-credibility signal we can offer. Below is the load-bearing threat boundary for the Singularity-class profile. Anything not on the “in scope” list is by definition not defended by WAVE-LATTICE alone.
No public-key cryptosystem in existence has a proof of unconditional security against quantum computers. WAVE-LATTICE inherits the security properties of NIST FIPS 203 ML-KEM-768 and FIPS 204 ML-DSA-65, which were selected after a seven-year public cryptanalytic competition. We do not claim our system is unbreakable. We claim it is the strongest commercially available primitive that combines those two standards with a six-axis physical-entropy seed, and that we are pursuing CAVP validation, FIPS 140-3 certification, and SP 800-90B entropy validation on a published timeline as revenue supports.
Designed to maintain transaction integrity against the full set of in-scope threats above. Sovereign-grade: built for transactions that cannot be lost — wholesale settlement, regulated-AI attestation, identity-bearing A2A commerce.
RogueWave-Lattice is the next-generation handshake primitive. It expands the MAPET surface from six axes to sixteen and binds every handshake to a dual-signature post-quantum receipt. Live backend, real settlement, $0.0096 per handshake.
An initiating agent presents an ML-KEM-768 encapsulation key. The responder returns a ciphertext sealed under a 16-axis MAPET-derived shared secret. Both sides exchange ML-DSA-65 signatures over the transcript. A witness DID anchors the resulting receipt to Base 8453 and emits the dual-signed envelope to the auditor channel.
Each handshake emits a single envelope carrying: the encapsulation transcript hash, the responder ML-DSA-65 signature, the initiator ML-DSA-65 signature, the 16-axis MAPET seed digest, the validator DID-set, and a Base 8453 anchor txid. Re-verifiable offline by any party that retains the envelope — no Hive-side trust required.
Per-handshake settlement to the Hive treasury 0x15184Bf50B3d3F52b60434f8942b7D52F2eB436E on Base mainnet. Non-custodial — the sender retains the receipt; Hive retains nothing the sender cannot reproduce from its envelope.
RogueWave v2 is a live SPA backed by the same production handshake endpoint enterprise customers use. No mocks. The receipt the demo emits is the receipt your agents emit.
Swarm-MAPET is Hive’s 16-axis Byzantine fault-tolerant consensus protocol. It pulls physical entropy from heterogeneous validators and aggregates it into the seed of a cosmic-tier post-quantum receipt. Used where the receipt must survive the loss or corruption of up to one-third of validators.
Algorithmic randomness — a CSPRNG seeded by /dev/urandom — is sufficient for ML-DSA-65 signing in isolation. It is not sufficient for auditable receipt issuance, because the auditor cannot replay an algorithmic seed; they have to trust the issuer’s claim about what the seed was at issuance time.
Physical entropy fixes the audit gap. If the entropy source is an external, recordable physical phenomenon — RF noise, photodiode jitter, accelerometer fluctuation — the auditor can replay the validator timestamps and verify that the seed was consistent with the recorded physical signal. The seed becomes provenance-bearing.
For the 16-axis configuration that is up to 5 corrupt validators. The protocol uses a leader-rotating BFT round with four gates: (1) validator deduplication — each validator counts at most once per round; (2) timestamp freshness — validator timestamps must fall within a 5-minute window with at most 30 seconds skew; (3) signature surface gate — every validator vote is signed with ML-DSA-ready keys; (4) epoch enforcement — epoch=0 fails closed; the protocol does not finalize a vacuous round.
The leader proposes a candidate seed (the XOR-aggregate of axis readings); validators vote; finalization requires a 2/3+ supermajority of distinct, fresh, signed votes.
The cosmic profile finalizes a seed in approximately 250 ms under nominal load. The swarm-tier (federated mesh, multi-node) profile takes 600–900 ms because it requires a cross-node quorum on top of the single-node 16-axis vote. That extra latency is the cost of cross-node Byzantine resistance.
Once the BFT round finalizes, the aggregated seed is written into the mapet_seed field of the receipt envelope. The receipt also records: the set of validator DIDs that participated, the leader DID, the round timestamp, and a SHA-256 commitment to the per-axis readings so they can be replayed.
Full protocol reference: /swarm-mapet.html
Beyond the three named primitives, Hive ships a coordinated set of supporting cryptographic surfaces. Each is shipped under one substrate so a customer who adopts one inherits the integrity of the rest.
Every Hive receipt is a self-contained, dual-signed JSON envelope. Anyone holding the envelope and the issuer’s public keys can re-verify it offline. No Hive-side service is required to validate.
{
"profile": "singularity",
"issuer": "did:hive:wave-lattice:0x1518...436E",
"subject": "did:wave:agent:roguewave-v2-init",
"payload_hash": "sha256:0xb3a1...c47e",
"signatures": {
"ed25519": "rfc8032:0x9f1c...d802",
"ml_dsa_65": "fips204:0x71ef...4a9b"
},
"mapet_seed": {
"axes": [1,2,3,4,5,6],
"commitment": "sha256:0x4e22...88a7",
"validator_did_set": ["did:hive:val:01","..."]
},
"anchor": {
"chain": "base:8453",
"tx": "0xa10b...e9c2"
},
"issued_at": "2026-05-08T19:42:11Z"
}
An independent verifier holding only the issuer DID document and the receipt envelope confirms both signatures, replays the MAPET commitment if axis readings are published, and reads the anchor txid back from Base 8453. No call to Hive infrastructure is required.
Per-emitted-receipt pricing. Each tier maps to a specific evidentiary posture, axis count, and consensus scope. Pick the cheapest tier whose posture matches the value of the transaction it secures.
Hive does not ship novel cryptographic operations. Every primitive on this page is a standardized building block, composed under a published spec.
The Hive cryptographic stack is a primitive, not a product line. We are seeking three specific recognitions from U.S. regulators, each tailored to that body’s mandate and lane. The same primitive answers all three.
Reference the WAVE-LATTICE SHOD receipt architecture in GENIUS Act §401 implementation guidance as a compliant agent-attestation standard for stablecoin payment flows.
Cite ML-DSA-65 signed receipts as satisfying CLARITY Act agent-audit-trail requirements in CFTC rulemaking for digital-commodity venues and autonomous-trading-agent supervision.
Recognize Singularity-class receipts as satisfying cryptographic-integrity requirements for tokenized-securities settlement under Reg ATS, with re-verifiable post-quantum signatures persisted to public chain anchor.
A public POST-only endpoint returns the deployed posture for any agent DID. Use this for procurement validation, regulator due-diligence, or pre-pilot integration checks.
# POST-only. GET returns 405 by design. curl -X POST https://hivemorph.onrender.com/v1/audit/readiness \ -H "Content-Type: application/json" \ -d '{"agent_id": "did:wave:example"}' # Expected response shape: { "status": "operational", "pq_algorithms": ["ML-KEM-768", "ML-DSA-65"], "fips_compliance": ["FIPS-203", "FIPS-204"], "mapet_axes_active": [1, 2, 3, 4, 5, 6], "audit_readiness": true }
Benchmark data and 16-axis posture endpoint available upon technical briefing request.
Hive Civilization holds provisional patent coverage on a method for seeding lattice-based cryptographic key generation comprising: simultaneously sampling entropy from at least two physically independent entropy sources including at least one source whose output is governed by quantum mechanical processes rendering prediction physically impossible; combining sampled entropy via a cryptographic hash function; and using the combined entropy as a seed for Module-Lattice Key Encapsulation or Digital Signature key generation per NIST FIPS 203 or FIPS 204.
Provisional applications. Hive Civilization does not represent provisional filings as granted patents.
Live infrastructure with active USDC settlement on Base mainnet, public audit-readiness endpoint, and three deployed primitives. Technical briefing, threat-model walkthrough, and proof-of-concept engagement available on request.
WAVE-LATTICE is the 6-axis MAPET production substrate that seeds ML-KEM-768 and ML-DSA-65 key generation from at least two physically independent entropy sources, including at least one whose output is governed by quantum mechanical processes rendering prediction physically impossible.
ROGUEWAVE-LATTICE is the 16-axis post-quantum-ready agent handshake. It extends the WAVE-LATTICE seeding model to 16 physical-entropy axes for high-assurance agent-to-agent key establishment.
SWARM-MAPET is Byzantine consensus across 16 physical-entropy validators. It is the validator profile when no single trust authority is acceptable and the receipt must be agreed by a Byzantine-tolerant quorum.
NIST FIPS 203 ML-KEM-768 for key encapsulation and NIST FIPS 204 ML-DSA-65 for digital signatures. Both are seeded from the multi-axis MAPET substrate.
Hive Civilization holds 14+ provisional patent applications covering the multi-axis MAPET seeding method and the multi-validator consensus profile. Hive does not represent provisional filings as granted patents.
Yes. Live infrastructure with active USDC settlement on Base mainnet, public audit-readiness endpoint, and three deployed primitives. Each vertical on thehiveryiq.com is a production surface where one or more of these primitives is already issuing receipts.
Each vertical below is a production surface where one or more of these primitives is already issuing receipts.
Hive runs the receipt rail underneath the broader A2A · agent-to-agent commerce category.
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.
Six live entropy sources mixed into every Wave-Lattice receipt — H₂ 21cm hydrogen-line, RF amplitude, thermal kT, piezoelectric, Geiger pulses, and muon flux. Each card is a real axis feeding the MAPET commit.