It's called an electricity meter.

we can definitely assess

read "other means principle" I think also from cryptoeconomics. erik voskuil.

explains how resistance would actually play out, step by step

We just got to get utreexo working folks.

And Luke -- release the Files! #1278933

🫵🏼🎄✖️⭕

delegated is fine.

you coudl distinguish between fractional and full reserve delegated custody.

"Making matters worse for Sanders’ mission, crypto-to-cash desks in Dubai had adopted more sophisticated methods to evade digital tracking than he was accustomed to in Ukraine. Some desks, he said, were generating new crypto wallet addresses every other day with which to conduct their business. These frequent wallet changes were nearly impossible to keep up with because he needed to visit with the services to obtain their new addresses. "

whack a mole

I was never able to understand what problem covenants solved.

Not scaling. Not security. (vaults don't make aense to me)

Yes smart contractw / shitcoins on bitcoin, but I don't want that.

the link there was a utreexo eli5. pretty close.

utreexo team is epitome of underpromise and overdeliver.

Luke won't even admit what he's been working on as of november, totally clammed up. I guess he wants to blindside core ... or something.

there's plenty of other devs working on utreexo.

but no one is as competent / efficient as LukeDashJr.

Totally lopsided narrative and I don't understand the half of it.

he's acting retarded, because Knots fork attack was never about stopping spam to begin with, let alone solving the issue of illegal content (CSAM) - neither knots nor core actually help with that. Luke is saving bicoin by threatening to destroy it.

"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"

#ReleaseTheFiles 🫵🏼🎄✖️⭕

I don't think mechanic believes the fork exists, either that or that he is being used. Kratter probably knows and is playing along.

Szabo / Samson Mao, hard to say. Probably some PR angle for Jan3. But I would assume almost everybody on the inside knows by now.

@justin_shocknet @Murch

re "plebs can’t run nodes anymore"

plebs can run utreexo fully validating nodes.

#ReleaseTheFiles Luke! 🫵🏼🎄✖️⭕

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! 🫵🏼🎄✖️⭕

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.

🫵🏼🎄✖️⭕

Not 444.

🫵🏼🎄✖️⭕

Which he hasn't pushed, obviously. Which I guess he is so far still denying even having, despite accounts of having demo'd privately.

Which takes care of both utxo bloat and concerns over serving illegal content for the vast majority of nodes. Validate, don't cache, and move on.

SPV is a kludge, 🫵🏼🎄✖️⭕ is how it should have worked for lite nodes from the beginning. But we'll see how it develops.

No matter how crazy he acts on the surface, don't count Luke-Jr out.

The history of this stuff is important, so thanks for the pointers.

That being said, would segwit have succeeded as a hard fork? Maybe.

My point stands that filters / BIP 444 doesn't shine with the brilliance of the true Luke, the blocksize wars Luke / the historical Luke. So what is he really up to?

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.

Luke won't release it, because.... well, therein hangs a tale I suppose.

There may or may not also be a copy floating around.

I don't claim to know the truth, but I am tired of being told not to talk about this by core contributors because "it makes Luke-Jr look good." What happened to the values of whatever makes bitcoin stronger / safer, no matter who authored the PR?

I just want to be able to run a validating node on my phone, and without worrying about serving illegal content to disgusting perverts.

So I would whisper softly in the ear of anybody that actually understands the situation to stop bickering like mommy and daddy at the lawyers office and #ReleaseTheFuckingFiles 🫵🏼🎄✖️⭕

💯

If that's true, and it might well be, then there's not much to do about L2s other than resist more softforks and entryist softforks of course.

But beyond that, let a thousand stinky flowers bloom I suppose.

That pretty much eliminates 99.9% of BTCTs. I wonder if it eliminates MSTR. I think it probably does actually.

Luke is a genius. He invented frickin segwit last time bitcoin was under attack by corporate douchebags.

And now we get

": this proposal's goal is not to block all​ methods of arbitary data insertion, just the most commonly abused ones."

OK I'm sorry these are the words of a genius?

This is Luke's masterplan?

Or this is the decoy that went wrong?

OR.... this is the decoy decoy, that was always going to pop from the beginning.

There's one realistic way to give home noderunners peace of mind from hosting arbotrary data. It's not Core 30.

And it's not Knots.

When you've got bad blood in your mouth it can be hard to spit it out.

But if you don't dude this will never end.

Mistakes were made. Of course Luke is going to win this one. In the end I mean.

Every bitcoiner will see. Every noderunner will validate. Safely.

#ReleaseTheFiles Luke! 🫵🏼🎄✖️⭕

The issue isn't to grind down fake L2s, the issue is for there to be enough organic use of clean lightning that no one takes them seriously or ideally has even heard of them.

Now there is no (or little) organic need for clean lightning, because onchain fees are just so gosh darned low. That will fix itself with time... or it won't. If it doesn't, the takeaway is that not enough people care about "money for enemies" and are fine using custodial kyc bitcoin that won't depreciate with purchasing and if they got rug pulled by the custodian, boo hoo. If this lack of demand persists over many halvings, the only technical fix that occurs to me is a softfork to reduce block size, and that may not be worth the effort.

Nice writeup though. You elicited many interesting responses.