public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tamas Blummer <tamas@bitsofproof•com>
To: Milly Bitcoin <milly@bitcoins•info>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin XT 0.11A
Date: Thu, 20 Aug 2015 16:25:21 +0200	[thread overview]
Message-ID: <4F2015D1-1941-4934-BDD7-292B8A7C18EC@bitsofproof.com> (raw)
In-Reply-To: <55D5C843.5040204@bitcoins.info>


[-- 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 --]

  reply	other threads:[~2015-08-20 14:25 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-15 22:39 muyuubyou
2015-08-16 18:37 ` Andrew LeCody
2015-08-16 23:02 ` Cameron Garnham
2015-08-16 23:22   ` Andrew LeCody
2015-08-17  0:03     ` Cameron Garnham
2015-08-17  6:42       ` Peter Todd
2015-08-17 12:29         ` Andrew LeCody
2015-08-17 12:33           ` Eric Lombrozo
2015-08-19 10:09             ` Jorge Timón
2015-08-19 15:41               ` s7r
2015-08-19 22:28                 ` Jorge Timón
2015-08-19 22:45                   ` Adam Back
2015-08-19 23:23                     ` Peter Todd
2015-08-20 10:25                   ` s7r
2015-08-20 11:32                     ` Milly Bitcoin
2015-08-20 11:46                       ` Hector Chu
2015-08-20 12:29                         ` Milly Bitcoin
2015-08-20 14:25                           ` Tamas Blummer [this message]
2015-08-17 21:42     ` Matt Corallo
  -- strict thread matches above, loose matches on Subject: below --
2015-08-16  2:08 muyuubyou
2015-08-15 17:02 Mike Hearn
2015-08-15 17:57 ` s7r
2015-08-15 18:38 ` s7r
2015-08-15 19:21   ` Mike Hearn
2015-08-15 20:36     ` Milly Bitcoin
2015-08-15 20:47       ` Bryan Bishop
2015-08-15 21:10         ` Milly Bitcoin
2015-08-15 20:55       ` Micha Bailey
2015-08-15 21:32 ` Eric Lombrozo
2015-08-15 22:01   ` Ken Friece
2015-08-15 22:16     ` Eric Lombrozo
2015-08-15 22:27       ` Angel Leon
2015-08-15 22:28       ` Ken Friece
2015-08-15 22:55         ` Mark Friedenbach
2015-08-15 23:04           ` Ken Friece
2015-08-15 23:07             ` Eric Lombrozo
2015-08-15 23:30               ` Michael Naber
2015-08-15 23:40               ` Mark Friedenbach
2015-08-15 23:57                 ` Ken Friece
2015-08-16  0:06                 ` Milly Bitcoin
2015-08-16 13:49   ` Mike Hearn
2015-08-16 15:44     ` Anthony Towns
2015-08-16 16:07     ` Tamas Blummer
2015-08-16 16:12       ` Levin Keller
2015-08-16 17:01       ` Adam Back
2015-08-16 18:15         ` Tamas Blummer
2015-08-16 20:27 ` Eric Voskuil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F2015D1-1941-4934-BDD7-292B8A7C18EC@bitsofproof.com \
    --to=tamas@bitsofproof$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=milly@bitcoins$(echo .)info \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox