Former Wall Street Quant w/ MS in Financial Engineering, Derivatives Trader & Financial Educator. Founder of @FinSummit, @Unconfiscatable & @UnderstandBit
The following is a full & detailed thread on what lead to #Bip148#UASF that ended the Scaling Debate with #SegWit Activation. ANYONE that is currently pushing for UASF #BIP110 should take the time to learn the history of this Controversial Consensus Change Method!
In this video @GrassFedBitcoin explains the danger of UASF & yet he still pushes changes proposed by Knots that maybe 20% node runners want!
* Back in 2020 from his first video, understood that Bip148 UASF was pushing changes EVERYONE Supported (unlike Knots), ๐38M Mark ๐
https://t.co/lJ50o7krWJ
- At 48 minutes he discusses that Bip148 was huge risk
- At the very end he endorses and talks about how great Taproot is.
โ @GrassFedBitcoin: why BIP-110 will succeed, the precedent BIP-148 set, and why nearly everyone will โpress the red button.โ ๐ด He begins by answering the question โcan BIP-110 fail?โ
@Admyral1@zndtoshi Saying that knots is 99% Core only makes your point more retarded, because without Core Devs, Luke would have to maintain and know every character in the code in case shit needs fixing ๐คฃ.... You guys might want to keep that part secret ๐คซ
Mostly agree, but this is still a concern for me "It leaves Core positioned to be more effective". @giacomozucco and I are in full agreement that Core needs to learn from this event and be better in the future:
- be more clear about changes
- maybe some money needs to flow for some PR
- this incident definitely could have been handled better.
But will it be a learning lesson to improve or will it embolden core devs to double down on controversial changes and next time perhaps you and I are fully against future core changes? My biggest concern with changes to Bitcoin code is that everyone wants their name forever mentioned that they wrote a critical line of code.
Listen to the entire interview! At no point did I say "don't run a node" I was explaining the limitations and perceived drunken power brainwashed plebs believe running a node gives them!
Bitcoin OG @ToneVays gives his full unfiltered take on the BIP-110 controversy:
"People have been convinced that just because you're able to spin up a node, that somehow you should be in control of the Bitcoin network, and that's a very dangerous precedent."
If you are scared to run a full archive node you are in luck! Bitcoin has an incredible ability to still validate transactions as a pruned node.... Men who are not scared will run archive nodes.... Scared cats like you are not a net positive to the network, it needs resilient node runners, not wimps.... Hard to believe people like you ever became bitcoiners as it was always a risk a transaction will make you a criminal.
The knotzis are about to get desperate as their narrative of v30 endangering Bitcoin fails. The v30 changes have already proven to be the right thing to do!
* In their final act of desperation, I expect them to add replay protection (or PoW change) and fork off into a shitcoin! They will never have a better chance! None of them have any wealth to lose anyway, but now they will have the power & relevance these leaders seek over the plebs they were able to brainwash.
** Really curious if Roger Ver was hired as a consultant based on their evolution path & all the AI sock puppet anon X accounts from 202x!
๐Great post by @L0RINC & discussion ๐
After talking with @Princey21M in Prague, I realized Bitcoin Core v30โs OP_RETURN policy change isnโt obvious to many: it didnโt create large OP_RETURN usage, it reacted to usage that already existed by removing a gate that wasnโt actually working.
Incorrect and you clearly did not listen to my interview above.... Consensus changes need consensus! Irrelevant changes that don't affect consensus (like removing Op Return limit) don't need consensus. The crazy Knotzis are trying to push an out of consensus change over an irrelevant upgrade in v30.
Back in 2017, the dangerous UASF of bip148 was avoided by the network by finally implementing Segwit in the final days, but Segwit had consensus support back in 2016, and blocked for political reasons. Not technical. There is no consensus on knots! At best it's 20% support.
Why are you not as concerned in stopping CSAM on the internet? Isn't it a bigger problem? It has never been a problem on bitcoin, maybe its a wet dream for you to be a problem so you get to look at it all the time as you point it out as a problem so you can't wait for it to appear
@satflation I don't dig inside the Bitcoin blockchain to look at CSAM just like I don't go on the dark web to look at CSAM.... It's people like you who seem to get a hard on constantly talking about CSAM ๐คท, you might want to look for some help with your mental problem.
What are the chances that Luke Dashjr is a man of his word and will never speak (or write) about Bitcoin again if RDTS attack fails?
* I know I will walk away completely if RDTS succeeds! Even considering deleting 10 years of content.
Bitcoin OG @ToneVays gives his full unfiltered take on the BIP-110 controversy:
"People have been convinced that just because you're able to spin up a node, that somehow you should be in control of the Bitcoin network, and that's a very dangerous precedent."
Completely agree on RDTS spinning off into a shitcoin with a PoW change. But I don't think this will embolden core, I actually think core will be more careful of future changes and even core supports will be paying more attention to future changes.
* Knots had a chance to change things! All they had to do was organically grow their client from 20% to 60% & grow their dev team to be as respected in quantity/quality to challenge the core team. But instead they threw it all in the trash by attempting to push through consensus rule changes out of consensus. (But I also don't see how Luke would allow the dev team to grow on Knots anyway with his ego)
That's the wrong question Roger! First you need be clear if you will drop support for RDTS or are you planning to regroup with the leaders of this Attack on Bitcoin and try again?
* If you are willing to let go of RDTS attacks on the protocol going forward I'm confident the community will have 0 problem welcoming you back.
* But if you plan to join another attack after this one fails then it's better you go ALL in Now and just fork off! If RDTS is better then how come you don't believe in it enough to go all in with skin in the game like the big blockers did?
* There is also always a chance that the RDTS attack succeeds in August and you become the new set of Bitcoin Rules. in that scenario I will put my reputation where my mouth is and never speak of Bitcoin again. Because I would be proven wrong and therefore I will STFU as I will admit I don't understand how Bitcoin works!
@adam3us@instacart30 90% of #bip110 profile accounts are anonymous AI bots of the class of 202x, it feels like it's over 10,000 of them, impossible to even block them all.
* Maybe 1 in 20 who engages with my tweets I know for a fact is a real human. I think in 3 years there will be 0 use for X.
@RubenBhodl@GrassFedBitcoin Congrats, he blocked me & everyone else who understands how Bitcoin works long ago.... I mostly only block anon accounts from 202x and people that really get out of line like Motorist.
If you believe that Segwit was a mistake then yes. The blockchain is growing faster than original design. If you believe that Segwit was the right upgrad to do then the blockchain is growing slower than what bitcoiners as a community decided in a social contract (with or without inscription garbage).
In either scenario, a $100 3T HD (from Amazon on prime day or Black Friday) will give you enough storage space for the next decade, so I don't understand the outrage from people screaming that maintaining a full archive node needs to remain affordable for a guy in the Amazon with no Internet ๐คท. If your monthly internet bill to share the data in the archived node is more expensive than storage capacity for 10 years and you are just pushing a false narrative to centralize the network to your rules.
On top of that, NO ONE has to even run a full archive node, a pruned node is all you need and maybe leave the archiving part to those who have $100 to spare ๐ค (and not $100 a month, just ONE time)
@RubenBhodl@GrassFedBitcoin Fortunately for him, his movement is too irrelevant for miners to even waste hashrate to stealth mine their chain which was one of our biggest concerns had Bip148 actually activated.
* But in that game theory scenario, Luke executes a PoW Change (his wet dream)