What you're describing is a hashpower activated soft fork to censor
transactions, in response to a user activated soft fork that the majority of
hashpower disagrees with.
It is always possible for a majority of hashpower to censor transactions they
disagree with. Users may view that as an attac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 4 August 2015 11:12:36 PM AEST, Gavin Andresen via bitcoin-dev
wrote:
>On Tue, Aug 4, 2015 at 7:27 AM, Pieter Wuille via bitcoin-dev <
>bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> I would say that things already demonstrately got terrib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
>I don't understand the situation here. Is the assumption of a group of
>miners suddenly switching (for example, they realise that they didn't
>intend to support the new rules)?
Or they're economically rational miners, and a large difficulty decrea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I've seen a lot of talk on this list debating the role of Bitcoin Core and its
maintainers WRT consensus, typically focused around whether they can
technically force anyone to run their code (of course, they can't.)
I've yet to see the discussi
