Hive · Architecture

From the receipt API down to the silicon.

Hive owns the whole stack, top to bottom. Receipts are what buyers actually see. Underneath that sits five phases of AFiR, a roadmap for embedded chips, and a strict way of checking every claim that works even without an internet connection. It goes deep, but the front door stays simple.

Evolution

The five AFiR phases

AFiR started as a way to sign one call and get one receipt back. It grew into something that can sign a live, real-time stream. Every phase is still live today, and each later phase uses the ones before it.

P1 · Live

AFIR: signed inference.

One call goes in, one signed receipt comes out. It uses ML-DSA-65 plus Ed25519, and it adds under 7ms to the request.
P2 · Live

AFiR-S: selective.

This one only signs the pieces your policy says matter. It's built to protect privacy from the start.
P3 · Live

AFiR-RC: recoverable.

This checkpoints an agent's work. If a step goes wrong, you can catch it, roll it back, fix it, and keep going, and you can prove every part of that happened.
P4 · Live

AFiR-Stream: real-time.

A sidecar signs streaming workloads off to the side, so it doesn't slow anything down. It adds only 28µs to a live voice conversation.
P5 · Roadmap

AFiR-PQ-Embed.

This signs with ML-DSA-65 right on the device chip, not in the cloud. We're building paths to get it onto phone chips and secure elements.
Coming to silicon

From a cloud receipt to a chip you can hold.

Hive owns everything from the receipt API down to the chip that creates it. We have three chip forms on the roadmap, and each one has its own path to get built in.

EMBEDDED

Wave-Lattice in your pocket.

We're porting Wave-Lattice onto mobile chips (ARM SE and TrustZone), so each app can get a post-quantum receipt straight from the device instead of the cloud. At phone-making volumes, this costs pennies per unit.
SoC

RogueWave-Lattice SoC.

A drop-in chip that gives any embedded device our top-tier randomness and ML-DSA signing. You can buy the standalone chip and reference board, or license the firmware yourself. We're targeting $15 per unit at 100,000 units.
ON REQUEST

Industrial, government, and orbital.

A data-center HSM card, a car's ECU, a satellite payload, an industrial control module: we build the form factor to fit what you need, with a full attestation chain built for government-grade use.
Stack

What lives where.

Receipts sit on top. Strict verification sits at the core. Settlement runs on real public payment rails. Everything below that runs from the API surface down to the chip itself.

SURFACE

Receipt API and SDKs.

One REST surface, three SDKs (Node, Python, Go), and the hive-vcr-1 wire format. Developers →
PRIMITIVES

The AFIR family.

Five signing primitives that make up the four assurance tiers. Assurance →
SUBSTRATE

Wave-Lattice.

Our production substrate runs on 6 axes and passes a CAVP self-test against NIST ACVP vectors. RogueWave-Lattice 16 is our top tier. Wave-Lattice →
SETTLEMENT

Protocol.

SIU units, MNKA discipline, and settlement in USDC on Base. Protocol →
Protocol Assurance tiers Developers Verify a receipt →
Hive receipt badge; verify the exact receipt profile and trusted key.

Certified third-party receipts

This work is checked using Hive-supplied verification materials

Every receipt on this page is separately signed by Hive, and anyone can check it offline against a published key. The mark signals that a checkable receipt exists outside the operating stack; it does not represent a neutral-party certification.

Verify a receipt → ML-DSA-65 · NIST FIPS 204 Offline-verifiable
Put this on your site
<a href="https://thehiveryiq.com/verify/" rel="noopener">
  <img src="https://thehiveryiq.com/assets/brand/hive-mark-192.png"
       alt="Hive receipt badge; verify the exact receipt profile and trusted key."
       width="120" height="120" loading="lazy">
</a>