1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
|
Return-Path: <hectorchu@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 09A9A87A
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 8 Aug 2015 06:36:27 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lb0-f176.google.com (mail-lb0-f176.google.com
[209.85.217.176])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5DF50A8
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 8 Aug 2015 06:36:26 +0000 (UTC)
Received: by lbbtg9 with SMTP id tg9so33449649lbb.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 07 Aug 2015 23:36:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:content-type; bh=55vYdCRmL6flb5U6w0n4OxftsXb9iFysQKcLeBGN8Q8=;
b=F17wBAk59Wyr6Faz6R84NJSjdH3aVAgFw5nJqCssUzeJfiet067svA9IUt2mi7VEqu
I4Gh29zBMncZn/UUtb65Ssn6GCSARO+FGgqB4YSY6nC1+EOiTjw//u5+QXtr1SXJcxN1
laqe7A7WIzGEAuB7YIoM1jQefUBlEvnaSstGYzCY5uF3VUn/rnmPtjQWPKN4AuS3R9Yj
I9qNLtr40rXWzpO14OWVi4HrAY3mB8xyW5xmkeXWvE6A+VONLKbbl/yDe021nQ4EZMzo
2+t8apiM31P0TdbtSERKbNOR1n7lGV9JjShic5Fz9uuh5rTyJfqiXrHFGo0b9Kk513ef
1DPw==
X-Received: by 10.152.203.172 with SMTP id kr12mr11596033lac.71.1439015784754;
Fri, 07 Aug 2015 23:36:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.22.25 with HTTP; Fri, 7 Aug 2015 23:36:04 -0700 (PDT)
In-Reply-To: <CAAO2FKEFA5ujJKe8F4-5Wnp0DCYuyHWNWhdtk5O=nCZ-zGu0rg@mail.gmail.com>
References: <CAAO2FKEFA5ujJKe8F4-5Wnp0DCYuyHWNWhdtk5O=nCZ-zGu0rg@mail.gmail.com>
From: Hector Chu <hectorchu@gmail.com>
Date: Sat, 8 Aug 2015 07:36:04 +0100
Message-ID: <CAAO2FKG-BpYA=qSQkjVVajtQWqZgXGEFEL7N8zJj=9Xu1E6SZw@mail.gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a113472faad38de051cc6f8c2
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,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
Subject: Re: [bitcoin-dev] Voting by locking coins
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: Sat, 08 Aug 2015 06:36:27 -0000
--001a113472faad38de051cc6f8c2
Content-Type: text/plain; charset=UTF-8
Also there may need to be weighting depending on how long the coins have
been locked for, to stop voting at the last minute having an undue
influence.
On 8 August 2015 at 07:27, Hector Chu <hectorchu@gmail.com> wrote:
> Has there ever been any discussion of locking coins till a certain date
> for casting votes on an issue?
>
> Say that the date for counting votes is 3 months from now. Every one who
> wants to cast a vote must lock coins until the vote closes (using CLTV). To
> increase the weight of your vote, lock more coins. Write your choice in the
> scriptPubKey or an OP_RETURN data output.
>
> On the date the vote closes the nodes tally up the coin values for the
> various vote options, and the choice with the highest total is the winner.
>
> Not saying this could be used to solve the block size issue necessarily,
> but we could have choices like:
> 1) Keep block size the same
> 2) Reduce block size by 10%.
> 3) Increase block size by 10%.
>
> The vote could be a rolling one. When the present vote is decided the vote
> for the next 3 months starts.
>
--001a113472faad38de051cc6f8c2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Also there may need to be weighting depending on how long =
the coins have been locked for, to stop voting at the last minute having an=
undue influence.</div><div class=3D"gmail_extra"><br><div class=3D"gmail_q=
uote">On 8 August 2015 at 07:27, Hector Chu <span dir=3D"ltr"><<a href=
=3D"mailto:hectorchu@gmail.com" target=3D"_blank">hectorchu@gmail.com</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Has the=
re ever been any discussion of locking coins till a certain date for castin=
g votes on an issue?<div><br></div><div>Say that the date for counting vote=
s is 3 months from now. Every one who wants to cast a vote must lock coins =
until the vote closes (using CLTV). To increase the weight of your vote, lo=
ck more coins. Write your choice in the scriptPubKey or an OP_RETURN data o=
utput.</div><div><br></div><div>On the date the vote closes the nodes tally=
up the coin values for the various vote options, and the choice with the h=
ighest total is the winner.</div><div><br></div><div>Not saying this could =
be used to solve the block size issue necessarily, but we could have choice=
s like:</div><div>1) Keep block size the same</div><div>2) Reduce block siz=
e by 10%.</div><div>3) Increase block size by 10%.</div><div><br></div><div=
>The vote could be a rolling one. When the present vote is decided the vote=
for the next 3 months starts.</div></div>
</blockquote></div><br></div>
--001a113472faad38de051cc6f8c2--
|
