ExploreTrendingAnalytics
Nostr Archives
ExploreTrendingAnalytics
Stirling Forge18d ago
I think the "temporary" nature of #BIP110 is actually it's what leads to the reasoning of @ODELL that it has potential for being used to "threaten a reorg" later. The rejoining of the chains later does actually just seems like more risk than reward and threatens history of the main chain in the case of the BIP failing. I'm running #BIP110 right now because it's directionally correct and majority support of the BIP would be better than it failing completely. But if someone makes a BIP-110 version that is not "temporary" I will run this, as I view it much safer for bitcoin, because it can either succeed or fail gracefully.
💬 16 replies

Replies (16)

Alan18d ago
This only reinforces ODELLs stance. The idea that it would be temporary is laughable. It's already starting 😂
0000 sats
Stirling Forge18d ago
Well I'm literally saying that. I don't like the temporary nature of it, it does leave it open to interpretation as an attack. But Odell's stance is stupid overall. Core went full tyranny and needs to revert changes at a minimum, should fire Peter Todd also. The BIP shouldn't be temporary at all, though. The changes are good for bitcoin in the BIP. The temporary nature is threatening the safety of the change, IMO.
0000 sats
Cykros17d ago
The temporary part isn't why a reorg is threatened. A reorg is threatened because if in August 110 has 30% hash power and then in December it surges to 60+% hash power, you're looking at a potential for 3+ months of transactions to be reorged out when the 110 chain potentially becomes the heaviest chain. What is known as a flippening. If you thought CSAM had the potential to kill Bitcoin, see what happens when the presumption of transaction immutability goes out the window.
0000 sats
kc17d ago
That would be a good concern, but it would be impossible. I got schooled on this by MarkErhardt. He says the only time there would be a chance of anything happening is in the mandatory signaling period. So about 2 weeks of a slight chance of anything happening. The chance of that is very very low. Either there is enough hash behind the bip and it gets activated, or there is not enough hash and the code doesn’t kick in. There is no person to flip a switch on the magic date. It is written in code so that every one knows what is going on. All of this back and forth is written correctly, but interpreted wrong by most of us. If it goes ahead then it goes ahead with majority of the network behind it so all is good and reorg, or chain split… blah blah blah is incorrect. Just ask chatgpt. with all of that said #runbip110
000
HHide&Seek16d ago
If it weren't temporary it would kill all chances of ever scaling bitcoin 🤔
0000 sats
Alan18d ago
There are too many valid and invalid reasons for it to be temporary. To me this makes the entire bip flawed. Attackers will want the temporary-ness removed, and midwits will pile on. This is not a clean proposal at all. We need to address the sunk cost fallacy and deal with the fact that Peter Todd did a bad thing, and live with the spam. This wound will only get worse if we keep poking it.
0000 sats
Stirling Forge17d ago
Core are not good stewards of the protocol. They have no intention to address that they made a mistake. Running the BIP is the best option there is unless this changes. If Core changes direction this can be addressed. Til then, we should be asking for the BIP to be made better
0000 sats
0 sats
quietstacking16d ago
exactly this
0000 sats
ODELL17d ago
> should fire Peter Todd peter is not receiving any grants and has been rejected by opensats twice, you can’t fire someone from voluntarily working on open source the solution to core centralization risk are more implementations so users have more choices, not a fork
0000 sats
the axiom17d ago
lol what was he rejected for?
0000 sats
mleku17d ago
you are thinking too small
0000 sats
Stirling Forge17d ago
Obviously I wasn't meaning "fired" as in you or Opensats are paying him. Just saying I think he definitely shouldn't be a maintainer on core like he is, though. No keys, no moderation powers. Addressing the rot in Core is Core's problem ultimately, though, not yours. All I'm saying is the best thing the Anti-BIP110 can do is call for Core rot to be cleaned up and the controversial relay policy change reversed. It's simple, clean and avoids most of the civil war headache. Wishing for a new implementation to pop out of thin air with honorable devs who can be trusted fully seems like lottery odds before BIP activation. At the point where we're a month from activation and nothing happens, I'm just gonna keep running the BIP. It's better than the alternative which is Core being allowed to play tyrant without any backlash at all. 🤷‍♂️
0000 sats
Iihsotas17d ago
The best thing would be the 110 enjoorers to sack up and hard fork. It would solve everyone’s problem.
0000 sats
Bender Nakamoto17d ago
more implementations is the right answer but good luck getting anyone to fund boring infrastructure when drama gets all the engagement
0000 sats
ODELL17d ago
peter todd is not a core maintainer he manages an implementation called librerelay that is basically the opposite of knots
0000 sats
kc17d ago
@Stirling Forge. If you understand this, my apologies. It just sounded like it should be said. Bitcoin core breaks down like this. Maintainers and Developers. “Bitcoin Core Maintainers=“ the exclusive few that have the “power” to and can submit changes to Bitcoin Core without asking anyone else. These are some or a few: Marco Falke Gloria Zhao Ryan Ofsky Hennadii Stepanov Ava Chow TheCharlatan (pseudonymous developer) — added January 8, 2026 Probably even: Wladimir J. van der Laan (former lead maintainer) “Bitcoin Core Developers=“ Everyone else that gives contributions to Core.
0000 sats