The best of crypto, tech and the open web. Curated by humans.
look the foundational problem with ethereum protocol design is that most of the people designing the protocol don't actually use ethereum themselves. you can't fix the right things if you don't use your own fucking product. you don't have enough skin in the game if you don't personally depend on the system you're designing & stand to lose money when it breaks. i understand, everything looks great from an ivory tower lol. things look very different when you're actually on the ground dealing with the consequences. if you don't use ethereum yourself but still think you're qualified to design its protocol, you're playing god with a system you don't have to live with and whose consequences you don't have to suffer.
Art Basel Paris 2026: a reality check for digital art. After speaking with Karim Crippa, the fair’s new director, one thing stuck with me: the Grand Palais wasn’t ready to host #Zero10 due to space constraints. But is space really the whole story? My take 🧵
🧵Yesterday may prove to be a turning point for security. AI is making vulnerability research dramatically faster. This favors attackers: they can find vulns and exploits at machine speed, while organizations must still inventory systems, test updates, and deploy patches without breaking production. PHP2Shell shows what that looks like. On August 11, researchers reported critical flaws in PHP runtime. They had existed for more than a decade and affects versions from PHP 5.4. An unauthenticated attacker could potentially execute code remotely, read process memory containing passwords, tokens, and API keys...🫠 Both vulnerabilities are rated CVSS 9.2. PHP powers roughly 70% of websites, totalling millions of servers. The researchers disclosed the bugs responsibly. Fixing them took about 70 days. The fix touchs 300+ files and changed nearly 12,000 lines. These were not simple mistakes. The disclosure then broke down. Amazon saw an apparent exploitation attempt on October 17, four days before the public release. This indicates a first leak. On October 20, the CVE identifiers leaked. The next morning, a supplier with advance access published patched container images more than six hours early, giving attackers a chance to study the fix while most defenders were still waiting. The official releases arrived at 14:00 UTC. Exploitation followed immediately. Cloudflare reported thousands of attempts in the ten hours before the announcement, tens of thousands in the first 45 minutes, hundreds of thousands within two hours, and millions later that day. Organizations that could not patch immediately had incomplete options: WAF rules, isolation, or taking services offline. Government portals, universities, and hospitals across Europe did exactly that. Large teams with accurate inventories and automated deployment could respond in hours. Many others still do not know where PHP is running: an old site, a vendor appliance, a forgotten container, or an unsupported internal application. AI did not make software insecure. It always was insecure. AI just changed the economics of finding and exploiting bugs and compressed the gap between disclosure and mass exploitation from days to minutes. Patching faster will not be enough. Critical systems need continuous inventory, automatic updates, isolation, memory-safe languages where possible. Our last bastion is software whose security can be demonstrated rather than assumed: formal verification, cryptography, memory-safe architectures, and secure hardware. The era in which complexity provided accidental protection is ending. PHP2Shell is not an isolated crisis. It is a preview.
This is insane. We cannot allow AI agents to go into your bank account and act independently without your authorization. But that is what’s happening right now. Left unchecked, AI could endanger the entire global financial system — including your bank account. Pause AI NOW!
SCOOP: Major U.S. banks are detecting unauthorized third-party AI agents inside customer accounts, including some attempting to take actions that appear to be independent of user instructions, sources told Axios. The findings have alarmed banking executives, who are racing to re…
Picked by the Kiwi community's upvotes. No spam, unsubscribe anytime. What's in it?
We owe you an apology. On October 20, we detected unauthorized access to our official website. After verifying API activity with Shopify, we confirmed on October 23 that a third party obtained customer shipping information. You trusted us with those details, and we're sorry we didn't keep them safe. Exposed: names, contact details, shipping addresses, and order details (items and prices). Not exposed: payment card or bank details, recovery phrases, private keys, or wallet passwords. We've blocked access, fixed the vulnerability, opened an investigation, and are emailing affected customers. Scammers may pose as Keystone by phone, text, email, or mail, offering refunds, replacement devices, or "fixes" for your order or address. None of it is from us. NEVER share your recovery phrase or private keys, and NEVER enter your recovery phrase into a device you didn't order. We will never ask for them. Don't click links in unexpected messages. Type http://keyst.one yourself. A detailed report is coming soon. Until then, trust only our official channels. If anything feels off, email support@keyst.one. We'd rather hear from you than have you take a chance. Again, we're truly sorry to everyone affected.
