I had way too much fun optimizating CLN due to a Boltz report recently. Like most engineers, I love optimizing, but bitter experience means I only allow myself to do so when I have an actual problem to solve. My favourites: 1. Adding 1M entries to a sqlite3 table with two indexes: 81 seconds. Adding entries *then* creating indices: 17 seconds. 2. Optimization of O(n²) cleanup code by realizing it could be deleted entirely. I admit I continued to optimize long after their performance problem was fixed, but you gotta have *some* fun!

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.

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.

Doing another open call on Script Restoration BIPs in about 11.5 hours, 1pm Berlin. Bring your questions!

The World Clock Meeting Planner - Details

Local time for a meeting, in user selected locations.

Jitsi Meet

Join a WebRTC video conference powered by the Jitsi Videobridge

I needed some code in a third place, so I decided to extract the ~100 lines it into a single function in common code (and make it more efficient, because I had seen it in profiles under stress testing). I often write code by starting it and seeing where it leads: this is helped by modern revision control and fast compile times (I point this out because we take these for granted). First extraction went fine. Then I tried to use the same code in the second place. By the time I'd had to add four callback hooks (three of which were unneeded in the first case) I stopped. The code was different enough that the "framework with callbacks" made the code far *less* clear. Threw it away, in favor of a handful of helper routines. More code for the first case, but much more natural for the second. This took a day, on and off. But the off was important: the breaks gave me time to ask "now it's almost finished, do I like it?" and avoid being too goal driven. .

I'm going to do an open hour on the Script Restoration BIPs: All questions welcome, even (especially!) if you're not a developer. About 24 hours from now (I'll comment with the Jitsi link)

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 😬

Finally posted the 4 script restoration BIPs to the mailing list. Sorry it's taken so long!

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.