The verification layer must be outside the attack surface of the code
it's verifying. Rust because JS can't protect itself. On-chain because
a server can be compromised. Multi-sig because one key is one point of
failure. Each technology follows from the threat model, not from
preference.
Rust
Systems
Verification in Rust because JavaScript cannot protect itself.
If the verification logic ran in JavaScript, a malicious bundle would override it before it executed. The verifier is a Rust native module inside Tauri 2's core process — it runs before the Webview sees any new code. keccak256 hashing, on-chain registry query, and bundle rejection all happen in Rust. No JS runtime can touch it. Memory safety eliminates an entire class of vulnerabilities that matter when wallets hold real funds.
~$0.000005 per publish. Sub-second finality. The cheapest trustless gate in crypto.
An Anchor program stores bundle hashes as [u8; 32] account fields on Solana. The verify instruction is a read-only CPI call — no write, no gas beyond the query fee. Solana's sub-second finality means the on-chain record is live within seconds of the developer signing. For Solana-native wallet teams, this is the natural home for the registry.
For EVM-native wallets — same model, deployed to Base or any L2.
OTARegistry.sol deploys to Base, Polygon, Arbitrum, or any EVM chain. publishUpdate writes bundle hash + rollout percent on-chain from the developer wallet. revokeUpdate is an instant, auditable rollback — not a server toggle. Swap the developer address for a Gnosis Safe and you have M-of-N governance over every update publication.
OTARegistry.sol — publishUpdate / revokeUpdate
Gnosis Safe as developer address — multi-sig governance
One compromised developer machine cannot push to your users. Ever.
The developer address in the on-chain registry is a Gnosis Safe. Publishing a bundle hash requires M-of-N co-signers — offline hardware wallets, not servers. One developer's laptop is compromised? The attacker has one key. They cannot reach M-of-N. The malicious bundle hash never makes it on-chain. Every publication is a publicly auditable multi-sig transaction that your users can independently verify.
Gnosis Safe 3-of-5 (configurable)
Offline Ledger signing — no hot keys
Every publish is a public, auditable on-chain event
Your chain, your registry. The architecture is portable.
OTARegistry.sol deploys to any EVM chain. The Anchor program runs on any Solana cluster.
If your wallet is on a different chain, talk to us — the on-chain registry model
works anywhere with a programmable ledger and a hash storage primitive.