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
|
Return-Path: <btcdrak@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 109A3A7C
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 25 Aug 2015 10:15:56 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-yk0-f179.google.com (mail-yk0-f179.google.com
[209.85.160.179])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id AA8A5115
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 25 Aug 2015 10:15:55 +0000 (UTC)
Received: by ykll84 with SMTP id l84so149997391ykl.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 25 Aug 2015 03:15:55 -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
:cc:content-type;
bh=vLUTYnqo6fx9xZCUh4HpXuPgbJdyDA1Fdf0+JGcWeSk=;
b=QjgltP5sUi+d/+lN05yPkO30jFw5XBjKOJtvnvUA3KSHzDv9ufu0rb7/F821B2UiZ2
yfEwFPXK441s8sOKnCm18XSEYUUeVjvEEF0PV7MLkq2i5MVIsmctwqVKLrcwgB5yU7wF
Ka9JKUsLjmg3CQ9ir/SXiRafkoJBciRmZAWdkBVMbK+YqcEPPR6fvldq+TvVmUMOYtHH
wPcQB1OM8FXdFR4/GddoFuLriUXl765iU1dobKCm3VFF+udHyMh7nmeuah5fQTLUga9z
DQTYF6xPkwLYLGoLtJ7m9qY9Iuu9zFX1JxNNHLUu583gI5OA76mNzM77ddmvklNcqALQ
eHKA==
X-Received: by 10.129.101.7 with SMTP id z7mr34016270ywb.81.1440497755017;
Tue, 25 Aug 2015 03:15:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.94.132 with HTTP; Tue, 25 Aug 2015 03:15:35 -0700 (PDT)
In-Reply-To: <d7ba4da921d3ab55dc774dbd78c21744@xbt.hk>
References: <CADJgMztgE_GkbrsP7zCEHNPA3P6T=aSFfhkcN-q=gVhWP0vKXg@mail.gmail.com>
<CADJgMzv8G3EqLBwEYRHJZ+fO_Jwzy0koi2pJ_iNRkXmoVarGcg@mail.gmail.com>
<CABm2gDod9z6ksgaCv86qFCyKLTQSL3+oNns+__5H77hVhs05DQ@mail.gmail.com>
<CAOG=w-sbOcaogkic2i4A5eZnBQ79LUibsGy0dyKyvQg53ktY1Q@mail.gmail.com>
<55DA6470.9040301@thinlink.com>
<CAAS2fgQKQpHu-nC1uSrigDx2JLUt64p-LqidVmiuULDE0MJCFQ@mail.gmail.com>
<85537faedb1e601d243e3edb666fa844@xbt.hk>
<CAOG=w-vXFcq1bCkviWOK8nh5wz77tYy9hbLXCn8nGLzNRTSgOw@mail.gmail.com>
<d7ba4da921d3ab55dc774dbd78c21744@xbt.hk>
From: Btc Drak <btcdrak@gmail.com>
Date: Tue, 25 Aug 2015 11:15:35 +0100
Message-ID: <CADJgMzsLU5tQDLp0NWDwE6S476PdwvrOWOpn8oQ+5JPyoyi8gQ@mail.gmail.com>
To: jl2012@xbt.hk
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HK_RANDOM_ENVFROM,
HK_RANDOM_FROM, RCVD_IN_DNSWL_LOW autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [BIP-draft] CHECKSEQUENCEVERIFY - An opcode for
relative locktime
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: Tue, 25 Aug 2015 10:15:56 -0000
This BIP has been assigned BIP112 by the BIP repository maintainer. I
have updated the pull request accordingly.
Regarding the suggestion to cannibalise version, by your own
disadvantage list, we would lose fine grained control over txins which
neuters the usefulness considerably. Also using version is also ugly
because there isn't a semantic association with what we are trying to
do, whereas, sequence is associated with transaction finality and is
thus the more appropriate and logical field to use.
|
