pull down to refresh
0 sats \ 2 replies \ @standardcrypto 21h \ parent \ on: New BIP-444: Reduce Data Temporary Soft Fork Proposal bitcoin
444 is the decoy / bait, and yeah of course that doesn't make him look good at all.
But we both know that isn't what we're actually talking about.
Say what you will about Luke, he understands the incentives structure of bitcoin.
And the man can code.
🫵🏼🎄✖️⭕
The rumors have been swirling about a secret knots code fork that actually fixes the utxo bloat, at least since Bitcoin Prague 2024. Core won't talk about it, because they can't stomach being scooped by someone they look down on as a. crank, but who has the chops and the work ethic to actually write the code.
^ seems at odds with
But we both know that isn't what we're actually talking about.
So, what are we talking about then?
reply
OK, so now we are playing "I don't know what Luke-Jr Did Last Summer."
I'll play along.
As we know, neither Knots nor the main v30 core client actually addresses utxo bloat, not to speak of illegal or disgusting content. Pruning helps but not that much. What actually does help is utreexo, which iiuc has been implemented in various fringe clients but not core.
Utreexo not only helps, it makes the entire debate all but irrelevant for the majority of noderunners. Someone needs to keep old blocks around of course, but I'm not too worried about losing the last copy of the blockchain.
So to be clear, what are talking about apparently is a private Knots fork with utreexo -- batteries included, fully regression tested, and from the rumors I have heard massively more performant tuned than libfloresta, whatever Tadge Dryja originally produced, and the various other test clients like mit-dci/utreexo which I guess was in go.
It's possible Luke has been working on this since he had the lightbulb about making segwit a softfork. It was always clear that utxo bloat was going to be a problem, and nobody has been more publicly focused on this than Luke, with the filters and tonal bitcoin and whatever all else he has been up to.
Coding, testing and packaging this must have been a gargantuan task in man years.
I don't know if anybody else could have pulled it off singlehandedly, other than him.
This is why I believe the rumors, and also that the time has come to set rivalry and resentment aside and speak honestly about what has and hasn't been written, tested, and is ready to push.
The only story that makes sense to me is that this entire filters fork has been drama fodder from Luke to get the attention on his utreexo pull request when he finally makes it... if he makes it. Or maybe that's how it started and now he's changed his mind because of... well it's always been hard to understand his thought process. But the motives don't matter, what matters is finally getting this published and running on a first batch of core nodes -- which should be easy enough to backport from knots (reversing the usual direction, which is amusing in its own right).
Or is everybody just going to keep acting like the demos in 2024 never happened?
#ReleaseTheFiles! 🫵🏼🎄✖️⭕
reply