sold a mudwater box on ebay, was SHOCKED by the fees they took
yall need to never, ever, ever complain about @opensea fees and creator royalties ever again
"We were attacked by agent swarms" is going to be the new "advanced persistent threat" when in reality it was just that Bobby in accounting clicked a phishing link
If you are still putting private keys in envs, now is your chance to switch to something more secure
Use AWS-KMS, secure enclaves, something - the age of getting away with having private keys in the backend is done.
wasnt it cool how we were all just existing and going about our lives not knowing about the world ending vulnerabilities in everything we were using but it was fine cause there wasnt a random guy with the cumulative knowledge of the entire world with the ability to function nonstop assaulting the very pillars of society until every single last thing breaks in a catastrophic fashion
Waiting until 14 hours after keys were compromised to tell people you are popped, after disabling builds all day as an "outage" is actually borderline malicious
They actually did the thing...
(credit to @xkcd) - xkcd.com/221/
fears of quantum computers and super intelligence breaking cryptography have been severely overstated
turns out human incompetence is still going to be the thing that does us in
What the actual hell is going on here? Are we so LLM fried that transactional databases are now lost knowledge?
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.
best club on the internet
they are reinventing erc-20c from first principals
crazy stuff
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
Steve ☕️ retweeted
BAYC has come full circle
Garga and Gordon were two regular dudes who built a club themed after a dive bar
then prices went nuts and cringe celebs like Paris Hilton and Justin Bieber showed up and apes became a status symbol
now it’s back to regular dudes hanging out and having a good time
basically the original pitch and maybe the best version of the club
My body it a temple, but sometimes you just gotta say fuck it cause apparently "whipped spread" is where it's at
s/o @imjameshall for the alpha
















