Any asset. Any chain. Anchored at 32 bytes.
Full post-quantum. Not compressed.
It exists because tokenized assets normally force a trade-off: to prove a transfer happened you expose the parties, amounts, and terms on a public chain, and the proof dies if that chain does. Tokenize removes both problems — a 32-byte portable attestation carries the proof across any chain while the sensitive fields stay private.
Related · tier-1 reading. For what a portable artifact actually is, see Portable Artifact.
All institutional state collapses into one permanent replayable fact. Watch the primitive form: a $50M tokenized treasury transfer, an autonomous compliance agent, encrypted policy evaluation, authority delegation, canonical preservation, multi-hardness survivability, deterministic reconstruction. One click. Two scenes.
H33 Products · Tokenize
What this product is
Tokenize is a product that runs a governed tokenized-asset transfer — the $50M treasury transfer you just watched — where an autonomous compliance agent enforces policy on encrypted institutional state, delegated approval authority is preserved, and the entire session collapses into one portable, replayable canonical fact. It owns the tokenized-transfer workflow, the institutional-continuity outcome, and the operational experience. It does not own, redefine, or reimplement the cryptography, evidence, governance, authority, or verification it relies on; it composes them.
The product boundary. Tokenize owns the tokenized-transfer workflow and outcome. It uses H33 mechanisms for evidence, verification, governance, authority, and privacy; it does not redefine or own those mechanisms.
Fully homomorphic encryption lets the compliance agent evaluate the five policy gates on ciphertext — it never decrypts beneficial owner, KYC, NAV, or counterparty PII. The product consumes encrypted processing; it does not define it.
H33-74 supplies the portable post-quantum attestation; the session collapses to a 32-byte canonical commitment anchorable on any chain. The product commits the fact; it does not produce the attestation primitive.
Verification lets anyone deterministically reconstruct the whole session in-browser, with H33 not in the room. The product surfaces the replay; the verifying is owned elsewhere.
Agent-008 governs the autonomous compliance agent (Agent ZERO) acting on the transfer, preserving authority and preventing drift. The product is governed by it; it does not perform governance.
The authority graph — who may approve the transfer, delegation from Carol to the agent, and authority transitions on the approve_transfer scope — is Authority Center's attested delegated authority. The product consumes those decisions; it does not define who holds authority.
If Tokenize anchored somewhere other than Bitcoin, or swapped FHE for another confidential-computing technology, it would still be Tokenize. The tokenized-transfer workflow and continuity outcome are what it owns. Mechanisms are chosen, not owned.
The "$50M treasury transfer" and case ACME-XFR-2026-00042 are an illustrative scenario shown to demonstrate the primitive, not a real customer transaction. The session, verifier, and canonical commitment are real and reconstructable in-browser.
When to use it
Use Tokenize when you run a governed institutional asset transfer — treasury movement, restricted-token issuance, sovereign bond — that must enforce policy on encrypted state, preserve delegated approval authority, and produce a portable fact that outlives the vendor and reconstructs cryptographically.
For issuing tokens for real-world assets with policy enforced before issuance (funds, cross-border offerings, secondary trading), use Tokenization instead. To evaluate a mechanism itself, read FHE, H33-74, Verification, or Authority Center.
To wire governed transfers into your own systems, use the Cryptographic APIs. This product is the workflow and outcome; the APIs are the building blocks.
Frequently asked questions
Tokenize, and how the product composes H33 mechanisms.
What is H33 Tokenize?
A product that runs a governed tokenized-asset transfer where an autonomous compliance agent enforces policy on encrypted institutional state, delegated approval authority is preserved, and the whole session collapses into one portable, replayable canonical fact. It owns the tokenized-transfer workflow and outcome; it uses H33 mechanisms for privacy, evidence, verification, governance, and authority rather than reimplementing them.
Which H33 mechanisms does it use?
It USES FHE so the agent evaluates policy on ciphertext, USES H33-74 to commit a 32-byte portable post-quantum fact, and USES Verification for deterministic in-browser reconstruction. The compliance agent is GOVERNED_BY Agent-008, and delegated approval authority on the transfer scope is Authority Center's attested authority. The product composes these; it does not own or redefine them.
Would it still be the same product if one mechanism were replaced?
Yes. If Tokenize anchored somewhere other than Bitcoin, or swapped FHE for another confidential-computing technology, it would still be Tokenize. The tokenized-transfer workflow and continuity outcome are what it owns. Mechanisms are chosen, not owned.
When should I use this versus another product?
Use it for a governed institutional asset transfer with delegated approval and portable, replayable evidence. For issuing tokens for real-world assets with policy enforced before issuance, use Tokenization instead. To evaluate a mechanism directly, read the FHE, H33-74, Verification, or Authority Center hubs.