I think I got nerd sniped into implementing online compaction for CLN's gossip store. Mainly from people agitating that we should use a DB for gossip messages.
This will speed startup and reduce memory usage. And it's only going to take me a couple of days' work, depending on how many side-cleanups I do.
It can be hard to tell a flawed implementation of a good idea from a bad idea. But trust me, this is gonna be great!
Rusty Russell
rusty@rusty.ozlabs.org
npub179e9...lz4s
Lead Core Lightning, Standards Wrangler, Bitcoin Script Restoration ponderer, coder. Full time employed on Free and Open Source Software since 1998. Joyous hacking with others for over 25 years.
I think finding a bug where printf("%*.s") was used instead of printf(".*s") was the point at which I realized that some C issues cannot be mitigated with better tooling...
I hate price talk, but if you're going to do it, please understand that "market cap" is a very rough *ceiling* on current value.
It's neither the amount of money which has gone in, nor the amount of money which can come out.
So the order of magnitude is useful to compare against other assets. But abusing it in terms of profits and losses is a category error, and I assume done mainly because it's so easy to measure.
Grump over.

Jitsi Meet
Join a WebRTC video conference powered by the Jitsi Videobridge
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:


The World Clock Meeting Planner - Details
Local time for a meeting, in user selected locations.
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!