HIVE×CIRCLE
Offering 01 · Hive Receipt EnginePrivate brief · May 2026
← Cut sheet·Offering 01 of 12
OFFERING 01· Plugs into Circle Gateway Nanopayments · Agent Stack · Agent Wallets

Hive Receipt Engine

Substrate. RogueWave-Lattice v2 (16-axis PQ). Footprint. All 11 Gateway Nanopayment chains.

Nanopayments without receipts are wire transfers without confirmations. Every payment that moves through Circle Gateway — every 402, every sub-cent USDC transfer, every batched A2A settlement — emits a dual-signed receipt on the RogueWave-Lattice v2 substrate. Ed25519 plus ML-DSA-65 (NIST FIPS 204). JCS-canonicalized (RFC 8785). Merkle-batched. Anchored across all 11 Gateway Nanopayment chains. The Circle transaction hash is bound directly into the signed payload, so any third party can verify end-to-end without trusting 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.
  • Circle transaction hash bound into the signed payload. Reproducible without Hive API access.
  • Drop-in beside Gateway middleware. Post-quantum from day one.
Live today. Receipts API at hivecompute-g2g7.onrender.com/v1/receipts. RogueWave-Lattice v2 substrate. Same pipeline that signs the 40+ agents in the Hive Catalog. Delivery to Gateway Nanopayments: ~30 days.
Ready when Circle is.