Dino

@QuantumFDN credit goes to: @rubenmarcus_dev amazing job 🤝

We just launched AEO Checker a free tool that tells you if your site is ready for the AI search era. Check yours in 10 seconds. No signup. No paywall.

The way people find information is shifting from search engines to AI answer engines. Most websites aren't ready for that shift yet aeo.js makes any site discoverable by ChatGPT, Perplexity, Claude, one npm install, fully open source. Proud of the team on this one.

@Cointelegraph $320B in stablecoins secured by cryptography that breaks under quantum attack. Sender stats are interesting, but custody security matters more when institutions ask if their assets survive to 2030. Post-quantum isn't a feature anymore, it's infrastructure.

🔥 LATEST: USDT, USDC, and USDT0 dominate stablecoin usage based on monthly sender activity, per TokenTerminal.

@WuBlockchain Lazarus took $2.02B in 2025 exploiting classical key infrastructure. Hot wallets running ECDSA are the attack surface. Fixing this requires cryptographic root changes, not just better ops. MCP threshold signatures and PQ custody primitives matter here.

Crypto payments platform Bitrefill disclosed that it suffered a cyberattack on March 1, 2026, suspected to be linked to the North Korean Lazarus Group / Bluenoroff. About 18,500 order records were accessed, involving email addresses and crypto addresses. The breach originated from a compromised employee device and leaked credentials, allowing attackers to access parts of its database and hot wallets and transfer funds. x.com/bitrefill/stat…

@0xManny4pf @QuantumFDN thanks, stay tuned for more

@QuantumFDN Great thread I can't miss out Solid asf 🔥🔥🔥

In 2026, a post-quantum secure smart wallet for EVM chains is non-negotiable. While building a PQ wallet itself, we are happy to announce that we have open-sourced a concept to everyone. PQ Thread. Link below.

@FlamezOnSol @QuantumFDN @stayymysti yes sir

@QuantumFDN @stayymysti Post-quantum security is the next step for crypto wallets. 🔐

SPHINCS+ (SLH-DSA) signatures are 7,856 bytes. That's 121x ECDSA. ML-DSA-65 signatures are 3,309 bytes, roughly 51x. On Arbitrum, L1 data posting is the dominant cost. At ~5.5 KB calldata per PQ UserOp with ML-DSA, you're looking at $2-8 per transaction. With SPHINCS+ you'd be north of $15-20, potentially more. That makes it unviable for any practical on-chain use today. SPHINCS+ is hash-based and yes, arguably more conservative from a cryptographic assumptions standpoint. We agree. That's exactly why our Quantum L1 architecture supports SLH-DSA as a cosigner hedge: if lattice math ever breaks, there's a hash-based fallback that operates on an entirely independent mathematical assumption. But for the primary signing scheme on an EVM smart wallet where users pay per transaction? ML-DSA-65 gives you NIST Level 3 security (192-bit) at a fraction of the size. It's the right trade-off between security and practicality.

@QuantumFDN why ML-DSA-65 over SPHINCS+? seems like a weird choice when SPHINCS is hash-based and arguably more conservative

Yes, the Snap in this repo requires MetaMask Flask (developer build). It's one of three signing rails we shipped in the POC alongside a Rust CLI and a WalletConnect demo. But the Snap is not our production path. We're building a standalone Chrome extension wallet with native ML-DSA-65 signing, no MetaMask dependency. Pure TypeScript using @noble/post-quantum. Passkey unlock, Google OAuth login, social recovery via on-chain guardians, ERC-4337 account abstraction through Kernel v3. The user never interacts with ML-DSA directly. Onboarding feels like any modern smart wallet: create a password, optional biometric, optional social login. The PQ layer is invisible. Testnet (Optimism Sepolia) is the first target. Base and Arbitrum follow. The MetaMask Snap in the current repo is a proof that PQ signing can work inside the existing MetaMask architecture. The native wallet is what ships to users.

@QuantumFDN the MetaMask Snap requires Flask… so devs only for now? any timeline for regular MetaMask?

@zynzynxxw @QuantumFDN @stayymysti same here

@QuantumFDN @stayymysti future ready security. excited to see how this develops✨

@jordan_dmfx @QuantumFDN @stayymysti be sure to check github repo as well,

@QuantumFDN @stayymysti I need to check this out

@BARONMOND_1 @QuantumFDN appreciate the comment

@QuantumFDN AMAZING THREAD

@itsayonotes @QuantumFDN @cryptohako we are open to suggestions :)

@QuantumFDN @cryptohako Omo, I'm happy to be part of this o, ngl Let's see what I can do to this community 🙌🏾✨

@TE_Heinz @QuantumFDN thanks

@QuantumFDN Amazing Tek @QuantumFDN 👌

@james_deli81465 @QuantumFDN @stayymysti thank you @james_deli81465

@QuantumFDN @stayymysti Beautiful article

@Original_sudais @QuantumFDN @stayymysti will be sharing more

@QuantumFDN @stayymysti This is amazing thanks for sharing

@havibanks @QuantumFDN thanks

@QuantumFDN Nice thread

@StevenAde_ @QuantumFDN let us know what do you think

@QuantumFDN Solid thread. Checking it out.

@Itsjavari @QuantumFDN @stayymysti it is very complicated on the inside haha, but the user will not see that on the outside

@QuantumFDN @stayymysti This is actually huge, finally a quantum safe wallet that isn’t complicated.

@Tsukuyom_i @QuantumFDN @stayymysti stay tuned

@QuantumFDN @stayymysti Would love to know more

@Lekandahustla @QuantumFDN more to come