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
138
139
|
Return-Path: <keatonatron@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 905888D4
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 20 May 2016 14:31:03 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qg0-f44.google.com (mail-qg0-f44.google.com
[209.85.192.44])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E7D151EE
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 20 May 2016 14:31:02 +0000 (UTC)
Received: by mail-qg0-f44.google.com with SMTP id j18so12919641qge.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 20 May 2016 07:31:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
bh=5tvwWqe0775GAWtLaa03WveNNlfY3tVH7Cx+2cJfUeI=;
b=IXp4931uEV5E96FruBbJXjutXAZL5sKcOMUIs53Vik9zWC/msjt27dSJS0kpFGyHBc
PPYWp+2xXgg6DHQ1IBDVxU7/MsNeGzxK+/0FG3Var88t85fvxRjekKDdCXp81PWxon7F
pUFGA7jDwJzv2ieLTqRzNMLJBpX6hANPYltN+xK9BX1hqjrSdrNgtQL03UacJsF0zAR4
Syj8GRv+yIX1oIP6+pqOUKuW685+CJUC8GEu9PS6IfPVeUBDxBPUuGnjznxvCy1Vaskv
kDJSN4lyTr8mBCvHJmoaeQlUg/VHQjk6USFq4cNvSEArkCr2POk97vbihIWiPpob0aoG
d+rg==
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;
bh=5tvwWqe0775GAWtLaa03WveNNlfY3tVH7Cx+2cJfUeI=;
b=d5V8fGMTdLGFXNnsqN2kDiNvKr19uMnd1A0kHDVFiVXMvX1yKEeHKT1YXDDDueoQcx
t5kRZDhK46dXuyNfi+oBlDsKeksTcKlRnZ1eWJVqGQiGlvhewZKCHSa92jWQEYzvAJ0v
4gzPwcFKUqLX73xHe4zaAbAMPwQZ1M7QalW1X6KUzAGYUDQeblOIvo0t6cYE7DNY2Jlp
djPHT5FfKLS1dh30UIViNKQeIroFHDIp+G1mMkG6WNI8a8haFWiIOHnLM5XdqxbVpDjb
ba2mAOTUzSkupScor9y/Nk6wciEN0gDW+THsV7XWYg4hFz3CfZnFA0LDZYUzn0zEK1E0
dQ4A==
X-Gm-Message-State: AOPr4FV48o7Y/5QTxR77VYLdgWsiCk4ridLFcsG8gSiz2P+N+qQcfww6yy7tQquHF3yeRS86Xciv4yBrMbg2Hg==
X-Received: by 10.140.201.143 with SMTP id w137mr3674336qha.66.1463754662186;
Fri, 20 May 2016 07:31:02 -0700 (PDT)
MIME-Version: 1.0
References: <CAAEDBiEB_RXBjrLB8kDb52bJOwZK-arVeHA_9LyoDgAraLKHNg@mail.gmail.com>
<CBBB62CD-2E30-4C9F-962E-3F340B29EDA7@xbt.hk>
In-Reply-To: <CBBB62CD-2E30-4C9F-962E-3F340B29EDA7@xbt.hk>
From: James MacWhyte <macwhyte@gmail.com>
Date: Fri, 20 May 2016 14:30:52 +0000
Message-ID: <CAH+Axy5G9j-0TXE6dCQ69pH=TKPDtFibfCf_tZ87o88FVd0pxw@mail.gmail.com>
To: Johnson Lau <jl2012@xbt.hk>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
Matthew Roberts <matthew@roberts.pm>
Content-Type: multipart/alternative; boundary=001a11426766ad94bb053346f05b
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] BIP: OP_PRANDOM
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol 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: Fri, 20 May 2016 14:31:03 -0000
--001a11426766ad94bb053346f05b
Content-Type: text/plain; charset=UTF-8
Matthew,
Other than gambling, do you have any specific examples of how this could be
useful?
On Fri, May 20, 2016, 20:34 Johnson Lau via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Using the hash of multiple blocks does not make it any safer. The miner of
> the last block always determines the results, by knowing the hashes of all
> previous blocks.
>
>
> == Security
>
> Pay-to-script-hash can be used to protect the details of contracts that
> use OP_PRANDOM from the prying eyes of miners. However, since there is also
> a non-zero risk that a participant in a contract may attempt to bribe a
> miner the inclusion of multiple block hashes as a source of randomness is a
> must. Every miner would effectively need to be bribed to ensure control
> over the results of the random numbers, which is already very unlikely. The
> risk approaches zero as N goes up.
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--001a11426766ad94bb053346f05b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr">Matthew,</p>
<p dir=3D"ltr">Other than gambling, do you have any specific examples of ho=
w this could be useful?</p>
<br><div class=3D"gmail_quote"><div dir=3D"ltr">On Fri, May 20, 2016, 20:34=
Johnson Lau via bitcoin-dev <<a href=3D"mailto:bitcoin-dev@lists.linuxf=
oundation.org">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div>U=
sing the hash of multiple blocks does not make it any safer. The miner of t=
he last block always determines the results, by knowing the hashes of all p=
revious blocks.</div></div><div style=3D"word-wrap:break-word"><div><br></d=
iv><div><blockquote type=3D"cite"><div dir=3D"ltr"><p style=3D"margin-botto=
m:0in;line-height:100%"><br>
</p><p style=3D"margin-bottom:0in;line-height:100%">=3D=3D Security</p><p s=
tyle=3D"margin-bottom:0in;line-height:100%">Pay-to-script-hash
can be used to protect the details of contracts that use OP_PRANDOM
from the prying eyes of miners. However, since there is also a
non-zero risk that a participant in a contract may attempt to bribe a
miner the inclusion of multiple block hashes as a source of
randomness is a must. Every miner would effectively need to be bribed
to ensure control over the results of the random numbers, which is
already very unlikely. The risk approaches zero as N goes up.</p></div></bl=
ockquote></div><br></div>_______________________________________________<br=
>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>
--001a11426766ad94bb053346f05b--
|
