Test

@Lyn Alden your website is down. 😱😢

Just read the disclosure of a severe vulnerability in libbitcoin's `bx` tool that limits seed entropy to 32 bits.

Milk Sad: /bx full write-up

Got me wondering about security of various multi/threshold signature wallets. Traditional OP_CHECKMULTISIG adds one bit of entropy for each extra signer, given that the individual pubkeys are disclosed. A 2of2 multisig would be 33 bits of entropy and also easily identifiable as vulnerable once a spending tx is published. But using taproot and musig2, the individual pubkeys are not disclosed, so the number of bits is doubled for each extra sig. A 2of2 multisig would be 64 bits of entropy, and not easily identifiable as vulnerable. Amirite? @Murch @waxwing Haven't thought about musig2 this way before. It's a belts and suspenders type of thing in case entropy turns out to suck.

How do I setup NIP-57 for receiving zaps? I run LNbits on top of a Core Lightning node. I'd expect there's some LNbits extension for this, but can't find any. 10000 sats reward to the best (according to me) answer. #[0] #[1] #[2]

Thank you @Sjors Provoost for your work on

GitHub

Switch hardened derivation marker to h by Sjors · Pull Request #26076 · bitcoin/bitcoin

This makes it easier to handle descriptor strings manually, especially when importing from another Bitcoin Core wallet. For example the importdescr...

It's going to be an absolute life-saver in @BTC Prague when I do a workshop on using Bitcoin Core as an air-gapped signing device. Too bad the PR didn't make it into v25.0, so I'm afraid I'll have to do the workshop on master. h > '

Decided to try Bitcoin Core GUI. Kinda disappointed. This is what happens when I double-click bitcoin-qt: So in order to run the GUI you have to open a *terminal* and run $ bla/bla/bla/bitcoin-24.0.1/bin/bitcoin-qt Is there some good reason why double-clicking it doesn't work?

I'm severely uninterested in AI. I don't know why. Everyone else seem super jazzed about it.