IBM in 1979:

CEASE ALL ECONOMIC ACTIVITY ON Zano and Confidential Assets MMEDIATELY. There will be a chain rollback of about 24 hours. More information to follow...

I mean, the ends do justify the means, but bad means lead to bad ends, so it’s just to justify the means, in the end.

I left @PubKey DC today so I can rest up and go to @PubKey NYC on Sunday to pregame for the @BTCtreasuries summit on Monday! Look forward to seeing everyone next week!

BREAKING: The FULL agenda for the #Bitcoin Treasuries Conference is now live and locked in. ⚡️ Over 50 speakers ⚡️ Over 20 talks and panels ⚡️ Over 1,000,000 BTC on the balance sheet Sept. 28. New York City. 8am ET 🔥

free idea

I should scan more codebases

Should I try to look like @DavidFBailey? I wasn’t sure if @realizingerin thought this was a good idea or a bad idea.

🚨 Bidget's hot wallets were drained. Over $350M was stolen, possibly the largest hack of the year. Security in crypto has always been hard. AI is making vulnerability research and exploits cheaper, which widens the asymmetry in favor of attackers. Closing that gap means reworking security paradigms and architectures, not just patching the last incident.

If I ran a hot wallet, I’d go offline for week(s) to do full sweeps, or greatly reduce hot wallet liquidity/exposure and do aggressive sweeps.

Filed a critical vulnerability today, under exposed to Bitcoin

During most recent episode of @hellmoneypod Bitcoin CEO @Rob1Ham says Bugle News are the best journalists in the game Follow: @bitcoin_bugle

Summary of the Pod: @AnchorWatch 🤝 @hellmoneypod

Private researcher reported a security vulnerability to Chromium on August 4. The fix went into the public source code but Chrome users never got it due to patching timelines. Two Chinese groups, apparently read that public fix, built an exploit chain from it and started phishing NGOs on September 1 using identical code. Technically an N-day but for anyone actually running Chrome, a zero-day. Here the public patch knowledge worked as an instruction manual. Open source means everyone can read the fix. With AI, some people just operationalise the knowledge faster. volexity.com/blog/2026/09/09…

You're right. THIS is Red Team.

Thanks for the careful review. This is the kind of discussion necessary for making progress on post-quantum Bitcoin. There's a lot here I agree with, though I come to a different conclusion. I agree that hash-based signatures are a good fit for Bitcoin, for the reasons the review gives. Reducing block space usage is indeed a primary design goal of SHRINCS, and it comes at a cost. The stateful path's safety depends on wallet infrastructure that the protocol does not prescribe and that still needs standards. I also agree that if block space stays cheap, the stateful path adds complexity for little benefit. But that seems unlikely, since today's fees reflect 64-byte signatures, and stateless SHRINCS signatures are about 90 times larger. High fees matter for a store of value too, because holders eventually need to spend, and we should aim for Bitcoin to remain usable by people who don't hold large amounts. Congestion and high fees are a strong argument for minimizing signature size, and stateful signatures are up to about 10 times smaller than stateless ones. Wallets can start with stateless signing and enable stateful signing for their existing keys later, without another soft fork. A block-size increase can't fully solve this. Every node has to download and validate every block, so blocks can't grow arbitrarily large. The review suggests that the stateful path lets the SHRINCS authors say the block-size concern has been addressed. The intent is rather that SHRINCS doesn't depend on a block-size increase, so that question can be discussed separately without holding up post-quantum signatures. On custody, I agree that it's unreasonable to expect replicas to share stateful signing slots safely. Some high-availability setups can still use the stateful path, for example one where a designated signer signs statefully while the replicas sign only statelessly, so failover costs larger signatures but requires no coordination of state. In practice, custodians may simply sign statelessly. The review describes stateful signing as an optimization, which fits better than the BIP's "primary path" wording. It also made me realize that calling the stateless path a "fallback" is misleading, and we're considering changing the terminology in the BIP. The review proposes considering a stateless-only scheme with a larger block size. Modified algorithms could reduce stateless signatures to roughly 4,000 bytes, about 60 times the size of a Schnorr signature instead of 90. Would that be worth departing from the SLH-DSA algorithms?

In control.

We’re in beautiful Columbus, OH for @MWBTCSummit! Stop by our booth to meet the team, learn about bitcoin custody and insurance, and grab some free AnchorWatch merch. We’d love to discuss your custody needs.

No better crew than @rodarmor and @realizingerin to sit down with for my first live in person podcast since the Red Team efforts kicked off! @hellmoneypod continues its reign as the bitcoin podcast which has its finger on the pulse of both technology and cultural vibes.

AI IS BREAKING BITCOIN Rob Hamilton spent the last six weeks on the front line of the AI War, this is his story. Casey @Rodarmor and Erin Redwing @realizingerin sit down with @Rob1Ham (CEO of @AnchorWatch and Bitcoin) to talk about AI tearing through the Bitcoin ecosystem - from the COLDCARD bug and Red Team to Chinese vs. American models and what comes next for software security. Rob’s conclusion: Bitcoin is getting hit first, but AI is coming for everyone. TIMESTAMPS 0:00 Intro & Bitcoin DEFCON Level 3:24 How Rob was recruited to the AI War 5:53 Kimi K3 changed everything 7:50 @COLDCARDwallet Hack 12:00 Red Teaming the Bitcoin Ecosystem with AI 21:13 AI Security as Spiritual War: Demons in Bitcoin's Code 24:07 The AI Great Oxygenation Event 26:30 The Gell-Mann Amnesia Effect 33:06 Collapse of the Internet Ad Revenue Model 35:06 Transhumanism 37:30 Red Teaming 42:00 Rob's Conscription to the AI War 46:52 AI Attack vs Defense 51:22 Rob is now a Bitcoin Core Contributor 54:56 Don't Trust, Verify 57:36 Pleb vs Dev: Who dominates Bitcoin culture now? 1:01:11 Covenants & Reactive Security 1:19:47 US vs China AI Models 1:27:35 Open Weight Models vs Frontier Labs 1:30:29 Math is Illegal 1:32:25 Raising Kids in the AI Era & Outro