From: Peter Todd <pete@petertodd.org>
To: Chun Wang <1240902@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org, greg@xiph.org
Subject: Re: [bitcoin-dev] Dynamically Controlled Bitcoin Block Size Max Cap [BIP 1xx - Draft]
Date: Tue, 25 Aug 2015 17:29:58 -0700 [thread overview]
Message-ID: <20150826002958.GA10628@muck> (raw)
In-Reply-To: <CAFzgq-zwkJ2QnnpFsf6X7L00k=+b4s--1POq_=T7j=v-+e1FTg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
On Wed, Aug 26, 2015 at 05:44:46AM +0800, Chun Wang wrote:
> On Wed, Aug 26, 2015 at 5:18 AM, Simon Liu via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
> > I don't think this would work.
> >
> > If the rule is that one user can only have one vote, how do you prevent
> > a user running multiple nodes?
>
> The vote is not counted by nodes, but bitcoin amount, or probably
> better, coin-days. It works like proof-of-stake. A mix of
> proof-of-work and proof-of-stake is good.
Yup.
To implement a vote where only users with access to a full node can
vote, you'd force part of the vote to be determined by a
non-miner-committed value calculatable by anyone with a full node. For
instance, a very simple toy example that would work is just XORing your
vote with SHA256(the entire blockchain)
--
'peter'[:-1]@petertodd.org
000000000000000008d42f5514157c3257577e006985ea8335e4567e1bed16bd
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-08-26 0:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 9:07 [bitcoin-dev] Dynamically Controlled Bitcoin Block Size Max Cap [BIP 1xx - Draft] Upal Chakraborty
2015-08-25 9:19 ` Chun Wang
2015-08-25 20:16 ` Peter Todd
2015-08-25 20:26 ` Matt Whitlock
2015-08-25 20:37 ` Peter Todd
2015-08-25 21:14 ` Matt Whitlock
2015-08-25 21:28 ` Eric Voskuil
2015-08-25 21:18 ` Simon Liu
2015-08-25 21:44 ` Chun Wang
2015-08-26 0:29 ` Peter Todd [this message]
2015-08-26 6:28 ` Hector Chu
2015-08-26 12:19 ` Upal Chakraborty
2015-08-27 15:09 ` Upal Chakraborty
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=20150826002958.GA10628@muck \
--to=pete@petertodd.org \
--cc=1240902@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=greg@xiph.org \
/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