«
The current soft fork deployed in Ethereum poses a DoS vector.
The current soft fork implement is, by all accounts, the most tested piece of code to ever make it into Bitcoin.
Not exact matches
An example of a
soft fork is when the new rule states that the block size will be changed from the
current 1 MB (1,000 KB) to 800KB.
As illustrated, implementing a
soft fork does not require an update of nodes and thus allows all
current nodes to stay functional.
«What is proposed is a
soft -
fork that increases bitcoin's scalability and capacity by reorganizing data in blocks to handle the signatures separately, and in doing so takes them outside the scope of the
current block size limit,» Blockstream's Greg Maxwell wrote last December.
Hard
forks and
soft forks do virtually the same thing, so Bitcoin Core argues that
soft forks are to be preferred as they do not cause the amount of harm on the Bitcoin network as a hard
fork can potentially do since users can choose to upgrade to new features when they want to, or remain or the
current Bitcoin core version that they are on.
The lack of useful tools for estimating support for hard
forks is one of the reasons
soft forks are preferred by the
current crop of Bitcoin Core contributors.
The
current implementation of the
soft fork is aimed to blacklist what is now called the «Dark DAO» account held by the attacker.