This is the next-generation receipt profile. It combines NIST FIPS 203 ML-KEM-768 and FIPS 204 ML-DSA-65 with a sixteen-axis Swarm-MAPET consensus protocol: a 4-phase Byzantine-fault-tolerant agreement across heterogeneous physical-entropy validators. Where WAVE-LATTICE seeds keys from one node, ROGUEWAVE-LATTICE finalizes blocks across a swarm. It is the first consensus protocol where the ‘work’ validators do is verifiable physical entropy, not hashing and not staking.
To forge a ROGUEWAVE-LATTICE block, an attacker would have to break the lattice math and also compromise a whole group of physically independent entropy sources at once, spanning quantum optics, particle physics, biology, gravitation, and cosmology. The 6-axis WAVE-LATTICE substrate is the inner ring. Ten more axes form the outer ring around it.
IDQ20MC1 vacuum-state quantum noise.
Single-photon avalanche, up to 12 Gbps.
Resistor thermal-noise harvested from analog front-end.
Wideband RF environmental capture.
Mechanical accelerometer drift.
Surface-level cosmic-ray scintillator.
Coherent elastic scattering on CsI[Na] + SPAD. Patent #1.
OECT + voltage-gated Na+. Patent #5.
Organoid spike-timing entropy.
Sub-shot-noise quadrature measurement.
Cryogenic magnetic-flux quanta.
GWOSC public strain channels.
NANOGrav 15-year array. Patent #4.
Extensive air-shower coincidence.
Independent vacuum-state homodyne pair.
High-rate single-photon array.
Validators are physical-entropy nodes. The ‘work’ they do is attested entropy generation across heterogeneous axes, not hashing and not staking. A 4-phase BFT round (PrePrepare → Prepare → Commit → Finalize) picks a leader by AIMEW-weighted entropy quality, checks per-axis attestations, excludes Guardian-quarantined axes, and finalizes a block. Byzantine tolerance: f < n/3.
Python reference implementation: consensus.py + engine.py + types.py + leader.py + verify.py. Multi-validator harness: 7 nodes, 2 byzantine, 20/20 rounds finalized, byzantine flagging triggered every round, all 5 honest validators led at least once.
Closed-binary in production. The Rust skeleton at rust-skeleton/ defines the canonical wire format. Reference Python implementation is open for partner review under NDA.
Provisional filed: Proof-of-Physical-Work consensus protocol. The first consensus protocol where validator work is verifiable physical entropy attestation rather than computational hashing or token staking.
ROGUEWAVE-LATTICE is a building block, not a product line. The same 16-axis Swarm-MAPET fabric runs across three surfaces.
Wave-Lattice axes run on ARM Secure Element and TrustZone. Every app gets its own device receipt. Any mobile agent in a regulated ecosystem can use this identity and attestation building block.
Dedicated silicon. Target $15 BOM at 100K volume. Sixteen-axis substrate in a single SoC for embedded swarm validators (Build #22).
Custom form factor on request. For sovereign-grade settlement infrastructure, orbital nodes, regulated-AI attestation appliances. Pricing on contact.
ROGUEWAVE-LATTICE is one system built from four audited parts. The cryptography follows finished NIST standards. What is new is the consensus: every block gets finalized across a swarm of physically different entropy validators.
This is Module-Lattice Key Encapsulation. The encapsulation key is 1184 bytes. The ciphertext is 1088 bytes. The shared secret is 32 bytes. It holds up against Shor’s algorithm and against attackers who store encrypted agent communications today hoping to decrypt them later once quantum computers exist.
This is Module-Lattice Digital Signature. The verification key is 1952 bytes. The signature is 2973 bytes. Every agent action carries a post-quantum signature that regulators and auditors can check offline, years later, and still trust.
Every settlement, attestation, or A2A commerce step gives you a Singularity-class receipt: a payload hash, an ML-DSA-65 signature, the MAPET axis set used, and a chain-anchor reference. You can carry these receipts anywhere, check them independently, and replay them.
This is the Multi-Axis Physical Entropy Tap: six independent entropy sources spanning quantum, thermodynamic, electromagnetic, mechanical, nuclear, and relativistic domains. To break it, an attacker would need to defeat the lattice math and all six physical processes at the same time.
Lattice cryptography is only as strong as the randomness used to build the keys. WAVE-LATTICE generates keys from six physically independent entropy sources, including at least one source whose output comes from quantum mechanics, which makes it physically impossible to predict.
Axes 3 and 5 give the strongest IID classification. Full entropy estimation under NIST SP 800-90B needs real physical hardware. Right now the production build uses cryptographically seeded simulation instead. That simulation is not an 800-90B validated entropy source. WAVE-LATTICE is built to line up with 800-90B, pending hardware validation. It does not yet claim 800-90B compliance.
A clear “out of scope” list is the most credible thing we can show you. Below is the real threat boundary for the Singularity-class profile. If something is not on the “in scope” list, WAVE-LATTICE alone does not defend against it.
No public-key cryptosystem today has a proof of unconditional security against quantum computers, and neither do we. WAVE-LATTICE inherits the security properties of NIST FIPS 203 ML-KEM-768 and FIPS 204 ML-DSA-65, both chosen after a seven-year public cryptanalytic competition. We do not claim our system is unbreakable. We do claim it is the strongest commercially available system that combines those two standards with a six-axis physical-entropy seed, and we are pursuing CAVP validation, FIPS 140-3 certification, and SP 800-90B entropy validation on a published timeline as revenue allows.
These results are a self-test against public NIST ACVP test vectors, not a CAVP certificate from an accredited laboratory. The excluded test groups (HashML-DSA pre-hash, internal-interface mu, deterministic-encap byte-exact) are documented in the linked repository. They come from upstream liboqs-python binding limitations, not gaps in the production code paths used by Singularity-class receipts. Hive Civilization will pursue formal CAVP validation, FIPS 140-3 module validation, and SP 800-90B entropy validation 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, including wholesale settlement, regulated-AI attestation, and identity-bearing A2A commerce.
WAVE-LATTICE is a building block, not a product line. We are asking three U.S. regulators for three specific things, each one matched to that body’s own mandate. The same system answers all three.
Reference the WAVE-LATTICE SHOD receipt design in GENIUS Act §401 implementation guidance, as a compliant agent-attestation standard for stablecoin payment flows.
Cite ML-DSA-65 signed receipts as meeting CLARITY Act agent-audit-trail requirements in CFTC rulemaking for digital-commodity venues and autonomous-trading-agent supervision.
Recognize Singularity-class receipts as meeting the cryptographic-integrity requirements for tokenized-securities settlement under Reg ATS, with re-verifiable post-quantum signatures anchored to a public chain.
A public POST-only endpoint returns the live status for any agent DID. Use it for procurement checks, regulator due diligence, or pre-pilot integration testing.
# 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 available upon technical briefing request.
Hive Civilization holds provisional patent coverage on a method for seeding lattice-based cryptographic key generation. It works by sampling entropy at the same time from at least two physically independent entropy sources, including at least one source governed by quantum mechanics that makes prediction physically impossible. It combines that sampled entropy through a cryptographic hash function, then uses the combined entropy as a seed for Module-Lattice Key Encapsulation or Digital Signature key generation under NIST FIPS 203 or FIPS 204.
Provisional applications. Hive Civilization does not represent provisional filings as granted patents.
We are pre-revenue and pre-customer. A technical briefing and proof-of-concept engagement are both available on request. The infrastructure is live, with active USDC settlement on Base mainnet, a public audit-readiness endpoint, and an SDK published on PyPI and npm.
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 works the same way everywhere: every transaction, every framework, every surface.