Day 3 of grinding kimi to do a complete CCAN audit (CCAN is the repo of C snippets I maintain, used by many projects including Core Lightning).
So far, some minor issues: mainly for weird corner cases not used by any codebase I'm aware of. But many of them, and this is battle-tested code.
It's impressive how cheap this is: I'm still under $50 spend, and less than 8 hours of my own time.
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 don't think burying Coinkite is the right answer, BTW. But reality rarely listens to my opinions!
I disagree with nvk on several things, but I like his uncompromising approach to hardware and shipping. Testing for weak entropy is hard, this is absolutely a mistake I could have made, and I would also be furious if this lost my funds.
I've been trying to come up with a witty name though. Stolecard? Goxbox? "MicroSiphon inside"?
I once printed out all 4096 BIP39 words across eight pages, and used a bazillion dice rolls in pairs (red die higher, choose left, white die higher, choose right, same value re-roll), based on the method described in BIP 93 (apparently this method is due Von Neumann, figures!). First three choices were between pages, then 4 columns, then rows (I made another sheet with a tree on it to do the rows, for my own sanity).
Used a coldcard to fix up the final word. Then burned the sheets I used, which had pencil marks on them.
This was mainly to see how long it would take. The answer: long enough that I've never, ever, ever recommended this method to anyone!
Today's side quest: Great Speculations (greatspectations.com).
Useful tool for checking source code quotes against a document: I used this in CLN and it improved compliance *and* the spec itself, as well as making it easy to follow spec changes.
This is the polished and published version which handles RFCs, BIPS, and any other markdown or other docs.
What a horrible day.
I am haunted by the fear that a normal Bitcoin use can do everything right, only to lose everything because you didn't hand-roll your entropy, or upgraded your firmware because "Ledger" sent you a warning email.
๐ข
The problem with this is that well-run, boring, positive cash flow companies are really hard to find. All the obvious ones were snarfed up by previous variants of this play.
It *sounds* great, until you get to the messy reality that the firms you want don't need you. So you have to find and pitch them. And why would they say yes? Because they're looking for an exit, which is the opposite of what you said you wanted.
This is not to say it's impossible, but there's a reasonable case that it's going to be far harder than VCs think, who are used to people approaching them.
View quoted note โ
Apparently the idea that we should be our best online, not our worst, is radically outside the mainstream?
Copyright was important and unassailable until there was Real Hot Money in ignoring it.
I'm not *happy* that intellectual property got broken by greed, but TBH I'm pretty happy...
This was fun! Good chat about finer grained control and incentives to mirror....
View quoted note โ
Sometimes I forget there are old pictures of me on the internet...
LWN.net
The Linux.Conf.Au dunk tank
Linus Torvalds was not the only one to get wet in the Linux.Conf.Au dunk tank. Here
At #OsloFF several people asked when Shit Bitcoiners Say would be back, so let me put it on the record: it's hibernating during the bear market.
The account serves me as a balance, to keep things grounded. It's not there to kick people when they're down, it's to serve as a reality check. When Bitcoin is a grind it should be offering free hugs or something.
When people are extrapolating to infinity and you feel the urge to research low-gravity espresso machines for your inevitable
Bitcoin moon-citadel: I'll be back!
Hey @ODELL should I be pitching @Century Metadata to OpenSats?
I'm back wearing a Pebble watch! I loved the original, and wanted to support the reboot. Let's see how we go after a month...
This is my new Century Metadata account. I'll try to remember to post CM stuff there, not here!
View quoted note โ
This is really touching!
I loved working on #bitcoinlightning and #CLN over the years, and I leave both in excellent hands. Lightning is going to be so much more than it is now...
View quoted note โ
Official Bitcoin Twitter Self-Worth Chart
$70k: your hairline recedes.
$60k: gangrene develops.
$50k: you lose the ability to make coherent sentences, and all you can say to your panicked loved ones is "Bitcoin is digital energy".
$150k: erectile dysfunction vanishes.
$250k: your wife returns with the kids, saying she made a terrible mistake.
$500k: your long-dead father rises from the grave, tells you that he was wrong and you were right, and he's proud of you.
Starting the long walk to Vienna!
Several people have asked about the future of CLN without me at the helm. It's a worthy question, but not one I'm concerned about.
One of my key responsibilities at Blockstream was to build up a team to support CLN development and usage. I've done that, and there's no critical dependency on me any more. I expect new developments to slow for a year while the team fills gaps, but users probably won't notice, because CLN is entering a phase of refinement, not radical change.
Most of the exciting change happens one layer up now: plugins are really coming into their own, and daywalker90 has plans to rewrite reckless as a "one stop shop" plugin manager, which should really boost the ecosystem. Its telling that my last two big efforts in CLN have been in plugins: payer proofs and repeatpay are both in plugins (coming in 26.09!).
I also have 2400 branches in my git tree; I'll have scripts and an LLM churn through them all looking for the unfinished/unmerged ones to decide how many are worth exposing to the world for others to finish.
Software is never finished, but this is not my first time handing over major FOSS projects I've founded: I consider that doing that well is a key part of maintenance.
My team is ready, and they will continue to make me proud!