Prom (@prom_io): We're building on a zk-based stack. That's not a random technical choice, it means no trust assumptions, no optimistic windows. The math either checks…

We're building on a zk-based stack. That's not a random technical choice, it means no trust assumptions, no optimistic windows. The math either checks out or it doesn't. That mindset shapes how we think about everything, including what happens before a tx even reaches our chain. The Last Mile Problem You can have the most elegant zk-circuit in existence, and it means nothing if a user signs a malicious tx from a compromised browser wallet. Billions have been lost not because protocols failed, but because the moment of signing was vulnerable. The attack surface isn't the rollup. It's the last mile. And on L2s, where transactions are cheap and frequent, users sign more often. More signing = more exposure. The math is simple. Why Hardware Wallets Are Non-Negotiable Hardware wallets isolate the signing environment completely. Keys never touch a network-connected device. Every transaction is reviewed on a trusted display: what you see is what you sign. For a zk-rollup, this is about consistency of ethos. Trustless verification shouldn't stop at the protocol layer and fall apart at the wallet. A few things that matter in practice: clear signing over blind signing, native L2 support so UX friction doesn't push users back to hot wallets, open-source firmware, and verifiable supply chain integrity. —— When you build trustless infrastructure, you owe users a trustless experience end to end. We'll have more to share on this front soon. Stay secure. Stay tuned.