Tadge Dryja

RT @ArtemisConsort: I read an interesting story about how fertility collapsed first in Anglophone countries because of a specific English-language book, “Fruits of Philosophy.” French Canada was unaffected. China is not infected with EA brainworms. You won’t be able to sell it to them. And translations won’t work, because doomerism is a specifically Western meme species: millenarianism.

I asked a friend who is in the Chinese tech scene what folks there think about “pacing the frontier” and she was like “AI safety is not really that much of a *thing* here”

"Please fix the bug first. The chain is under risk at latest commit right now. Make sure every node is patched. Then we will transfer the money back safely after confirming the fix."

Good thing we've got these >100B op_returns eh?

RT @narcelio: Parece que o ladrão tá querendo devolver "most"

RT @n1ckler: Today, we're publishing BIP SHRINCS, the first concrete proposal for a post-quantum signature scheme designed specifically for Bitcoin. The BIP draft turns what began as a rough idea into exact algorithms with an executable reference implementation. This is an important milestone: the discussion can now focus on analyzing, criticizing, and improving a concrete proposal. The BIP makes choices ranging from major design questions, such as whether to support flexible XMSS and how to balance signature size against verification time, to the many smaller decisions involved in saving a byte here or there. All of these choices are up for debate. Big thanks to Mike Casey, @conduition, @Ethan_Heilman, @kudinov_mikhail, @olkurbatov, Boris Nagaev, and @remix7531 for their contributions to the BIP. A lot more work lies ahead: - The draft BIP specifies only the cryptography. Using SHRINCS in Bitcoin Script will require a separate BIP. - We are working on a security proof for the exact construction and parameters. - Wallet integration and user experience, for example around backups and recovery after state loss, are still at an early stage. The design space remains wide open. SHRINCS is not intended to be Bitcoin's "final" signature scheme, and it is not optimal along every axis. I do think it is a very good trade-off among the options we have now. bitcoin-dev post: Draft BIP:

RT @MaelstromFund: Maelstrom is pleased to announce that Tadge Dryja ( is the 6th recipient of the Maelstrom Bitcoin Grant Program

Utreexo: Accumulate Bitcoin. A Bitcoin Twitter Thread 🧵 1/9

New releases of BTCD-based utreexod and rust-based Floresta (built with rust-bitcoin) are out and ready to try. Still in testing mode so don't put real coins on these, and software may crash. But ready for testing! 9/9

Post script - yeah this is joking :) I doubt any programmers really like spam. But Utreexo really does let you stop worrying about how big the utxo set gets. It's a great tool for L1 scalability & it's cool there are more people working on it & using it! 10/9

RT @n1ckler: We just published "Hash-based signatures for Bitcoin," a new analysis of post-quantum schemes by @kudinov_mikhail and myself at @blksresearch. This paper serves as a gentle intro to hash-based schemes and explores how to optimize them specifically for application in Bitcoin. 🧵

Probably shouldn't get into this but: To someone running a bitcoin node may seem cool, customizable, and hey if you don't want it, don't use it. But to someone *programming* that bitcoin node, it's basically spam. Nobody wants to maintain that code.

This is one of the tricky parts of the Currency of Enemies. You can write & run whatever code you want. But it can be very hard to get other people to write and maintain that code for you.

2043 is 18 years from now. 18y * 365d/y * 144blk/d = 946080blk. Even if every block for the next 18 years was nothing but 1MB of outputs (no inputs, no real transactions), you couldn't get to a 1TB utxo set.

But also... yes, UTXO set growth is a long term scalability problem in bitcoin. Also utreexo is a great way to fix it! :)

The Bitcoin UTXO set is 11 GB now. At current growth rates it will exceed 128 GB in 2035, preventing many people from running nodes. In 2043 it will exceed 1 TB, and many larger mining operations will struggle to run nodes.