With the ABC chain of the hash war in Bitcoin Cash convincingly maintaining the its hash lead, and with the majority of the ecosystem assigning the BCH ticker to them, things appear to be calming down.
Markets have mirrored this attitude, as the free fall in cryptocurrency prices across the board seems to have been paused at around 146 billion US dollars in total market capitalisation.
While Bitcoin Cash remains successful in maintaining the decentralisation of its development efforts, inconsistency in consensus rules as defined by different clients can be a source of multiple network vulnerabilities. In order to prevent this, developers from all client implementations must first agree on all the specifics of the proposed changes. Bitcoincash.org has historically been a good reference on the agreed upon changes.
Software clients like Bitcoin ABC, Bitcoin Unlimited, BitcoinXT and bcash have implemented the initial proposal, that nChain objected to very shortly before the planned upgrade. The uppermentioned clients are dominating the network in both hash power and node count, with no network difficulties, sans the ones induced by the hash war.
This is probably why bitcoincash.org maintainers feel confident in declaring the upgrade as successfully completed.
The website lists the following upgrade highlights:
- Remove topological transaction order constraint, and enforce canonical transaction order (also called “CTOR”)
- Enable OP_CHECKDATASIG and OP_CHECKDATASIGVERIFY opcodes
- Enforce minimum transaction size
- Enforce “push only” rule for scriptSig
- Enforce “clean stack” rule
- Automatic replay protection for future upgrades
Contrary to the announcement, CoinGeek have announced that their hash power will remain on the offensive, unless BCH loses its trading ticker – a scenario that seems highly unlikely.
However, with checkpoints also being enabled on the winning chain, preventing the most devastating potential attacks, threats of future attacks seem less daunting