pull down to refresh
Guida states "I think we should have this in our back pocket in case miners decide to collude to destroy bitcoin"
Dahsjr states: "Hopefully won't come to that, but probably good to have it prepared just in case."
Mechanic states: "Makes no sense not having it prepared (for all scenarios given how centralized mining is, not just BIP110). If it ends up being necessary and we end up PoW changing...don't threaten me with a good time."
Dathon Ohm states: "I suppose if firing all of the miners is necessary to have miners that will do their job, then so be it."
All shortly after the Guida's post. I maintain that this is clearly evidence of much more than "just as an exercise" -- further, Guida himself in the OP says: "So I've rebased @LukeDashjr's 2017 PoW-change hardfork code onto a recent version of Knots"
My OP title is almost a verbatim what he said. I've been scolded by bip110 supporters before for misinterpreting what they say, so in this case I went with what I thought was a safe path.
RIP110 lol
FAFO means **** around fork off, right!
I thought adlai was a bot, I have it muted, unmute?
adlai is not a bot.
thank you for copying the tweets.
I definitely didn't mean the "just an exercise" in the context of these commits!
they obviously want leverage against miners, although it still seems to me that they are only at the stage of preparing this leverage, just in case it is needed.
I've worn out some of my patience on the topic through many conversations with guida and co, and so I'm probably a little too touchy on it these days. Certainly looking forward to some resolution in the near future.
I think the title of this SN post could have been a little more interpretive, perhaps best including the word "prepares"; it doesn't seem from a quick skim that any concrete plans have been made... if they had, I'm guessing that would've been the news.
Developers rebase old code to maintain optionality, improve orthogonality, or sometimes even just as an exercise.
anyway I give myself ten minutes to sanity-check my initial skim, starting... now!
verdict: there's not even a pull request...
sure, "where there's smoke, there's a fire", although in this case, you're only pointing at a circle of stones, long cold from the previous campsite, that were moved closer to the current one.
where's the smoke? ~lol