Judge walkthrough · 5 minutes
No token mints without a proof of a signed document.
Everything here is inspectable without a wallet.
What to do
- Upload it, unchanged
The engine reads back its fixed amount, its issuer and the one wallet it is bound to. Uploading spends nothing.
- Check it on chain
Gate, verifier and ATS token, each read live and pinned by runtime code hash.
The proof and the mint are presenter-led: one designated wallet signs the exact request. Want your own wallet in a run? Ask for a budget.
- 1 Signed document The institution already signed the PDF. We add no new standard.
- 2 zkPDF inside SP1 The signature is checked in a zero-knowledge VM. 224 bytes come out, not the file.
- 3 The Gate 11 ordered checks in one transaction. One failure reverts everything.
- 4 Token Not minted. The Groth16 proof has not returned, and the Gate needs it.
Hedera track · Tokenization of Anything
Qualification requirements
Use the Asset Tokenization Studio to issue or manage a tokenised asset
MetThe mint adapter holds the only issuance role on the token.
Inspect the token graph →Deploy and demonstrate on Hedera testnet
MetGate, verifier, adapter and the ATS graph, live on chain ID 296.
Read live chain state →Public GitHub repo, contracts verified where applicable
MetExact Sourcify matches, each pinned by runtime code hash.
Open the repository →Demo video showing issuance, configuration and a lifecycle operation
Pending live resultCloses only after a confirmed proof-gated mint and a 0.001 g transfer are recorded.
Follow the mechanism →
Current boundary
What the demo establishes
Enforcement Eleven checks in one transaction. One failure reverts all of it.
Identity ERC-8004 names the issuer. Only the Gate decides whether a mint may happen.
Asset The PDF and institution are synthetic. No backing, custody or redemption is claimed.
Completion Reconciliation confirms what happened. It cannot authorize a mint, or repair one.