OrangeSurf

Public Key

npub18h0w55nsp839ezxnggf00jd2xc6yl0ht62mf5p8wwllu8s80wdcs83ws8m

NIP-05 Address

Profile Code

nprofile1qqsrmhh22fcqncju3rf5yyhhex4rvdz0hm4a9d56qnh80l7rcrhhxugpz4mhxue69uhhyetvv9ujumn0wd68ytnwv46qz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpr9mhxue69uhhyetvv9ujumn0wd68yanfv4mjucm0d5q3vamnwvaz7tmpw3kxzuewdehhxarj9ekxzmnyqyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqpr9mhxue69uhhxarjvee8jtn0wpjku6r0danxgtnwdsgfg6ve

Publishing to

Author Public Key

npub18h0w55nsp839ezxnggf00jd2xc6yl0ht62mf5p8wwllu8s80wdcs83ws8m

Show more details

Last Notes

2026-06-05 12:45:40 UTC

I keep hearing BIP110 proponents describe their fork as being the safe option even with a minority of hashrate due to the "asymmetry" that the BIP110 chain can wipe out the legacy chain, but the legacy chain cannot wipe out the BIP110 chain.
This asymmetry is real for ANY soft fork, but it doesn't make a minority hashrate soft fork safe.
Softfork nodes reject legacy blocks, so they'll never reorg onto the legacy chain
Legacy nodes accept softfork blocks so they will reorg onto the softfork chain if it has more cumulative work.
Once again, If it has more cumulative work.
Nodes (including miner nodes) follow the most-work (valid) chain. A minority hashrate softfork chain accumulates work slower than the legacy chain.
With a minority of hashrate the BIP110 chain will not persist as the most-work chain, it will fall further and further behind over time.
The BIP110 chain could get lucky and get ahead temporarily, but over time the luck will run out and once it falls sufficiently far behind it won't ever catch up to the chain tip.