public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Dave Scotese <dscotese@litmocracy.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Wrapping up the block size debate with voting
Date: Fri, 7 Aug 2015 01:32:12 +0200	[thread overview]
Message-ID: <CAPg+sBhura_n92GErDeQVScJh6Y_J3t6KAED9mHYXjSbgMnGJw@mail.gmail.com> (raw)
In-Reply-To: <CAGLBAhf34uqzxprY37QnfhDpP4FddfRKGnTeHe+o5Zh-rguD-Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 560 bytes --]

On Fri, Aug 7, 2015 at 1:26 AM, Dave Scotese via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

"Miners can do this unilaterally" maybe, if they are a closed group, based
> on the 51% rule. But aren't they using full nodes for propagation?  In this
> sense, anyone can vote by coding.
>

They don't need to use full nodes for propagation. Miners don't care when
other full nodes hear about their blocks, only whether they (eventually)
accept them.

And yes, full nodes can change what blocks they accept. That's called a
hard fork :)

-- 
Pieter

[-- Attachment #2: Type: text/html, Size: 968 bytes --]

  reply	other threads:[~2015-08-06 23:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04  7:50 [bitcoin-dev] Wrapping up the block size debate with voting jl2012
2015-08-04  9:03 ` Pieter Wuille
2015-08-04  9:22   ` jl2012
2015-08-04  9:29   ` Hector Chu
2015-08-04  9:23 ` Venzen Khaosan
2015-08-04  9:44   ` jl2012
2015-08-04 10:22 ` Tier Nolan
2015-08-06 23:26 ` Dave Scotese
2015-08-06 23:32   ` Pieter Wuille [this message]
2015-08-07  0:37     ` Will

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=CAPg+sBhura_n92GErDeQVScJh6Y_J3t6KAED9mHYXjSbgMnGJw@mail.gmail.com \
    --to=pieter.wuille@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=dscotese@litmocracy.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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