theWeb3CloudGuy.icp ∞
303 posts

theWeb3CloudGuy.icp ∞
@theweb3cloudguy
🌐 Cloud Engineer (7+ yrs) | Web2 → Web3 | Exploring ICP, ETH, BTC, HBAR | Tech believer & enthusiast 🚀







🔐 Proton CEO Andy Yen warns that the global push for age verification is the quiet death of online anonymity, because every passport scan, selfie, and biometric uploaded for "verification" inevitably ends up leaked, hacked, or monetized. He argues Big Tech and governments cannot be trusted to act as gatekeepers, and the only real protection for ID data is to never collect it in the first place.





DNS hijacks are spiking in crypto. CoW Swap and eth (dot) limo were both hit. You visit a frontend, everything looks normal, you sign a transaction and funds go to an attacker's wallet. The defense isn't better detection. It's frontends that STRUCTURALLY can't be cracked. Two approaches already exist: > IPFS + ENS: Your frontend lives on a distributed file network instead of a server. Point your web3 domain (ENS) at that file. No DNS, no central server to compromise > Fully onchain (ERC-4804): The app itself lives inside smart contracts. The frontend is served directly from Ethereum Sadly though, regular browsers can't load either. That’s why we have web3 browsers like: > Freedom Browser: open-source browser that loads ENS domains and IPFS sites natively, the same way Chrome loads (dot) com addresses > EVM Browser: built around the web3:// protocol, loads apps served directly from smart contracts on Ethereum or any EVM chain The proof of concept is already live. @z0r0zzz built zSwap is a DEX frontend deployed ENTIRELY into Ethereum contract bytecode for under $5. Anyone can load it through EVM Browser. In other words: No servers, No DNS, Nothing to hack. Every DeFi project should ship a permanent onchain frontend as a fallback. Best security is just to go straight to the contract. The tools exist. Build toward it.





reminder








