diff options
| author | Peter Todd <pete@petertodd.org> | 2015-08-25 17:29:58 -0700 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2015-08-26 00:30:11 +0000 |
| commit | 9f39dd6a6e3a47aeee884951bd07dfd64750bb8c (patch) | |
| tree | 1b2d06b4fcb58ea0c9ef1164389146956a49578b | |
| parent | 9745c1a3accd704572f13fe5f8d0e7d52f56950e (diff) | |
| download | pi-bitcoindev-9f39dd6a6e3a47aeee884951bd07dfd64750bb8c.tar.gz pi-bitcoindev-9f39dd6a6e3a47aeee884951bd07dfd64750bb8c.zip | |
Re: [bitcoin-dev] Dynamically Controlled Bitcoin Block Size Max Cap [BIP 1xx - Draft]
| -rw-r--r-- | 4b/ada6e023d2cbeff1c2d583ccf6e44c1df6548f | 117 |
1 files changed, 117 insertions, 0 deletions
diff --git a/4b/ada6e023d2cbeff1c2d583ccf6e44c1df6548f b/4b/ada6e023d2cbeff1c2d583ccf6e44c1df6548f new file mode 100644 index 000000000..931cee6ba --- /dev/null +++ b/4b/ada6e023d2cbeff1c2d583ccf6e44c1df6548f @@ -0,0 +1,117 @@ +Return-Path: <pete@petertodd.org> +Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org + [172.17.192.35]) + by mail.linuxfoundation.org (Postfix) with ESMTPS id D59F09FB + for <bitcoin-dev@lists.linuxfoundation.org>; + Wed, 26 Aug 2015 00:30:11 +0000 (UTC) +X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 +Received: from outmail148096.authsmtp.net (outmail148096.authsmtp.net + [62.13.148.96]) + by smtp1.linuxfoundation.org (Postfix) with ESMTP id 1DFC417B + for <bitcoin-dev@lists.linuxfoundation.org>; + Wed, 26 Aug 2015 00:30:10 +0000 (UTC) +Received: from mail-c237.authsmtp.com (mail-c237.authsmtp.com [62.13.128.237]) + by punt17.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t7Q0U4Ve025506; + Wed, 26 Aug 2015 01:30:04 +0100 (BST) +Received: from muck ([50.58.157.74]) (authenticated bits=128) + by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t7Q0TxDw048867 + (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); + Wed, 26 Aug 2015 01:30:02 +0100 (BST) +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> +X-Server-Quench: 97e9a6cc-4b89-11e5-9f75-002590a135d3 +X-AuthReport-Spam: If SPAM / abuse - report it at: + http://www.authsmtp.com/abuse +X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR + bwdMdAQUGUATAgsB AmMbW1VeU117WWA7 bgpPaA1DY09JQQJu + T01BRU1TWkFvYBxl TmpZUh16fwNBNn90 ZUBnEHlcCU0rcxUu + X0oGHWQbZGY1bX0W BkddagNUcgZDfk5E aVUrVz1vNG8XDSg5 + AwQ0PjZ0MThBHWx5 UwcEKFMZSEIPD3YX QBYeBzIrGUAJDw8y + MxchK1hUNkIWOUZ6 ClozVBo9Og9aIQRG fQl+Kg5hbwARV2Ju RS9AVEACJVUA +X-Authentic-SMTP: 61633532353630.1024:706 +X-AuthFastPath: 0 (Was 255) +X-AuthSMTP-Origin: 50.58.157.74/587 +X-AuthVirus-Status: No virus detected - but ensure you scan with your own + anti-virus system. +X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW + autolearn=ham version=3.3.1 +X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on + smtp1.linux-foundation.org +Cc: bitcoin-dev@lists.linuxfoundation.org, greg@xiph.org +Subject: Re: [bitcoin-dev] Dynamically Controlled Bitcoin Block Size Max Cap + [BIP 1xx - Draft] +X-BeenThere: bitcoin-dev@lists.linuxfoundation.org +X-Mailman-Version: 2.1.12 +Precedence: list +List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org> +List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, + <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe> +List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/> +List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org> +List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help> +List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, + <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe> +X-List-Received-Date: Wed, 26 Aug 2015 00:30:12 -0000 + + +--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-- + |