Rusty Russell

In two days' time Julian and I will be doing an open Jitsi meeting to discuss the work on Script Restoration. Come and ask questions! 1pm Berlin time: https://www.timeanddate.com/worldclock/meetingdetails.html?year=2025&month=10&day=15&hour=11&min=0&sec=0&p1=5&p2=37

Should I run open hours for the script BIPs? Like, one a week for four weeks, you can show up and ask questions and I'll try to answer? That might help me get a feel for what is unclear or confusing. If so, what platform do I use? Never done anything like this before 😬

I strongly suspect that the bitcoin experience, even for veterans, will be quite different in ten years. BIP 353 brings names: ACINQ have a spec for supporting contact lists too. I expect vanity addresses to follow as providers get onboard. Silent payment addresses should replace all other on-chain addresses, especially deposit to exchanges. Though you'll probably just send to e.g. <acctname>@client.river.com (will this allow probing of account names? Will they use random ones instead? Or accept anything and if they get typo payments sort it out in customer service?) And BOLT12 provides reusable lightning addresses, which provide the off-chain analog of silent payments. Doesn't matter to you if the recipient is using some weird layer 2, either. BIP 353 returns both this and a silent payment address, so the sender wallet chooses.

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: nostr:nprofile1qqsr6tj32zrfn7v0pu4aheaytdnnc6rluepq73ndc2tdjzus34gat9qpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhswulwwv 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