There actually isn't an activation threshold in Bitcoin Classic. The hard
fork rules are active the moment you install the software. As was noted,
there aren't any release notes, so you can be forgiven for not knowing that
BIP109 support was removed and the proposal rejected. Classic recently
No, Bitcoin classic only activates if 75% of the _miners_ adopt it. That
says nothing about the broader network and indeed is much easier to achieve
through politicking, bribery, coercion, and other tomfoolery as 75% of the
hashrate is ultimately only a dozen people or so.
You have plenty of
Bitcoin Classic only changes the block format (by changing the rule
that they have to be 1MB or less). Miners are the only ones who make
blocks, so they are the only ones who mater when it comes to changing
block rules. Nodes, wallets and other software are not affected by
changing block rules.
On Saturday, 7 January 2017 21:15:11 CET Btc Drak via bitcoin-dev wrote:
> There actually isn't an activation threshold in Bitcoin Classic.
Thats partly correct.
There is just not a formal one, there very much is an informal and practical
threshold.
I, and I'm not alone in this, think that a
Le 07/01/2017 à 21:26, Chris Priest via bitcoin-dev a écrit :
> Bitcoin Classic only changes the block format (by changing the rule
> that they have to be 1MB or less). Miners are the only ones who make
> blocks, so they are the only ones who mater when it comes to changing
> block rules.
On 01/07/2017 03:10 PM, Aymeric Vitte via bitcoin-dev wrote:
> Still wondering why you guys don't care about the ridiculous number of
> full nodes, no incentive to run one and what would happen if someone
> were to control a majority of full nodes
The level of control over a majority of full
Can you guys please take this discussion elsewhere? Perhaps to
bitcoin-discuss? This is not the place to rehash discussions that have
taken place a million times already. The behavior of the network under
contentious hard forks has been discussed ad nauseum. This mailing list is
for the discussion
Its too bad you're not the one who decides what gets posted here or
not. If you don't like whats being discussed, then don't open those
emails.
On 1/7/17, Eric Lombrozo via bitcoin-dev
wrote:
> Can you guys please take this discussion elsewhere? Perhaps to
On 01/07/2017 12:26 PM, Chris Priest via bitcoin-dev wrote:
> ... it doesn't matter that 75% of hashpower is made up of a dozen
> people. That's how the system works, it's not a matter of opinion.
It's a bug, not a feature.
e
signature.asc
Description: OpenPGP digital signature
Bitcoin Classic only activates if 75% of the network adopts it. That
is not irresponsible or dangerous. It would only be dangerous if it
activates at 50%, because that would create a situation where its not
clear which side of the fork has the most proof of work.
On 1/7/17, Eric Lombrozo via
On Saturday, 7 January 2017 00:55:19 CET Eric Lombrozo wrote:
> Your release announcement does not make it clear that Bitcoin Classic is
> incompatible with the current Bitcoin network and its consensus rules.
To explain why I didn't write that;
Bitcoin Classic is not incompatible with the
The purpose of this list is Bitcoin protocol discussion of all kinds,
including consensus rules that require hard and soft forks and there
have been many discussions about both. There is also a clear technical
process for proposing, discussing and peer reviewing consensus rule
changes via the BIPs
Your release announcement does not make it clear that Bitcoin Classic is
incompatible with the current Bitcoin network and its consensus rules. It
is a hard fork on mainnet with no safe activation as well as including
other unsafe changes. There is also no BIP for the hard fork. There is also
no
Hi Tom
Please don't post release announcements for software that is
incompatible with the current bitcoin consensus rules here.
Otherwise we give green-lights to any sorts of altcoin to post their
releases here.
Thanks
> Bitcoin Classic version 1.2.0 is now available from;
>
>
14 matches
Mail list logo