← Cut sheet·Offering 01 of 12
OFFERING 01· Plugs into Circle Gateway Nanopayments · Agent Stack · Agent Wallets
Hive Receipt Engine
A nanopayment without a receipt is just a wire transfer with no confirmation. Every payment that moves through Circle Gateway, whether it's a 402, a sub-cent USDC transfer, or a batched agent-to-agent settlement, gets a receipt signed two ways on the RogueWave-Lattice v2 substrate: Ed25519 plus ML-DSA-65 (NIST FIPS 204). It's put in order per RFC 8785, batched with a Merkle tree, and anchored across all 11 Gateway Nanopayment chains. The Circle transaction hash is baked right into the signed payload, so anyone can check it start to finish without having to trust the Hive API.
How it plugs in.
circle_gateway_nanopayment.py
# Three lines beside any Circle Gateway nanopayment call. import hive_receipt as hive receipt = hive.sign_nanopayment( circle_tx_hash=tx.hash, # from Gateway / Agent Wallet from_wallet=agent_a.address, to_wallet=agent_b.address, amount_usdc=0.000096, # sub-cent, gas-free chain_id=8453, # Base, or any of 11 Gateway chains service="contract_review_v3", substrate="rogue-wave-lattice-v2", # 16-axis PQ default ) # Ed25519 + ML-DSA-65 signed. Anchored across all 11 chains.
What Circle gets.
- Every nanopayment carries proof of delivery, not just a ledger entry.
- One-click block explorer link per receipt across all 11 Gateway chains.
- The Circle transaction hash gets baked into the signed payload, so it can be checked without Hive API access.
- It drops right in beside Gateway middleware, post-quantum from day one.
Ready when Circle is.