Nick Walters

@hkanji Comes for all of us :)

I am too old and out of date for this business

@WarOnTheRocks I'm getting a 404 on your sign in links? Persistent across two browsers

@WarforgeXP Yip. Archers were ridiculously OP...

My first PC game ever! Bought a used PC with that installed ( and Larry’s Leisure Suite. My mom dint know 😂)

@EvansRyan202 I mean presumably someone at DoD thinks the whole idea is completely loony tunes and is acting accordingly... but, also, yes.

Can we please stop leaking this stuff? Jesus H. Christ washingtonpost.com/national-secur…

@MrDylanCollins Coin market cap extreme fear greed flipped around the same time.... coinmarketcap.com/charts/fear-an…

Interesting cc @nickbrw

@Richarddd102 @DefiNiku @TrueFiDAO So if they burnt, is the circulating suppy # of Coingecko (3bn+) wrong...?

@DefiNiku @TrueFiDAO This is pretty accurate, except they didn't sell into liquidity, they burnt for eth. One line here missing a plus sign 'v13 = _SafeDiv(v6, v12 + v9)' caused it.

Truebit just got drained for 8,535 $ETH. And this one wasn’t “bad price action” or “whales dumping” - it was a straight smart contract failure that let someone print $TRU for free and arb it into real $ETH. Here’s the core mechanic (and why it’s so nasty): The attacker hit an old bonding-curve style bug where the purchase price could return 0 for a big enough mint, meaning they could “buy” huge amounts of $TRU for nothing. Then they just looped it: mint $TRU at 0 cost → sell into liquidity → repeat, until the pool was empty. The most absurd detail: the exploit path literally involved calling a function named Attack. That’s not CT slang - it’s in the on-chain trace. On-chain, you can see the footprint clearly: 8,535 $ETH extracted (roughly $26.5M at the time) massive $TRU transfers (we’re talking billions of tokens moving) as the loop runs the drain split across addresses as the $ETH gets consolidated Truebit’s side also made it clear this wasn’t “expected behaviour” - they acknowledged an exploit and even floated a bounty-style return offer (reported as 20%). Why this matters (beyond $TRU holders getting nuked): Legacy contracts are the quiet killers. You don’t need a new zero-day if there’s an old pricing function that no one stress-tested under extreme inputs. And once a loop like this works, it’s not “a one-time hack” - it’s a reusable playbook. Same pattern shows up again and again in bonding curves, illiquid pools, and unpatched DeFi code. What I’d watch next is mechanical: do the stolen funds keep routing through obfuscation rails (mixers have been mentioned in reporting) do CEXs/bridges start freezing obvious endpoints does the team ship a clean post-mortem + hard disable, or does this fade into silence If you’re still playing legacy DeFi, treat “old contract” like “live grenade”. One bad function is enough to turn a token into zero overnight. DYOR.

Blyat.

Ah shit....

Leopards. Faces.

Security design is hard part 34862. The comments on the store page for the Coinbase Wallet extension are full of people saying "CB say they'll never ask you for your seed phrase but this *DOES*!!". And when you think about it...

@ballmatthew And it occurs to me that they don't capitalize R&D, which they probably could legitimately do. Oh god, now I kinda want do a rebase of the P&Ls of major F2P platforms to have consistent accounting.

@ballmatthew Yup, read and enjoyed that too :) And MSOs did have cast iron recurring rev. Still - be interesting to see a Roblox P&L with slightly tweaked accounting policies.

@ballmatthew (also - not new - but usual quibble that Roblox "loses" money in somewhat the way that cable "lost" money while it was being built out. FCF tells a different story. Slide 138)

@ballmatthew 🤦‍♂️ofc.

@ballmatthew Ah yeah, good now. Just needed to refresh.

@ballmatthew Minor copy errors if it's helpful: Slide 59: “Has” not “gas” Slide 84: last para, *size* of the market Slide 119: I think one of the “revenues” should read “operating income” - doesn’t look like rev is down 6%

@ballmatthew Shudder to think how many slides got burned down before we even got to see them. Just got through first read. It's awesome. F*ck knows how you got the data for slide 180/1. I am impressed.

@MrMaketsu Dude, I cannot tell you how helpful this is for a thing I'm working on. Thank you thank you thank you.

Nickelodeon schedule: June 21-27, 2010. Probably the best schedule of the 2010s. Really, it's up there. Look how amazing it really is.

Are you scared? I am scared.