You asked what explains my complete reversal. I have NEVER changed my attitude. read below pls:
I supported BIP-110 as a temporary soft fork on Bitcoin. I built
bip110.run so people could see the coalition, the census, and how the UASF was supposed to work. In my own words at the time, BIP-110 was Bitcoin minus a SegWit/Taproot data exploit.
“Bip-110 = Bitcoin - (Segwit+Taproot exploit)”
nitter.net/DrStarHeartsong/status…
“Building
bip110.run”
nitter.net/DrStarHeartsong/status…
“I built a state machine model of the process (WIP):
bip110.run/consensus”
nitter.net/DrStarHeartsong/status…
bip110.run/coalition/
nitter.net/DrStarHeartsong/status…
That is concern for Bitcoin. It is not a pledge that if miners ignore the UASF, a new hash function inherits the name.
They ignored it. The story I had bought, from Luke, Kratter, and others, was that game theory would force miners to follow nodes. I said that story was wrong, on the record, to the people I had been arguing with.
To
@adam3us, the day after the split, quoting his point that economic users control the protocol through the market:
“Adam, on this point, in hindsight, I was wrong, and you were right, imho. The defect in my model was to think that all the miners were independent variables that could flip. Dead wrong. They are all one matrix incentive-driven machine, already captured. Rock on, Bitcoin.”
nitter.net/DrStarHeartsong/status…
To
@Excellion, same day:
“Samson, on this particular point, In hindsight, I was wrong, and you were right.”
nitter.net/DrStarHeartsong/status…
I pointed back at that apology later:
“Unlike others, I took responsibility for poor judgement and being wrong about BIP-110.”
nitter.net/DrStarHeartsong/status…
What I admitted was the UASF mechanic. What I did not do was convert that loss into “Blake2b is now Bitcoin.”
The live problem, after 8/8, was miner centralization. A hardfork is a different instrument from a UASF. I said the bar is higher, and that the only justification that would matter is fixing that bug.
“This bar for a hardfork is MUCH HIGHER than for a UASF.”
nitter.net/DrStarHeartsong/status…
When Hammond asked if I was joining the fork or staying for NGU, I pointed him at the long posts and restated the claim:
“I care deeply about the miner decentralization bug, and I assert that the hardfork does not solve for it.”
nitter.net/DrStarHeartsong/status…
When Dave said changing PoW is how you “fire” miners, I answered as an engineer:
“I view this in terms of software bugs only. Was a bug in Bitcoin that allowed miners to centralize? Yes!! Does the hardfork fix the bug? No!!”
nitter.net/DrStarHeartsong/status…
Then the longer version in that same argument, which is the whole position in one paragraph:
“BIP-110 was a softfork that narrowed/refined consensus. A hardfork is a much bigger deal and needs to justify itself rhetorically as fixing the elephant in the room problem with Bitcoin, which is the ability of miners to centralize under current incentives. It could totally be addressed by a solution such as Digibyte's multi-lane, as I've been a proponent of. To NOT address the issue is to switch one mining cartel (SHA256d) for another (Blake2b) and that simply is unacceptable to most Bitcoiners. For a hardfork to have a legitimacy that grows in a measurable provable way (i.e. hashrate), imo, it would need to do better.”
nitter.net/DrStarHeartsong/status…
I did not shrug that. I built
bitcoin-hardfork.org and ran the simulations so the claim could be inspected.
“check my work, pls:
bitcoin-hardfork.org”
nitter.net/DrStarHeartsong/status…
“try it:
bitcoin-hardfork.org, you can pick your parameters”
nitter.net/DrStarHeartsong/status…
“I spent 100+ hours of due diligence on the hard fork, including modeling and simulating possible all worlds outcomes, and my decision and view is built on that diligence.”
nitter.net/DrStarHeartsong/status…
The published result, Aug 23, title first:
“BLAKE2B HARDFORK DOESN'T SOLVE THE MINER DECENTRALIZATION BUG”
Then the finding:
“I spent 100+ hours creating many-worlds socioeconomic agent simulations to get realistic about the chances of the hardfork becoming accepted as the true Bitcoin and calculating the terminal hash rate of each possible hardfork. I found one solution that was incredibly promising: multi-lane PoW like Digibyte… Unfortunately the hardfork that is on the table that everyone is following is not viable according to the simulation as I have programmed it… Will it become adopted widely? I say <0.01% chance because it doesn't provably solve the MINER DECENTRALIZATION BUG! It just turns Bitcoin into FOLLOW WHAT THE LEADER SAYS, which is exactly ETHEREUM.”
nitter.net/DrStarHeartsong/status…
That is the fork I measured. Not a hypothetical perfect fork. The Blake2b chain people are actually running.
So I did not follow it.
“BIP-110 failed… I followed it on the premise of some valid points about tail risks to the blockchain. but quickly peaced out when the group hardforked and started gaslighting ppl.”
nitter.net/DrStarHeartsong/status…
“in light of BIP-110's failure, and me definitely NOT following any hard fork…”
nitter.net/DrStarHeartsong/status…
What I still want fixed on Bitcoin is miner centralization. That is why I talk about DATUM and Ocean, not about taking the XBT ticker.
nitter.net/DrStarHeartsong/status…
The post you quoted is that same measurement applied to exchanges. You said the fork has replay protection. I said what it has is user opt-in, one-way protection. Automatic two-way replay is the standard that got other alt-bitcoin forks through custody. XBT is the ISO code and the ticker Kraken and BitMEX still use for Bitcoin. Listing Blake2b under that ticker is the affinity problem. Those are reasons a Coinbase compliance officer does not list it as XBT. They are not a new religion about which chain I “really” meant in July.
“Without automatic, two-way replay protection, which is the gold standard for alt-bitcoin forks, there is LITTLE CHANCE that any major credible exchange will list the coin. And ESPECIALLY after Blake2b coin chose
$XBT as the ticker… Using it as Blake2b's ticker screams affinity scam and becomes a major compliance issue.”
nitter.net/DrStarHeartsong/status…
nitter.net/DrStarHeartsong/status…
I ran
bip110.run to change rules on Bitcoin. I ran
bitcoin-hardfork.org to see whether this fork could earn that name. I published that it does not. That is the documentation.