It's been two years since the twenty-weeks-of-friends-coming-over that was Pandemic Legacy. Now the second edition of Gloomhaven has arrived, and we are planning another epic: If you haven't played this kind of thing before: the game is a progressive cooperative affair, designed to be played in two(?) hour long sessions. Obviously there are weeks you miss, but the overall experience is a season or two of regular game play. There are highs and lows as things twist and turn, and I always feel the discomfort of doing something complex and unfamiliar, but overall it's about shared experience. Must get the script BIP drafts published *before* we start this!

Don't suggest a developer resign unless you're the one who will shoulder the load. And if any bitcoin developer is thinking of stepping down over the current drama, *please * reach out to me: I've been a FOSS dev full time for over 25 years and I've been there! I'm not going to judge, but I may have a useful perspective. ❤️

$ xpay ₿rusty@rustcorp.com.au 100sat Took me longer to get DNSSEC working than to implement!

Finalizing the #CLN 25.09 rc1 now, and I'm particularly delighted by the new BIP353 plugin! I'm going to try to sneak in xpay support if I can distract the Release Captain for a moment... BIP 353 is one of the two features I really wanted this release to help push the ecosystem onwards: @Matt Corallo also has a feature in his node that supports BIP353 resolution by onion messages which I would like to spec up and support as well. Next release...

Not that anyone probably cares, but the debate on Bitcoin Treasury companies is an interesting one. It seems clear to me that the hype that pushes MNAV significantly over the value of the regulatory arbitrage is the same force that can push it dramatically below one in the case of a market panic. It's interesting to think about what happens in this scenario. And that's where the parallel to 1929 comes in. In theory, it's an opportunity to pick up cheap coins and some steep discount with mnav < 1, and some do, but then decline continues and now they're out of money. It won't help that in the hype, corporate structures have gotten intertwined and complicated and layered and there's a healthy dose of fraud. Panic continues...

JFK committed suicide

The surest way to "retire your bloodline" is castration, I would have thought.

I'm just going over here, doing anything but listening to this.

I remember a more whimsical Internet.

So, you might not have noticed, but I still haven't published my BIPs. That's mainly because I've been having too much fun with Julian who has been hacking on the benchmark code as we refine the BIP. In particular, OP_ROLL. BIP-143 already notes this opcode can be slow, and indeed, moving every stack element by one is bad enough when you can have 1000 of them. If we want to increase that to 32k, which we'd like to do so you can push every output onto the stack, for example, we can no longer ignore this problem. This is the only case where stack manipulation itself causes a significant overhead. For every other opcode we can treat it as the cost of interpreting opcode and it is not addressed by varops. Annoying! So we have benchmarks which show how much we should charge for it to limit the damage it can cause. But everything else is derived from a "bytes manipulated" model, and so I would like to extend the model a little to take into account this case. Not just for bitcoind as it is today, but for any reasonable implementation in the future.

@Blockstream Jade Plus as bling at morning coffee.

@Blockstream Jade crafternoon results. Now it's lanyard-worthy! 💚