summaryrefslogtreecommitdiff
path: root/4d/cd5788af97225fce06bd72ff31a28bf4a49457
blob: 20938ef0e42080e0ddb7184ed156028f6cd4f314 (plain)
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
Return-Path: <jlrubin@mit.edu>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 9CBFEC000E;
 Thu,  8 Jul 2021 15:48:30 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id 7F2C64000B;
 Thu,  8 Jul 2021 15:48:30 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3,
 SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from smtp2.osuosl.org ([127.0.0.1])
 by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id EYPU10DrYYvm; Thu,  8 Jul 2021 15:48:28 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11])
 by smtp2.osuosl.org (Postfix) with ESMTPS id 1F00E401EA;
 Thu,  8 Jul 2021 15:48:27 +0000 (UTC)
Received: from mail-il1-f178.google.com (mail-il1-f178.google.com
 [209.85.166.178]) (authenticated bits=0)
 (User authenticated as jlrubin@ATHENA.MIT.EDU)
 by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 168FmPx7015990
 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT);
 Thu, 8 Jul 2021 11:48:26 -0400
Received: by mail-il1-f178.google.com with SMTP id z1so7121702ils.0;
 Thu, 08 Jul 2021 08:48:26 -0700 (PDT)
X-Gm-Message-State: AOAM531CV8DuWfcpCX2p6NRXRmK5EsCIq/1ZsOSpWR8rBs/EbRGr74hO
 ttn0KRS/rXhrQBPrUWUcm2PTP9Fc1sousWq9/vQ=
X-Google-Smtp-Source: ABdhPJwcaLJsczeDAMOn5JAbcGRn8+23+rilpyhhYVB5jUNYpiiHRXhuPWGAA7tCX3QZOuJQkORhJzWLTSlgLoJr5xU=
X-Received: by 2002:a05:6e02:1a0f:: with SMTP id
 s15mr22679386ild.58.1625759305726; 
 Thu, 08 Jul 2021 08:48:25 -0700 (PDT)
MIME-Version: 1.0
References: <CAD5xwhgO5p2Ldy1P1rUuqDHcJ0opSe7Tg_mX_rb+ZpLOxa47cA@mail.gmail.com>
 <20210708084416.GB1339@erisian.com.au>
In-Reply-To: <20210708084416.GB1339@erisian.com.au>
From: Jeremy <jlrubin@mit.edu>
Date: Thu, 8 Jul 2021 08:48:14 -0700
X-Gmail-Original-Message-ID: <CAD5xwhjVod-Lu-gjU89znmVZnmL4UrL7xVuy=gZuuG6JG9X5yg@mail.gmail.com>
Message-ID: <CAD5xwhjVod-Lu-gjU89znmVZnmL4UrL7xVuy=gZuuG6JG9X5yg@mail.gmail.com>
To: Anthony Towns <aj@erisian.com.au>
Content-Type: multipart/alternative; boundary="000000000000e8810305c69e95b0"
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
 lightning-dev <lightning-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Eltoo / Anyprevout & Baked in Sequences
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
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: Thu, 08 Jul 2021 15:48:30 -0000

--000000000000e8810305c69e95b0
Content-Type: text/plain; charset="UTF-8"

>
> This would disallow using a relative locktime and an absolute locktime
> for the same input. I don't think I've seen a use case for that so far,
> but ruling it out seems suboptimal.


I think you meant disallowing a relative locktime and a sequence locktime?
I agree it is suboptimal.


What do you make of sequence tagged keys?

--000000000000e8810305c69e95b0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:r=
gb(204,204,204);padding-left:1ex">This would disallow using a relative lock=
time and an absolute locktime<br>for the same input. I don&#39;t think I&#3=
9;ve seen a use case for that so far,<br>but ruling it out seems suboptimal=
.</blockquote><div><br></div><div><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">I thi=
nk you meant disallowing a relative locktime and a sequence locktime? I agr=
ee it is suboptimal.</div><br></div><div><br></div><div><div class=3D"gmail=
_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;c=
olor:rgb(0,0,0)">What do you make of sequence tagged keys?</div><br></div><=
div><br></div></div>

--000000000000e8810305c69e95b0--