News for hackers. Stuff that matters.
Re:Bottle: A Bitcoin SV Browser by kinghajj on Tuesday June 25, 2019 @05:27PM (#20279145)
Except for an early hard fork due to a transaction verification bug that allowed for infinite Bitcoins to be created, the main Bitcoin chain, as implemented by the Bitcoin Core client, has never forked, to my knowledge. It also seems disingenuous to claim that it doesn't resemble the original protocol, when the block size cap that the forks adjust, was put into place by Satoshi himself.
Re:Bottle: A Bitcoin SV Browser by shilch on Wednesday June 26, 2019 @01:21AM (#20282114)
BTC hard forked twice (or thrice if you count the one accidental hard fork) and soft forked a dozens of times. Claiming that BTC is the "main chain" is misleading. The main chain is dead for years; run the original bitcoin client, it won't sync up.
Re:Bottle: A Bitcoin SV Browser by onion-soup on Tuesday June 25, 2019 @06:47PM (#20279905)
Bitcoin core altered the protocol by removing instant transactions and adding segwit. So it’s not bitcoin anymore
Re:Bottle: A Bitcoin SV Browser by kinghajj on Tuesday June 25, 2019 @08:46PM (#20280859)
"Removing instant transactions?" Do you mean "the GUI shows 0-conf transactions as pending?" And why does adding Segwit make it "not bitcoin anymore"? Further, the Bitcoin Core devs didn't alter the protocol, the miners and users did by using the voting mechanism to enable Segwit, entirely of their own volition.
Re:Bottle: A Bitcoin SV Browser by shilch on Wednesday June 26, 2019 @01:38AM (#20282173)
> Do you mean "the GUI shows 0-conf transactions as pending?

It's not just GUI but also a miner policy which can break the use of BTC as cash - as it was originally intended.

> And why does adding Segwit make it "not bitcoin anymore"?

It's an ugly addition to the original protocol that among others breaks the definition of a coin as a chain of digital signatures. This might lead to legal issues as some people (including lawyers) pointed out.

Re:Bottle: A Bitcoin SV Browser by RustyRussell on Tuesday June 25, 2019 @06:40PM (#20279838)
FWIW, that was a soft fork, since it's backward compatible. It did cause a brief chain fork, however.