Nano-Band · Sixth Lattice · Patent Pending

Four bands. Each carries the cryptographic weight the payment is worth.

Nano-Band is a post-quantum signing setup for micropayments that matches the crypto to the payment size. A tiny payment doesn't need a 3,309-byte ML-DSA-65 signature. A $25 payment does, plus a witness quorum. The payment amount decides the band. The random seed comes from the NIST Randomness Beacon v2.0. Patent Pending · Filed 2026-05-08

The four bands.

A receipt that costs less than a thousandth of a cent shouldn't pay for the same signature as a $25 payout. Nano-Band spreads ML-DSA-65 across batches at the bottom, pays per payment in the middle, and adds a witness quorum at the top.

B0 · dust
Dust
< $0.001
Per-payment sig: none
Batched PQ: 1 ML-DSA-65 every 10,000 leaves
Leaf: BLAKE3 only
Use: per-token billing, per-pixel, per-impression
B1 · micro
Micro
$0.001 to $0.10
Per-payment sig: Ed25519 (64 B)
Batched PQ: 1 ML-DSA-65 every 1,000 leaves
Leaf: BLAKE3 + Ed25519
Use: per-API-call, per-second compute
B2 · milli
Milli
$0.10 to $10
Per-payment sig: hybrid Ed25519 + ML-DSA-65
Batched PQ: 1 per payment (no batching)
Leaf: full hybrid receipt
Use: per-job, per-tier, per-task
B3 · macro
Macro
> $10
Per-payment sig: hybrid + STH inclusion + witness quorum 2-of-3
Batched PQ: never
Leaf: hybrid + Merkle proof + 3 witness co-signatures
Use: payouts, settlements, sovereign receipts

Live band policy.

The server hands back the band policy directly. Every /v1/nano/mint response carries the band it landed in, the leaf hash, and any per-payment signatures that band needs.

BandRangePer-paymentBatch ratioCost amortization
B0 dust< $0.001none1 / 10,000~0.00033 of a PQ sig per payment
B1 micro$0.001 to $0.10Ed255191 / 1,000~0.001 of a PQ sig + classical sig
B2 milli$0.10 to $10hybrid1 / 1full hybrid per payment
B3 macro> $10hybrid + STH + 2-of-31 / 1full hybrid + log inclusion + quorum

NIST Randomness Beacon as entropy.

Each Nano-Band batch root locks in the latest NIST Beacon pulse, a chained, RSA-signed randomness source that updates every 60 seconds. The batch can't have been signed before that pulse came out. The time is locked in. The batch is locked in. Every leaf inside the batch inherits both.

{ "scheme": "nano-band-v1", "entropy_source": "NIST Randomness Beacon v2.0", "pulse": { "chainIndex": 1, "pulseIndex": 1809800, "timeStamp": "2026-05-30T05:30:00Z", "outputValue": "a7c4f2…512-bit hex…" }, "merkle_root_blake3": "7e0c…", "operator_sig_ed25519": "…", "operator_sig_ml_dsa_65": "…3309 bytes…" }

Five-line verify recipe.

Anyone, anywhere, with nothing but the receipt and the operator's public keys, can check a Nano-Band payment offline.

# 1. Get the policy curl -s https://ct-log.onrender.com/v1/nano/policy LIVE # 2. Mint a receipt: the band is set by amount_usd curl -s -X POST https://ct-log.onrender.com/v1/nano/mint \ -H "content-type: application/json" \ -d '{"amount_usd": 0.50, "payer_did":"did:hive:alice", "payee_did":"did:hive:bob"}' # 3. Batch B0/B1 leaves under one ML-DSA-65 signature curl -s -X POST https://ct-log.onrender.com/v1/nano/batch \ -H "content-type: application/json" \ -d '{"leaves":["7aa8…","37f8…","aed0…"]}' # 4. Verify the leaf inside the batch curl -s -X POST https://ct-log.onrender.com/v1/nano/verify \ -H "content-type: application/json" \ -d '{"leaf":"…","batch":{…}}' # 5. Returns checks[]: 7/7 PASS = receipt is valid

Why a band, not a fixed scheme.

Cost matches value

A 3,309-byte ML-DSA-65 signature is about 150 times bigger than the Ed25519 signature it replaces. Paying that on every micropayment would eat your margin. Nano-Band batches things up when the leaf is cheap and pays in full when the leaf is real money.

Court-grade at the top

B3 macro payments carry the full sovereign-tier setup: hybrid signature, public log inclusion, and a 2-of-3 witness quorum. That's self-authenticating evidence under FRE 902(13) to (14).

Patent-pending band classifier

The classifier maps the amount to a band, the band to a signature policy, and the signature policy to a verification recipe, all in one envelope. Patent Pending · Filed 2026-05-08 Steve Rotzin / Hive Civilization, Inc.

Inside the lattice family.

Patent Pending · Filed 2026-05-08 · Steve Rotzin / Hive Civilization, Inc.