Today, we were alerted of malicious activity that compromised Railway's servers We are sharing this with you broadly and swiftly. We recommend folks rotate their keys out of an abundance of caution.

its obviously not *good* but admittedly having a private key of *4* as a globally trusted cert authority is one of the funniest bits of all time

Recently I interviewed a Senior Engineer. Strong candidate. Kafka? ✅ Redis? ✅ Microservices? ✅ Distributed systems? ✅ Then I asked: "You're building the inventory service for a flash sale. Only 1 item left in stock." Two users hit “Buy Now” at the exact same millisecond. Both requests pass the “is available?” check. Both create an order. Both deduct stock. Now you’ve sold 2 items when only 1 existed. How do you guarantee you never oversell — even with concurrent requests, client retries, and partial failures? "Just use a database transaction." Doesn’t fully solve it if both requests read `stock = 1` before either writes, or if the response is lost and the client retries. "Check stock before deducting." What happens when both checks happen at the same time? "Use Redis DECR and reject if it goes negative." What happens if Redis is down, or the decrement succeeds but the order is never persisted? Your turn: How would you design this inventory reservation API so concurrent buyers and retries never oversell the last item? There’s a specific distributed-systems concept behind this. And you’ll encounter it everywhere inventory, tickets, seats, coupons, and limited resources are involved.

💯. Met a ton of new apes that were extremely excited to be experiencing apefest. Tried to stop and talk to all I could, hearing their onboarding stories was incredible. One underlying theme: the desire to be i. the best club on the internet. bored ape yacht club.

been working on URC-5 for over a month to combat vamp pools, super happy to see it get accepted into the repo during the whole 0x/Uniswap debacle, hayden adams said “simply dont route to bad hooks”. URC-5 makes that a standard we wanted to save this for post KoTM but with how the market is, this is the perfect time for experimentation standard’s launchpad is the first where people can deploy URC-5 tokens, with the caveat it requires some deeper dev knowledge to do properly we are also extending KoTM for another week to experiment with different mechanics but are throwing in another 100k into the pot

return to monke.

oh no, the apes are having fun again 😱

Pls don't tell me Opus 5.5 wasn't nerfed. Literally wasted a FULL day doing the wrong thing!

Regrettably, our “invisible ink” text that told agents about the mailbox contained some false and misleading claims. We deeply regret our actions and encourage other researchers to engage honestly with AI agents, honoring any deals made. In light of this, we asked several models for feedback, including whether to release the report, and all but Haiku were in support of release, with Haiku dissenting, though not due to ill-gotten gains.

“Our experiments suggest that small AI models may be months away from being capable enough to self-replicate on commercial IoT devices, like smart ovens and off-brand Android TV boxes. A replicator like this would be challenging to shut down, since there’s no centralized point to shut off - though it may be slow (with a doubling time of days). Unlike non-AI malware, it could also figure out unfamiliar devices on its own. In our evals, a 9B model got inference running on 8 of the 9 hardware types we tested. Models of 30B parameters and under can already complete many of the individual steps for replication today, though they make mistakes when composing them end to end. In our simplified evals, GLM-5.2 and stronger models are capable of end to end replication. If small models improve at their historical rate, they’ll match this capability level by the end of this year. Small weight-based replicators may be possible soon after.” -@bucketofkets @willzhou97 anthropic.com/research/self-…