pull down to refresh

by orangesurf

BIP110 Situation Monitor I have made a BIP110 situation monitor which tracks live miner signalling data and shows the chain tip of both a core node and bip110 node to flag forks. It also has a visual guide to the activation paths & forking dynamics. Finally it has a simulator which allows you to explore the generic softfork chainsplit dynamics. The aim is to educate, particularly targeted at those who have (imo) been misled by proponents of this softfork into thinking that it is ‘the safe option’. Any suggestions would be greatly appreciated!

My Expectation While the above tool attempts to remain as balanced and neutral as possible, I have shared my expectation for what will happen (repeated below). I would be interested in hearing if others expect the same thing.

...read more at delvingbitcoin.org
explore the generic softfork chainsplit dynamics.

there's no chain split in a softfork. only losers getting rekt

reply

I'm no expert on this, but I think that can happen. Timechain just recovers by following the longest chain, right?

reply

then call it hardfork, not softfork. but bip110-ers are still calling it softfork...

reply

I'm not sure I follow what you mean. A chain split can happen at any time, with or without a soft fork or hard fork, right?

reply

The problem is this: it can happen any time though a natural occurring race or block withholding. It can also happen due to a consensus bug (like nondeterministic outcomes between different hardware architectures, or one of those mystery CPU circuit decay errors Google found to happen with 1 in a couple million Intel CPUs)

However, that is not the case here: this is programmed to split, regardless of safety measures, just a flag day bang. I think that a bunch among us that watched the cringe of the BU crap going down (which also started as a softfork), feel that when it is intentional like that, and no reasonable measures are taken to build consensus (our way or the high way) then that is not the same thing as some bug or faulty hardware or natural occurring race.

In the end, consensus is formed between humans, the machines just reflect (when not buggy) the choices the humans made. And in this case, there are humans trying to find out how far they can push things, regardless of safety, and worse, spreading a lot of FUD. They put their novel idea of what consensus should be before the existing consensus that is. It's okay to disagree and fork off. But then just be clear about what you're doing. But this being a power struggle more than an actual improvement to bitcoin prevents honesty.

reply

Ah, that makes more sense now. Haven’t really had time to dive into the details lately. Thanks for clearing that up!

reply

Most of this is clearly formulated by Mechanic in his last AMA. It's less about the spam, more about the "them". For example:

If BIP110 is not adopted by the industry who resoundingly ignore it then I'd happily say good bye to them rather than capitulate and try something else from within.

That is 100% Iatrogenesis. You create/elevate the problem, then you create a cure, then you blame everyone that doesn't take the cure. Sounds familiar from something in recent history that fucked everyone?

111 sats \ 0 replies \ @Fenix 27 Jul

at the same site you have this https://bip110.orange.surf/forking.html that could explain better about the split. The slip, if happened, reset for each “invalid” block for bip-100. so if they have 55% hash power they can enforce it as the longest pow chain

reply

Murch replied to me the other day about this and what I learned is that fork type describes not the outcome but the factual code change: "RDTS changed the rules in a compatible manner", which apparently makes this a soft fork even when it fails. It just has a high potential for a permanent chaintip split if it fails but doesn't get abandoned.

I don't like this ambiguity where you can name something one way but there is a high risk of the opposite outcome... but whatevs. Namers be naming.

reply

This fork intent is so complicated that will die in the first hours.
Will be reminded as the most lame fork in Bitcoin history.

@remindme in 1 year

reply
234 sats \ 1 reply \ @optimism 27 Jul

@remindme in 14 days

to remind Darth that this won't take a year

reply
reply
103 sats \ 0 replies \ @Kruw 27 Jul

I took a bet that they will convert the soft fork into a hard fork with a PoW adjustment (similar to BCH).

reply

Wait is the bip 110 soft fork actually happening before we ever did CTV?!?

reply

What signal would convince you that BIP110 has failed or succeeded? Is there a specific miner threshold or market reaction you are watching?