Zero unknowns. Every chain.
Buyers can prove who created a token, and that no one can change its rules after launch. Powered by zkTLS creator proofs and immutable multi-DVN presets.
Locked Omnichain Tokens
Only tokens that have completed all 8 steps of the immutable recipe are displayed here.
Three things you used to take on trust, now anyone can check.
Creators who only claim an identity
On other launchpads, anyone can paste a famous X handle. On ZeroKnown, creators prove control cryptographically using Reclaim zkTLS, and that proof is permanently bound on-chain to the deployer wallet.
Bridges guarded by a single verifier
The Kelp DAO exploit (April 2026, ~$292M) happened because pathways were guarded by a single 1/1 DVN. ZeroKnown tokens mandate a 2-required multi-DVN preset from distinct operators, strictly rejected if 1/1.
“Renounced” that isn’t really
In LayerZero V2, renouncing contract ownership doesn’t make an OFT immutable, because the delegate registered on the endpoint can still mutate DVN configs. ZeroKnown zeroes the delegate first, then renounces.
Zero Unknowns on every token.
The /t/<address> page reads every fact straight from RPC in your browser, not from a ZeroKnown database.
A background monitor checks the same facts on a schedule and sends an alert to public channels if anything ever shifts. On a properly locked token, that monitor never fires, and that is the guarantee.
Three chains, one messaging layer.
Every cross-chain signal flows through LayerZero V2 messaging with the exact same locked DVN security preset.
Robinhood Chain
Tokens are born here alongside their initial liquidity pool. The ZKFactory deploys the OFT, creates the AMM pair, and transfers the LP tokens to the creator in a single atomic transaction.
Base
The token is mirrored at the exact same deterministic address via CREATE3. Peers are wired bidirectionally, ULN libraries are locked, and delegate is zeroed permanently.
Arbitrum
Reclaim zkTLS cryptographic proofs are verified on-chain by the Reclaim contracts on Arbitrum. Verified badges are then broadcast to Home and Expansion registries via LayerZero messages.
Eight steps in required order.
One preset for every token, and creators cannot modify it. A 1/1 single-DVN configuration is rejected hard at the factory level.
After step 8, no new chains can ever be added to that token, and stuck messages cannot be recovered because there is no delegate to invoke skip, nilify, or clear.
Pin Send & Receive Libraries
Explicitly bind custom send and receive ULN libraries; never rely on mutable LayerZero defaults.
Enforce Multi-DVN Configuration
Set 2 required DVNs from distinct operators (Labs + Google Cloud) + 1-of-2 optional DVNs with 15 block confirmations.
Set Executor Configuration
Define max message size and pin the LayerZero default executor address.
Set Enforced Options
Pre-allocate gas limits for lzReceive execution across both pathways.
Bidirectional Peer Wiring
Wire endpoints Robinhood EID ↔ Base EID with identical deterministic token addresses.
On-Chain getConfig Verification
Smart contract validates active getConfig values against preset; reverts immediately if any mismatch occurs.
endpoint.setDelegate(address(0))
Permanently erase endpoint delegation privileges so former owners cannot mutate pathway configurations.
renounceOwnership()
Surrender contract ownership forever. The token becomes completely autonomous and immutable.
Multi-DVN reduces risk. It doesn’t erase it.
The Kelp exploit came from RPC poisoning inside one DVN’s infrastructure. Multiple DVNs ensure a single compromised DVN cannot push an arbitrary malicious message through.
- No shielded pools (regulatory scrutiny)
- No Solana or HyperEVM until LayerZero V2 endpoints are fully standardized
- No bonding curves (direct AMM pool creation)
- No $ZKN governance token until mainnet is mature
Verification & Gate Checks
Audit DVN pathway availability on Robinhood ↔ Base & check active Reclaim verifier addresses.
Contracts on Testnet
Deploy ZKToken, ZKFactory, execute invariant tests, and simulate DVN outage failovers.
Verified Creator & Zero Unknowns
Full client-side RPC inspection interface and automated alert monitor service.
External Security Audit
Independent smart contract audit focusing on immutable recipe, ULN defaults, and badge relays.
Limited Mainnet
10 locked tokens running without incident for 2 weeks before opening public factory.
Public Mainnet
Open launchpad deployment with verified creator onboarding and omnichain bridge.