MIME-Version: 1.0
From: "t. khan" <teekhan42@gmail.com>
Date: Thu, 2 Feb 2017 14:39:51 -0500
Message-ID: <CAGCNRJqNg9-aYG62OxTz5RJyx+JJkx-kt2odooZWs92f5teZiw@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a113e1c9c3125470547915491
Subject: [bitcoin-dev] [Pre-BIP] Community Consensus Voting System
Precedence: list

--001a113e1c9c3125470547915491
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Please comment on this work-in-progress BIP.

Thanks,

- t.k.

----------------------
BIP: ?
Layer: Process
Title: Community Consensus Voting System
Author: t.khan <teekhan42@gmail.com>
Comments-Summary: No comments yet.
Comments-URI: TBD
Status: Draft
Type: Standards Track
Created: 2017-02-02
License: BSD-2
Voting Address: 3CoFA3JiK5wxe9ze2HoDGDTmZvkE5Uuwh8  (just an example, don=
=E2=80=99t
send to this!)

Abstract
Community Consensus Voting System (CCVS) will allow developers to measure
support for BIPs prior to implementation.

Motivation
We currently have no way of measuring consensus for potential changes to
the Bitcoin protocol. This is especially problematic for controversial
changes such as the max block size limit. As a result, we have many
proposed solutions but no clear direction.

Also, due to our lack of ability to measure consensus, there is a general
feeling among many in the community that developers aren=E2=80=99t listenin=
g to
their concerns. This is a valid complaint, as it=E2=80=99s not possible to =
listen
to thousands of voices all shouting different things in a crowded
room=E2=80=94basically the situation in the Bitcoin community today.

The CCVS will allow the general public, miners, companies using Bitcoin,
and developers to vote for their preferred BIP in a way that=E2=80=99s publ=
ic and
relatively difficult (expensive) to manipulate.

Specification
Each competing BIP will be assigned a unique bitcoin address which is added
to each header. Anyone who wanted to vote would cast their ballot by
sending a small amount (0.0001 btc) to their preferred BIP's address. Each
transaction counts as 1 vote.

Confirmed Vote Multiplier:
Mining Pools, companies using Bitcoin, and Core maintainers/contributors
are allowed one confirmed vote each. A confirmed vote is worth 10,000x a
regular vote.

For example:

Slush Pool casts a vote for their preferred BIP and then states publicly
(on their blog) their vote and the transaction ID and emails the URL to the
admin of this system. In the final tally, this vote will count as 10,000
votes.

Coinbase, Antpool, BitPay, BitFury, etc., all do the same.

Confirmed votes would be added to a new section in each respective BIP as a
public record.

Voting would run for a pre-defined period, ending when a particular block
number is mined.


Rationale
Confirmed Vote Multiplier - The purpose of this is twofold; it gives a
larger voice to organizations and the people who will have to do the work
to implement whatever BIP the community prefers, and it will negate the
effect of anyone trying to skew the results by voting repeatedly.

Definitions
Miner: any individual or organization that has mined at least one valid
block in the last 2016 blocks.

Company using Bitcoin: any organization using Bitcoin for financial, asset
or other purposes, with either under development and released solutions.

Developer: any individual who has or had commit access, and any individual
who has authored a BIP

Unresolved Issues
Node voting: It would be desirable for any full node running an up-to-date
blockchain to also be able to vote with a multiplier (e.g. 100x). But as
this would require code changes, it is outside the scope of this BIP.

Copyright
This BIP is licensed under the BSD 2-clause license.

--001a113e1c9c3125470547915491
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Please comment on this work-in-progress BIP.</div><di=
v><br></div><div>Thanks,</div><div><br></div><div>- t.k.</div><div><br></di=
v><div>----------------------</div><div>BIP: ?</div><div>Layer: Process</di=
v><div>Title: Community Consensus Voting System</div><div>Author: t.khan &l=
t;<a href=3D"mailto:teekhan42@gmail.com">teekhan42@gmail.com</a>&gt;</div><=
div>Comments-Summary: No comments yet.</div><div>Comments-URI: TBD</div><di=
v>Status: Draft</div><div>Type: Standards Track</div><div>Created: 2017-02-=
02</div><div>License: BSD-2</div><div>Voting Address: 3CoFA3JiK5wxe9ze2HoDG=
DTmZvkE5Uuwh8 =C2=A0(just an example, don=E2=80=99t send to this!)</div><di=
v><br></div><div>Abstract</div><div>Community Consensus Voting System (CCVS=
) will allow developers to measure support for BIPs prior to implementation=
.</div><div><br></div><div>Motivation</div><div>We currently have no way of=
 measuring consensus for potential changes to the Bitcoin protocol. This is=
 especially problematic for controversial changes such as the max block siz=
e limit. As a result, we have many proposed solutions but no clear directio=
n.</div><div><br></div><div>Also, due to our lack of ability to measure con=
sensus, there is a general feeling among many in the community that develop=
ers aren=E2=80=99t listening to their concerns. This is a valid complaint, =
as it=E2=80=99s not possible to listen to thousands of voices all shouting =
different things in a crowded room=E2=80=94basically the situation in the B=
itcoin community today.</div><div><br></div><div>The CCVS will allow the ge=
neral public, miners, companies using Bitcoin, and developers to vote for t=
heir preferred BIP in a way that=E2=80=99s public and relatively difficult =
(expensive) to manipulate.</div><div><br></div><div>Specification</div><div=
>Each competing BIP will be assigned a unique bitcoin address which is adde=
d to each header. Anyone who wanted to vote would cast their ballot by send=
ing a small amount (0.0001 btc) to their preferred BIP&#39;s address. Each =
transaction counts as 1 vote.</div><div><br></div><div>Confirmed Vote Multi=
plier:</div><div>Mining Pools, companies using Bitcoin, and Core maintainer=
s/contributors are allowed one confirmed vote each. A confirmed vote is wor=
th 10,000x a regular vote.</div><div><br></div><div>For example:</div><div>=
<br></div><div>Slush Pool casts a vote for their preferred BIP and then sta=
tes publicly (on their blog) their vote and the transaction ID and emails t=
he URL to the admin of this system. In the final tally, this vote will coun=
t as 10,000 votes.</div><div><br></div><div>Coinbase, Antpool, BitPay, BitF=
ury, etc., all do the same.</div><div><br></div><div>Confirmed votes would =
be added to a new section in each respective BIP as a public record.</div><=
div><br></div><div>Voting would run for a pre-defined period, ending when a=
 particular block number is mined.</div><div><br></div><div><br></div><div>=
Rationale</div><div>Confirmed Vote Multiplier - The purpose of this is twof=
old; it gives a larger voice to organizations and the people who will have =
to do the work to implement whatever BIP the community prefers, and it will=
 negate the effect of anyone trying to skew the results by voting repeatedl=
y.</div><div><br></div><div>Definitions</div><div>Miner: any individual or =
organization that has mined at least one valid block in the last 2016 block=
s.</div><div><br></div><div>Company using Bitcoin: any organization using B=
itcoin for financial, asset or other purposes, with either under developmen=
t and released solutions.</div><div><br></div><div>Developer: any individua=
l who has or had commit access, and any individual who has authored a BIP</=
div><div><br></div><div>Unresolved Issues</div><div>Node voting: It would b=
e desirable for any full node running an up-to-date blockchain to also be a=
ble to vote with a multiplier (e.g. 100x). But as this would require code c=
hanges, it is outside the scope of this BIP.</div><div><br></div><div>Copyr=
ight</div><div>This BIP is licensed under the BSD 2-clause license.</div></=
div>

--001a113e1c9c3125470547915491--