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
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <j.faber@elevate.nl>) id 1Z3UcP-00088C-82
for bitcoin-development@lists.sourceforge.net;
Fri, 12 Jun 2015 19:27:57 +0000
X-ACL-Warn:
Received: from mail-la0-f51.google.com ([209.85.215.51])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z3UcN-0005gE-DF
for bitcoin-development@lists.sourceforge.net;
Fri, 12 Jun 2015 19:27:57 +0000
Received: by lacny3 with SMTP id ny3so6662512lac.3
for <bitcoin-development@lists.sourceforge.net>;
Fri, 12 Jun 2015 12:27:48 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to:cc:content-type;
bh=ir0N/2Vepsa4zS68A6NX8m9DbBg6akjgriUnWGY2fqc=;
b=N9jM7LPK+5yJsgrviIdIBn39Zco6F5WW5hnCX2qPKykS52ixEqbeTmoEVqtoGrcbAg
TVjicFmI8WICJGhjl1x0XyQEmVIPlxEr1XmcbIdkkJQ6Ydx6h7x70PrCCY/BZ3JxpfEA
R9U8OMCeaVFx8a7qPMuw4jxNzNxrPReA9ML8wbmtxvZqUS9GUMWJvjY+9PtwtCuhSKVl
UnGwW80OoLERP8QZ1aHcx/9zYEhEpxTbiHgx3V5bCC/Iw6krWHvkG74eXIMVPOnX741r
9fQizacUVJ/No1f5CGHSmMvfwGd4IkiHh4h7kyaAr6LHZwVD9SSwWqN00MEOSeZiItXm
Jrlg==
X-Gm-Message-State: ALoCoQku4V/XlgneBcv6rEh2NBJqtzRb9Y8giFRqB1loMKrutzKYACLhw1Q50r5+nMfmPwNmyZAT
X-Received: by 10.112.126.42 with SMTP id mv10mr16827245lbb.58.1434135428155;
Fri, 12 Jun 2015 11:57:08 -0700 (PDT)
MIME-Version: 1.0
References: <20150612181153.GB19199@muck>
<CAOG=w-up7-wp2NnK52jeCLvcSWvbC-iT-YRDoA=10QhU=K14-g@mail.gmail.com>
<1466351.XXvDcu7nzO@crushinator>
In-Reply-To: <1466351.XXvDcu7nzO@crushinator>
From: Jannes Faber <j.faber@elevate.nl>
Date: Fri, 12 Jun 2015 18:56:57 +0000
Message-ID: <CABeL=0g5Lq0zpwW2sHTbO+TTj84aJaDH=1wzeQdFVyhHf-QiSg@mail.gmail.com>
To: Matt Whitlock <bip@mattwhitlock.name>,
Mark Friedenbach <mark@friedenbach.org>
Content-Type: multipart/alternative; boundary=001a11c36bc6c1635d051856ac71
X-Spam-Score: 1.1 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid
X-Headers-End: 1Z3UcN-0005gE-DF
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] User vote in blocksize through fees
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 12 Jun 2015 19:27:57 -0000
--001a11c36bc6c1635d051856ac71
Content-Type: text/plain; charset=UTF-8
I'm imagining in Peter's proposal it's not the transaction votes that are
counted but only the votes in the blocks? So miners get to vote but they
risk losing money by having to exclude counter voting transactions. But
garbage transactions are no problem at all.
Note that users that want to cast a vote "pay" for that by increased
confirmation time (on average, hopefully slightly depending on the trend).
On Fri, Jun 12, 2015, 20:27 Matt Whitlock <bip@mattwhitlock.name> wrote:
> On Friday, 12 June 2015, at 11:20 am, Mark Friedenbach wrote:
> > Peter it's not clear to me that your described protocol is free of miner
> > influence over the vote, by artificially generating transactions which
> they
> > claim in their own blocks
>
> Miners could fill their blocks with garbage transactions that agree with
> their vote, but this wouldn't bring them any real income, as they'd be
> paying their own money as fees to themselves. To get real income, miners
> would have to vote in accordance with real users.
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--001a11c36bc6c1635d051856ac71
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr">I'm imagining in Peter's proposal it's not the t=
ransaction votes that are counted but only the votes in the blocks? So mine=
rs get to vote but they risk losing money by having to exclude counter voti=
ng transactions. But garbage transactions are no problem at all.</p>
<p dir=3D"ltr">Note that users that want to cast a vote "pay" for=
that by increased confirmation time (on average, hopefully slightly depend=
ing on the trend).</p>
<br><div class=3D"gmail_quote"><div dir=3D"ltr">On Fri, Jun 12, 2015, 20:27=
=C2=A0Matt Whitlock <<a href=3D"mailto:bip@mattwhitlock.name" target=3D"=
_blank">bip@mattwhitlock.name</a>> wrote:<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">On Friday, 12 June 2015, at 11:20 am, Mark Friedenbach wrote:<br>
> Peter it's not clear to me that your described protocol is free of=
miner<br>
> influence over the vote, by artificially generating transactions which=
they<br>
> claim in their own blocks<br>
<br>
Miners could fill their blocks with garbage transactions that agree with th=
eir vote, but this wouldn't bring them any real income, as they'd b=
e paying their own money as fees to themselves. To get real income, miners =
would have to vote in accordance with real users.<br>
<br>
---------------------------------------------------------------------------=
---<br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" rel=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/=
listinfo/bitcoin-development</a><br>
</blockquote></div>
--001a11c36bc6c1635d051856ac71--
|
