by now everyone should know(including Doomad) that 148 and 91 were used and both involve mandatory rejecting non-segwit flagging blocks before segwit even activated(141) on 24th august 2017.
so lets recall some messages from a certain person who spent years denying it ever happened, even contradicting himself
first lets see him admitting it was used.. right when it happened.
Definitely not worth buying the popcorn for, heh. I had a pretty strong feeling that it wouldn't exactly be fireworks, but I thought there might be
something happening. So much hype and drama for so little action. Oh well, onto the next big drama, I guess.
Nothing has happened yet, apart from BIP148 having locked in.
Either you've got your BIP numbers mixed up or you've been listening to the wrong people. BIP91 has been locked in, BIP141 is currently on course to lock in,
but isn't there just yet. We have to wait for the 1208 blocks currently remaining in this signalling period to complete the lock in for SegWit. Once that happens, BIP148 will become completely redundant and won't be required. Some might argue that it has already served its purpose in forcing an ultimatum to begin with, though.
For those who have been reading
the announcements, it should be noted that the first post is based on circumstances that changed not too long after. Initially, there was a chance that BIP148 could result in a split, but this was mostly negated by BIP91. Today was going to be boring from the offset until BitcoinCash reared it's ugly head, but as it turned out, that's pretty boring too, heh.
//EDIT: "
The Bitcoin network has forked as of block 478559". BitcoinCash splutters into life... just.as you can see. on august 1st 2017 he was happy to admit 148 led to 91 which would in 3 weeks lead to 141(segwit)
and admits the split occured on the day everyone said it would due to the actions of the 141 91 stuff
heck there are other posts where he also admits that due to the split BCH had to change its magic to actually be an altcoin rather that a reject block orphaner fighting against bitcoin. heck he even mentions how gmaxwell had to plead to BCH to add some changes, heres one: (note the date, ill explain later)
Indeed. BCH had to make a few important changes. First and foremost was updating their network magic, so that they would not be following the BTC chain, then they needed the EDA to compensate for the lower-than-anticipated hashrate their chain had.
Either way, it takes two to tango. But I'd personally still argue that BCH announced their fork prior to agreeing to change their network magic, which is why Core responded by implementing the code they did.
the reason why they had to change the EDA, was because it wasnt its own altcoin, just borrowing blockdata. it was a split based on the 148/91 and so the split of bch begun at the same difficulty as bitcoin
(a true altcoin just copying blockdata but wanting to go-it alone without the mandatory cause, would start at a near 0 difficulty(EDA))
and then.. here he is denying things happened. (as you can tell in 2017- april 2019 date shows how he knows it happened in 2017 . and admits it in 2019.. 2 months later, below = contradicting himself)
dont feed the troll.
Is obvious that he is trolling
yep doomad is trolling
even he knows that luke JR invented the code for the mandatory split crap MONTHS before bitcoin cash was even a brainfart
Back to the point on Luke Jr, though, individual devs can do things that other devs don't support. One person's actions does not necessarily represent the views of an entire dev team. It's not a conspiracy, you flailing fruitloop. All that happened is that someone coded something you don't like and now you apparently have to spend the rest of your life bitching about it on the internet, because that's what butthurt sadcases do.
You are the only person who still cares about this "mandatory" code that wasn't mandatory in the slightest because not enough people were running it. here he is saying that no one used those bips. and the bips were not mandatory (facepalm+laugh to his own contradiction)
and for years after he was saying
"it never happened", "there is no mandatory", "bips didnt activate until after 24th aug 2017", "there was no split".. just so he can be a social drama queen showing off loyalty to some core devs
there are many many more posts where he says there was no split (although the world can see BCH exists),
yea i removed some insults from his post but they were just his usual boring ramblings. but as you can tell he is the one thats being uncivilised and contradictory. which then prompts me after years, to bite back.
again i dont feel sympathy for him playing the victim card now, because he was the instigator by doing his contradiction games just to play debater and cause reason for him to act uncivilised as part of his game.
but hey. ill give it a month and he will again forget about 148/91 before 141 and instead go back to insisting 141 activated without any mandatory bips. just so he can cause social drama for his new friends to hug him.
(not his first time with that tactic(forgetting he got debunked when he pretends nothing happened, forgetting his own admissions of what did happen))
yea all boring social drama.
his latest point of wanting to ask about devs can write any code. is to narrate that no one should/can stop core.
(something he is passionate about not wanting people to stop core from being the authority)
he then tangents to pretend that core cant mandate (due to lapse in his memory of events(the contradiction)).
but when circling back to the facts and not his narrative.
they did mandate and they got segwit activated without miners or users needing to upgrade software to actually use segwit.
because all they had to do was edit a couple bits in a block to signal something without needing to upgrade software.. "due to backward compatibility". pools were threatened to change bits because the 'limited' user that did use 148UASF were the main NYA agreement group that included some pools, merchant tools, payment services and exchanges. meaning they were the economic majority nodes of importance. .. which is why the threat worked. and on august 1st the rejected blocks caused the fork resulting in BCH, which core devs demanded they either stop, or change their 'magic' to not disrupt bitcoin
so any time you see a consensus upgrade described as "backward compatible", it means that it does not require majority to upgrade the software.
because bip148, 91, 141 did not need general users to upgrade software to cause activations of segwit. it worked by the threats of the economic nodes(exchanges/payment gateways)