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
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
|
Return-Path: <a.ranchalpedrosa@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id A69F1CF3
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 7 Sep 2018 07:12:44 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wr1-f66.google.com (mail-wr1-f66.google.com
[209.85.221.66])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 113E58B
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 7 Sep 2018 07:12:43 +0000 (UTC)
Received: by mail-wr1-f66.google.com with SMTP id j26-v6so13857548wre.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 07 Sep 2018 00:12:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=subject:to:cc:references:from:message-id:date:user-agent
:mime-version:in-reply-to:content-language;
bh=KMRiyhFhJZtSeybfvE4dMpxlIzpIjNeTgwXcdc6HsN4=;
b=ZxvDzf+QzOBzqw1TneDJSEPZsx5Oyll2MymqdOgD1WiAj+86F87NHR7fUakDYGzJsP
UfV5nuzk+fGf1h/NK4NQZCLNCl/YidxEa8cqq1K5V+qSPgF49bgqjuVmh+NUhjiAtuhb
jdvfWHJcT3I2jC0Lm6z/pG3/hFEeAYzoeVQ9qNUNyQ/N9yfRMy+vnkb/8qLn/W6gtEou
GNucpEZlWQYbxp6P5IMZ9pLTG9hazTR9/yaQBq/x/SlVhrBma0XpAu3Es8dN6C3fO0Qp
eZXW3pT2UrX9UiQ3MeXm+VvmU3QrYzxrbdBlyvUVwkMfVxWV1zeI8DSRW/Q89Rwu8D7P
unZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:subject:to:cc:references:from:message-id:date
:user-agent:mime-version:in-reply-to:content-language;
bh=KMRiyhFhJZtSeybfvE4dMpxlIzpIjNeTgwXcdc6HsN4=;
b=PIrqxpJnwHJyJHbnjqt8xy5DkiXT1wb284C97oh7BAis4CduUZO7agpuStNUXEQkeh
gStZU3pbctSpUP0Dv0udZe81HBvB8VvEATwR9J6j4F/4qFQEbmvWny36V9suFpKyr3LC
jJcMqhvkBadFfqODerDAI0upJ5P4o1+LqmtHo9z3JVWvEDx/y2+L5k1hTLALBJwWu9WS
Vy0Gw8C6TM5URkGeD61XLXHaUD3PpizcQC4hTha0RG8vRG8jI/XqZ1+Rw6hIl8TnLaH9
VsDGZwgjWPqwLR1faP5YXjv0v6e1xWCEEd72y0qdJqrNHTReMiKovzk1HzQu3l4s3US0
VEbA==
X-Gm-Message-State: APzg51Dgn2xSKTA1PreXcxuwCvwgiva0lvOPaKWW7t1JJ/aP3xf0p1cf
mM24ldfBHU/7OiqBzWjWM/U=
X-Google-Smtp-Source: ANB0VdZCn5TI++WEvpFeVuZmX0gdKw95E/YWDXJxldYdaWtQWrr3Sk5JSwI8EfoCDILdfZvN8NkzCw==
X-Received: by 2002:adf:aa9c:: with SMTP id
h28-v6mr5176061wrc.149.1536304362507;
Fri, 07 Sep 2018 00:12:42 -0700 (PDT)
Received: from [10.192.86.228] (clients-xsf-96.upc.es. [147.83.201.96])
by smtp.googlemail.com with ESMTPSA id
g129-v6sm8483631wmf.42.2018.09.07.00.12.41
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Fri, 07 Sep 2018 00:12:41 -0700 (PDT)
To: Brandon Smith <freedom@reardencode.com>, Gregory Maxwell <greg@xiph.org>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
References: <3d4162e0-1f8b-0f23-85fc-9d18d4352cae@gmail.com>
<CAAS2fgQqer6nMXXdcuoXE8UyJokuLTTLBwT+w0tH2+BA2gDu0w@mail.gmail.com>
<20180906203244.GQ62902@hank.reardencode.com>
From: Alejandro Ranchal Pedrosa <a.ranchalpedrosa@gmail.com>
Message-ID: <caa38174-5bd9-74dd-deaa-3feb7a10822b@gmail.com>
Date: Fri, 7 Sep 2018 09:12:40 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101
Thunderbird/57.0
MIME-Version: 1.0
In-Reply-To: <20180906203244.GQ62902@hank.reardencode.com>
Content-Type: multipart/alternative;
boundary="------------7904B80976948DC081CF3E0B"
Content-Language: en-US
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Fri, 07 Sep 2018 13:43:59 +0000
Cc: Onder.GURCAN@cea.fr
Subject: Re: [bitcoin-dev] A BIP proposal for transactions that are
'cancellable'
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, 07 Sep 2018 07:12:44 -0000
This is a multi-part message in MIME format.
--------------7904B80976948DC081CF3E0B
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Hi all,
Thank you for the link, and also to Gregory for the remarks. I did not
know about this previous proposal. I think the last paragraph of future
work is interesting:
"It may be interesting to add enhance OP_CHECKSEQUENCEVERIFY
<https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki> to
allow outputs that are spendable by Alice until time foo, always
spendable by Bob, and spendable by Joe only after time bar, or other
such cases"
Perhaps it would allow this functionality, while keeping the validity of
coins, if the new OP_zzz took an additional argument than suggested,
such that the first one is the timelimit for Alice to keep the coin (say
in the first 24 hours), and after those 24 hours the ownership goes to
the third argument, say Bob.
That is, it is not possible to use only specifying the owner in the
first 24 hours. Would this be considered harmful?
Best,
Alejandro.
On 9/6/18 10:32 PM, Brandon Smith wrote:
> ade a similar proposal about 7 months ago, and documented some of the
> discussion points here:
--------------7904B80976948DC081CF3E0B
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi all,<br>
</p>
<p>Thank you for the link, and also to Gregory for the remarks. I
did not know about this previous proposal. I think the last
paragraph of future work is interesting:</p>
<p>"It may be interesting to add enhance <a
href="https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki">OP_CHECKSEQUENCEVERIFY</a>
to allow outputs that are spendable by Alice until time foo,
always spendable by Bob, and spendable by Joe only after time bar,
or other such cases" <br>
</p>
<p>Perhaps it would allow this functionality, while keeping the
validity of coins, if the new OP_zzz took an additional argument
than suggested, such that the first one is the timelimit for Alice
to keep the coin (say in the first 24 hours), and after those 24
hours the ownership goes to the third argument, say Bob.</p>
<p>That is, it is not possible to use only specifying the owner in
the first 24 hours. Would this be considered harmful?</p>
<p>Best,</p>
<p>Alejandro.<br>
</p>
<div class="moz-cite-prefix">On 9/6/18 10:32 PM, Brandon Smith
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20180906203244.GQ62902@hank.reardencode.com">
<pre class="moz-quote-pre" wrap="">ade a similar proposal about 7 months ago, and documented some of the
discussion points here:</pre>
</blockquote>
</body>
</html>
--------------7904B80976948DC081CF3E0B--
|
