Related · tier-1 reading. For the integrity anchor that makes this verifiable, see Avalanche Evidence Anchoring.
A visual walkthrough of the H33-74 attestation workflow. The encrypt/decrypt step runs real AES-GCM in your browser; the FHE, STARK, and post-quantum signature values illustrate the production pipeline. Verify the real cryptography — every byte — in the Proof Lab.
What you're about to see
A simulated $10M BitBond goes through the full H33-74 attestation pipeline: the bond data is encrypted with homomorphic encryption (so it's never visible in plaintext), a compliance check runs on the encrypted data, and then the result is signed with three independent post-quantum signature families and committed to a 58-byte cryptographic primitive. The encrypt/decrypt step below runs real browser AES-GCM; the FHE, STARK, and signature values illustrate the production pipeline you can verify in the Proof Lab.
In production, this 74-byte evidence is produced and anchored by H33-74 — the portable post-quantum evidence primitive this demo walks through.
STEP 1 / 7WAITING
Create BitBond
Simulated U.S. Treasury bond with 1% Bitcoin allocation
What's happening: A bond is created with a CUSIP identifier, face value, BTC allocation percentage, and 30-year maturity. This is the raw financial instrument that needs cryptographic attestation.
STEP 2 / 7WAITING
Encrypt with FHE
Bond data encrypted using BFV Fully Homomorphic Encryption
What's happening: Every field of the bond (face value, allocation, maturity) is encrypted using lattice-based homomorphic encryption. The data is never decrypted at any subsequent step. All computation happens on the encrypted values. This is not tokenization or hashing — it's mathematically proven encryption that allows computation without decryption.
STEP 3 / 7WAITING
Encrypted Compliance Check
TFHE threshold check: "Is BTC allocation ≤ 1%?" — computed on encrypted data
What's happening: Using a different FHE scheme (TFHE, optimized for comparisons), the system checks whether the Bitcoin allocation complies with the 1% limit. The check runs entirely on encrypted bits. Neither the allocation amount nor the threshold value is ever decrypted. The result itself is encrypted — only the bond issuer can see it.
STEP 4 / 7WAITING
Bond Fingerprint
SHA3-256 hash of the encrypted bond data + compliance result
What's happening: A cryptographic fingerprint is computed over the encrypted bond and the compliance result. This fingerprint uniquely identifies this specific bond at this specific moment. It cannot be forged, and any change to the underlying data produces a completely different fingerprint.
STEP 5 / 7WAITING
Mint H33-74 Primitive
58-byte attestation primitive — the permanent cryptographic record
What's happening: The fingerprint is embedded into a 58-byte H33-74 primitive. This is the atomic unit of trustless verification in the H33 system. It contains: the computation type (BitBondIssuance), the SHA3-256 commitment, a timestamp, and a cryptographic nonce. 58 bytes. That's the entire persistent footprint.
STEP 6 / 7WAITING
Three-Family Post-Quantum Signing
ML-DSA-65 + FALCON-512 + SLH-DSA-SHA2-128f — three independent mathematical bets
What's happening: The H33-74 primitive is signed by three different post-quantum signature algorithms, each based on a different mathematical hardness assumption. To forge this signature, an attacker would need to break lattice problems, NTRU lattice problems, AND stateless hash functions simultaneously. No known or theoretical quantum computer can do this.
STEP 7 / 7WAITING
Bitcoin Mainnet Anchor LIVE
32-byte commitment permanently anchored to Bitcoin mainnet via OP_RETURN
What's happening: The first 32 bytes of the H33-74 primitive (the SHA3-256 commitment) are ready to be written to Bitcoin mainnet via a standard Taproot transaction. Once anchored, anyone can verify this bond attestation existed at a specific point in time — without knowing anything about the bond itself. The anchor is permanent and immutable.
Verification
The values below illustrate a production H33-74 attestation. Verify real H33-74 proofs and post-quantum signatures — offline — in the H33 Proof Lab.
Decrypt Bond Instrument
The bond metadata below is AES-256-GCM encrypted. Paste the decryption key to reveal the data. Wrong key = no data.
Encrypting...
YOUR DECRYPTION KEY:
HOW THIS WORKS IN PRODUCTION
This demo uses AES-256-GCM for browser efficiency. In production, H33 uses BFV Fully Homomorphic Encryption — the bond data is encrypted with a lattice-based scheme that allows computation on the ciphertext without decryption. The key holder sees the data; the compute layer never does.
The attestation proves that the encrypted data was processed correctly (threshold checks, compliance gates) without ever decrypting it. The decryption key is held by the bond issuer or authorized party — not by H33, not by the compute infrastructure, not by any intermediary.
Three independent post-quantum signature families (ML-DSA, FALCON, SLH-DSA) sign the attestation. To forge it, an attacker would need to simultaneously break lattice problems, NTRU problems, AND stateless hash functions. No known or theoretical quantum computer can do this.
