Re: [bitcoin-dev] Bitcoin XT 0.11A

[Tamas Blummer <tamas@bitsofproof.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1932 bytes --]

POW is by design the voting mechanism for the valid chain continuation.

Many rightfully dislike that the same voting mechanism is used on the validity rules, since ideally
validators (non-mining full nodes), SPV user and even those having an investment in their cold wallet
would all have a vote.

That ideal voting mechanism is not yet in the protocol.

Before XT we used discussions and an informal consensus of those with commit access to github to evolve Bitcoin.
The decision, not the discussion, is now suggested to be replaced with POW vote with XT.

It is not hard to see problems with both approaches.

If XT comes closer to miner majority, validators will also be forced to take side, so they will be able to express
their vote. I think that most Bitcoin entrepreneurs will pick XT if Core has no comparable offer
to scale transactions per second.

XT, Not-XT and a Core with some not-BIP101 offer will potentially set the stage for the perfect hard fork storm.

I still believe, that the idea of Bitcoin is powerful enough to weather that storm.

Tamas Blummer

> On Aug 20, 2015, at 14:29, Milly Bitcoin via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
> 
>> Security is provided via POW.
> 
> POW is only one aspect of security and that algorithm was created by developers and adopted by miners.  Developers provide security by creating an algorithm and miners provide security by adopting it.  If the developers and miners decided to do something insecure then Bitcoin will be insecure.  POW is not some outside force.
> 
> The security of Bitcoin as a system is a very complex subject that involve a number of factors that are the result of actions by humans.
> 
> Russ
> 
> 
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> 


[-- Attachment #1.2: Type: text/html, Size: 3557 bytes --]

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]