Date: Tue, 25 Aug 2015 17:29:58 -0700
From: Peter Todd <pete@petertodd.org>
To: Chun Wang <1240902@gmail.com>
Message-ID: <20150826002958.GA10628@muck>
References: <CAED3CWipF8u5g3LUrqfyHxvEk4Lu+d12ZOJZnoBUw6iZZOg-ZQ@mail.gmail.com>
	<CAFzgq-x9GBbqARyhMgfSPc=wYeBgzXy4VUQ0D76GC+TCAxWDuA@mail.gmail.com>
	<20150825201643.GC11083@muck> <1489961.GhSFCGzPRJ@crushinator>
	<20150825203744.GB3464@muck> <55DCDB98.80004@bitcartel.com>
	<CAFzgq-zwkJ2QnnpFsf6X7L00k=+b4s--1POq_=T7j=v-+e1FTg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="1yeeQ81UyVL57Vl7"
Content-Disposition: inline
In-Reply-To: <CAFzgq-zwkJ2QnnpFsf6X7L00k=+b4s--1POq_=T7j=v-+e1FTg@mail.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]
Precedence: list


--1yeeQ81UyVL57Vl7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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?
>=20
> 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)

--=20
'peter'[:-1]@petertodd.org
000000000000000008d42f5514157c3257577e006985ea8335e4567e1bed16bd

--1yeeQ81UyVL57Vl7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQGrBAEBCACVBQJV3QiDXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAwOGQ0MmY1NTE0MTU3YzMyNTc1NzdlMDA2OTg1ZWE4MzM1
ZTQ1NjdlMWJlZDE2YmQvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQwIXyHOf0udzs5Qf/RbbX6oJBqxLcSdKtnsEufNE1
/KG0ad/2xwxXazUNkAv5y2Zn+hGFnvyJWkka6FV5XxtNNE3CbLXkShNZlX+mBFyW
D06xQ9ZHsHCCymOWlHNyiwlLxo5lJyPmARR2Lg2/qsGOcUmwQre/OjjkELDO6U5J
xSkKRvGyegE+1mFWc/nzmHNvGJkaOL17+ZMnke9hD6q/+46lHUCt9h0YVYG9Md6c
PiF5UY/UQdAeb1CVyoltidlxdg0yiHgF5Wh06xsEdJC2GYOuJQFBBcTImmaaZM8M
YC38B5rHpDs1c/7GvWQGmn5rCi0GeV0vlRNKQH6sDFVuTsZewOB7gHATrwNm4g==
=4pYO
-----END PGP SIGNATURE-----

--1yeeQ81UyVL57Vl7--