From the founder · Eric Beans, CEO H33

A portable 32-byte post-quantum anchor across chains.

Q: How is the portable anchor different from Verification?

H33-74 produces and anchors the evidence; Verification renders the independent verdict over that evidence. One is the durable receipt; the other is the judgment a relying party reaches by re-checking it.

Q: Does H33 own the chains it anchors to?

No. Bitcoin, Solana, Ethereum, Polygon zkEVM and Zcash are external environments the evidence anchors to, never owned. The post-quantum families and hashing standards are external NIST/IETF standards H33 uses, never invented or owned.

Bitcoin · Solana mainnet · Ethereum · Polygon zkEVM · Zcash — STARK-backed privacy on the rails that support it, tied to three independent NIST-standardized post-quantum key families (ML-DSA + FALCON + SPHINCS+). No single-point cryptographic failure.

BitcoinTaproot · BIP-341 Solanalive · mainnet Ethereumcalldata + event Polygon zkEVMSTARK-privacy Zcashunique nullifier

What this enables

A portable 32-byte post-quantum anchor across chains means…

Operations & Anchoring

Replayable operational infrastructure
Live operational proof systems
Cross-chain replayable receipts
74-byte portable attestations across Bitcoin, Solana, Ethereum, Polygon zkEVM

Cryptography & Privacy

Post-quantum attestations
Cryptographic continuity across organizations and agents
Q-Sign post-quantum signing infrastructure
Privacy-preserving compliance and audit trails

AI & Governance

Encrypted AI / agent execution tracking
Independently verifiable governance replay
Agent-Zero operational lineage
H33-Upstream provenance + governance continuity

Beyond tokenization or proofs. This is reconstructable operational truth at AI scale — trillions of transactions, accurate replay, no operator dependency.

What this is

A portable anchor in one sentence.

A portable post-quantum anchor is a compact, self-contained evidence artifact that H33-74 produces and anchors — a receipt committing an event to independent NIST-standardized post-quantum signature families, so the record can be re-checked offline, against schema and hash, by anyone, long after the system that created it is gone. It exists because operational evidence usually dies with the infrastructure that produced it: when the chain, cloud, vendor, or organization is replaced, the proof is replaced with it. The anchor makes the evidence outlive the operator and survive the post-quantum transition.

Use it when

You need portable, offline-verifiable proof that must outlive the systems that produced it
A record must remain replayable across chain, cloud, vendor, model, or org change
A relying party must re-verify trusting no one — no operator, no live service, no H33

Don't use it for

The verdict itself — that is rendered by Verification, not H33-74
Live monitoring or alerting of systems — that is what HATS records
Governing an agent's authority in the moment — that is Agent-008

How it stays honest

Re-checked offline against schema and content hash; representation never exceeds reality
Bound to three independent external PQ families — no single-family break defeats it
The external chain it anchors to is a reference environment, never owned by H33

Questions

Boundaries of the portable anchor.

What exactly is the anchor, and what does it NOT do?

It is a portable, durable evidence artifact that H33-74 produces and anchors — a receipt independently re-verifiable offline. It does not render the verdict (that is Verification), does not monitor or record systems (HATS), and does not govern agent authority (Agent-008). It carries proof; others decide and observe.

How is this different from Verification?

H33-74 produces and anchors the evidence; Verification renders the independent verdict over that evidence. One is the durable receipt; the other is the judgment a relying party reaches by re-checking it.

How is it independently verified?

By re-checking the receipt offline against its published schema and content hash using the open verifier — trusting no operator and no live service. The anchor survives infrastructure changes and the passage of time, so verification does not depend on the original system still existing.

Does H33 own the chains it anchors to?

No. Bitcoin, Solana, Ethereum, Polygon zkEVM, and Zcash are external environments the evidence anchors to, never owned. The post-quantum families (ML-DSA, FALCON, SPHINCS+/SLH-DSA) and hashing standards are external NIST/IETF standards H33 uses — never invented or owned.