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
|
Return-Path: <luke@dashjr.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 3E288A7C
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 1 Oct 2016 05:02:57 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from zinan.dashjr.org (unknown [192.3.11.21])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id D81BA1CE
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 1 Oct 2016 05:02:56 +0000 (UTC)
Received: from ishibashi.localnet (unknown
[IPv6:2001:470:5:265:a45d:823b:2d27:961c])
(Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id C58FF38AB775;
Sat, 1 Oct 2016 05:02:10 +0000 (UTC)
X-Hashcash: 1:25:161001:rusty@rustcorp.com.au::WGxI7naw9Ke9Xtst:bwXwU
X-Hashcash: 1:25:161001:bitcoin-dev@lists.linuxfoundation.org::TbC5HRK2XHxBzHtG:bFO49
From: Luke Dashjr <luke@dashjr.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Date: Sat, 1 Oct 2016 05:02:09 +0000
User-Agent: KMail/1.13.7 (Linux/4.4.21-gentoo; KDE/4.14.24; x86_64; ; )
References: <201609230957.03138.luke@dashjr.org>
<87oa34d8fz.fsf@rustcorp.com.au>
In-Reply-To: <87oa34d8fz.fsf@rustcorp.com.au>
X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F
X-PGP-Key-ID: BD02942421F4889F
X-PGP-Keyserver: hkp://pgp.mit.edu
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201610010502.09524.luke@dashjr.org>
X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,RDNS_DYNAMIC
autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP draft: OP_CHECKBLOCKATHEIGHT
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: Sat, 01 Oct 2016 05:02:57 -0000
On Saturday, October 01, 2016 4:01:04 AM Rusty Russell wrote:
> Prefer a three-arg version (gbits-to-compare, blocknum, hash):
> - If <bits> is 0 or > 256, invalid.
> - If the hash length is not (<bits> + 7) / 8, invalid.
This means zero padding on-chain, which would be undesirable.
Rather "at most" and have the consensus implementation do the padding.
> - If the hash unused bits are not 0, invalid.
Why?
> - Otherwise <bits> of hash is compared to lower <bits> of blockhash.
Lower in what endian? Why only that endian? Why only lower? I can see a
possible use case where one wants to look at only the high bits to ensure
their transaction is only valid in a block with at least a certain
difficulty...
> This version also lets you play gambling games on-chain!
>
> Or maybe I've just put another nail in CBAH's coffin?
Or maybe resurrected it...
Luke
|
