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
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
|
Delivery-date: Tue, 17 Dec 2024 16:27:25 -0800
Received: from mail-yw1-f186.google.com ([209.85.128.186])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBC57ZSP77YIRBZFNRC5QMGQEFIWRO6A@googlegroups.com>)
id 1tNhuP-0003nd-AN
for bitcoindev@gnusha.org; Tue, 17 Dec 2024 16:27:25 -0800
Received: by mail-yw1-f186.google.com with SMTP id 00721157ae682-6effbb8ca1fsf71325037b3.1
for <bitcoindev@gnusha.org>; Tue, 17 Dec 2024 16:27:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1734481639; x=1735086439; darn=gnusha.org;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:reply-to:x-original-sender
:mime-version:subject:message-id:to:from:date:from:to:cc:subject
:date:message-id:reply-to;
bh=KxmzNgbp/43s+FNhuAgkOz83uWNvIay1LMQ6/VmkGR0=;
b=KIhYAx35MRv0zz4Lnx5c1RA3/e0MxGmS1TgFiBY8awiyqCH9qdVjZXF1VkY+GgwQGQ
BnaWh3kUXvHnTIg26Z2vOocTfc6Oz5ktRcAg2Y252Q1+qlHDzLT6bi1eH9u/u+ok1AYs
taRMSTel5UeiJH6bxGYBz80jfqeSyzfcCvd7AAppp0KbPL4Qx44QCFMrMkgXtswxWvXD
SL8zOHhndP/VvzT00qHQRYAmPbvBBOintacoLeTtgI/eM2LtyT7o7VoMceDMnWMnR+YE
b/yXSZQ4HAz5de3oT2QHwxtPltDOmbwngiInr+RVRSE4dVgcC8Aij9t4FtyFL6g8eQCb
yFSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1734481639; x=1735086439;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:reply-to:x-original-sender
:mime-version:subject:message-id:to:from:date:x-beenthere
:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
bh=KxmzNgbp/43s+FNhuAgkOz83uWNvIay1LMQ6/VmkGR0=;
b=Z3mPUesUm+k75w22FOOkDEkTFM8XtFoEfuyDGx2eFi7j7GSRSMWCCMPhESAXc36wUR
IKLa1VoenD2Kd+z3Ciryn7yjbK3mIC5tAta2+E979dJhYSn48ok4kWnM7aQ3ihOX0pgl
ZIG9IttQp7fQpA+vRRNuCcN1UQkOLv00CwW9JElTuEclKaFZLdrZJvwJoMrDjBCLu4iU
oka9xuNNz4XjoWMf5YTN/lINxTs7GpfLv11DLXzfGDFLMN+RBieOVEUsZcdQ8fsZxur7
Rx9QJ8dA07XKe2cuLcZM89bNsr6q7QK5+tfNex3klnvuiZjcDUTfl/4QP7fe7pQw96Pt
gNXA==
X-Forwarded-Encrypted: i=1; AJvYcCWPV2rJh6vicS4aN62WCholixkv0cbABn+mm4JtEYPqn2dYXQM5MCsbOpo6Tpsuf6/B8QfiHhF6SaEf@gnusha.org
X-Gm-Message-State: AOJu0YxtioCFHrLNkZXlvaWqfZZSwYzsHcj8BthNVPU3FZieHEh0NKvt
PONRmrgkiS5OYuJctAbV9YHmve0fTC6KIdTWz8OopZ+5vCribKXd
X-Google-Smtp-Source: AGHT+IFfIBFQ83WtZg31gWxsrkWiDfm2bMTLCAChl8nnOAN5Wf3ZopDdIX4Q0TyhCg1Xdj3r0lrnhw==
X-Received: by 2002:a05:6902:2747:b0:e3a:2011:19a5 with SMTP id 3f1490d57ef6-e536218d740mr761858276.3.1734481638990;
Tue, 17 Dec 2024 16:27:18 -0800 (PST)
X-BeenThere: bitcoindev@googlegroups.com
Received: by 2002:a25:d302:0:b0:e48:8566:cdf0 with SMTP id 3f1490d57ef6-e488566d005ls2047187276.1.-pod-prod-02-us;
Tue, 17 Dec 2024 16:27:16 -0800 (PST)
X-Received: by 2002:a05:690c:6505:b0:6e7:e340:cd36 with SMTP id 00721157ae682-6f3d26b693dmr7005567b3.40.1734481636135;
Tue, 17 Dec 2024 16:27:16 -0800 (PST)
Received: by 2002:a0d:c247:0:b0:6ef:7d10:5a2f with SMTP id 00721157ae682-6f3096061d1ms7b3;
Tue, 17 Dec 2024 16:25:44 -0800 (PST)
X-Received: by 2002:a05:690c:3612:b0:6ef:6cfa:e1c9 with SMTP id 00721157ae682-6f3ccc22b58mr6181207b3.5.1734481544056;
Tue, 17 Dec 2024 16:25:44 -0800 (PST)
Date: Tue, 17 Dec 2024 16:25:43 -0800 (PST)
From: "'stutxo' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <5565b149-48b7-4823-9363-89cfd70ecf09n@googlegroups.com>
Subject: [bitcoindev] TRUC and P2A for CTV fee management
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_23764_2018848505.1734481543797"
X-Original-Sender: stuart.morley@zebedee.io
X-Original-From: stutxo <stuart.morley@zebedee.io>
Reply-To: stutxo <stuart.morley@zebedee.io>
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com
List-ID: <bitcoindev.googlegroups.com>
X-Google-Group-Id: 786775582512
List-Post: <https://groups.google.com/group/bitcoindev/post>, <mailto:bitcoindev@googlegroups.com>
List-Help: <https://groups.google.com/support/>, <mailto:bitcoindev+help@googlegroups.com>
List-Archive: <https://groups.google.com/group/bitcoindev
List-Subscribe: <https://groups.google.com/group/bitcoindev/subscribe>, <mailto:bitcoindev+subscribe@googlegroups.com>
List-Unsubscribe: <mailto:googlegroups-manage+786775582512+unsubscribe@googlegroups.com>,
<https://groups.google.com/group/bitcoindev/subscribe>
X-Spam-Score: -1.0 (-)
------=_Part_23764_2018848505.1734481543797
Content-Type: multipart/alternative;
boundary="----=_Part_23765_1172593453.1734481543797"
------=_Part_23765_1172593453.1734481543797
Content-Type: text/plain; charset="UTF-8"
Hi everyone,
I am trying to learn more about op_ctv (or its true name, op_securethebag).
One thing I keep hearing is that estimating fees are potentially an issue
when spending CTV transactions.
jamesob mentioned fees in his simple_ctv_valut
<https://github.com/jamesob/simple-ctv-vault>
*Because coins may remain vaulted for long periods of time, the unvault
process is sensitive to changes in the fee market. Because use of OP_CTV
requires precommiting to a tree of all possible specific outputs and the
number of inputs, we cannot use RBF to dynamically adjust feerate of
unvaulting transactions.*
and rustyrussell on nostr also mentioned fees being a problem
<https://primal.net/e/note1ulw6tr8hrqz092wy02fcyshn3fgt309kc5w95mhl7j0shj7c9zxsu8a2mw>
*Optimised sponsors for solving the "but how do I add fees" problem in a
way that doesn't drive miner centralisation.*
With v3 transactions available in bitcoin 28.0
<https://bitcoinops.org/en/bitcoin-core-28-wallet-integration-guide/>there
are a bunch of new techniques that have been enabled that we can use to
hopefully solve these issues
As long as you have an output for 240 sats paying to a P2A address, such as
tb1pfees9rn5nz on signet, you or anyone else will be able to bump the fees
using CPFP on the anchor output.
I have some examples of these transactions here on signet
CTV spend transaction with zero fees:
https://mempool.space/signet/tx/32f4f4e6165e7f8df9b9a762e11a6ca7f16087713e0e3e42352021e6bf3800e3
P2A CPFP transaction:
https://mempool.space/signet/tx/9a3582f03b0ac39cff8ed024cf8f38e4fc4a1ee2ff216badf041bf4572c0d03b
Code used is here:
https://github.com/stutxo/simple_ctv
Is there anything I am missing here? What are the downsides of this method?
Is this how most ctv scripts spends would work?
Thanks!
stu
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/5565b149-48b7-4823-9363-89cfd70ecf09n%40googlegroups.com.
------=_Part_23765_1172593453.1734481543797
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hi everyone,<div><br />I am trying to learn more about op_ctv (or its true =
name, op_securethebag). One thing I keep hearing is that estimating fees ar=
e potentially an issue when spending CTV transactions.=C2=A0<br /><i><br />=
</i>jamesob=C2=A0mentioned fees in his <a href=3D"https://github.com/jameso=
b/simple-ctv-vault">simple_ctv_valut</a><i><br />Because coins may remain v=
aulted for long periods of time, the unvault process is sensitive to change=
s in the fee market. Because use of OP_CTV requires precommiting to a tree =
of all possible specific outputs and the number of inputs, we cannot use RB=
F to dynamically adjust feerate of unvaulting transactions.<br /></i><br />=
and rustyrussell on nostr also mentioned fees being a <a href=3D"https://pr=
imal.net/e/note1ulw6tr8hrqz092wy02fcyshn3fgt309kc5w95mhl7j0shj7c9zxsu8a2mw"=
>problem</a>=C2=A0<br /><i>Optimised sponsors for solving the "but how do I=
add fees" problem in a way that doesn't drive miner centralisation.</i><br=
/><br />With <a href=3D"https://bitcoinops.org/en/bitcoin-core-28-wallet-i=
ntegration-guide/">v3 transactions available in bitcoin 28.0 </a>there are =
a bunch of new techniques that have been enabled that we can use to hopeful=
ly solve these issues</div><div><br />As long as you have an output for 240=
sats paying to a P2A address, such as tb1pfees9rn5nz on signet, you or any=
one else will be able to bump the fees using CPFP on the anchor output.=C2=
=A0</div><div><br />I have some examples of these transactions here on sign=
et</div><div><div><br />CTV spend transaction with zero fees:<br />https://=
mempool.space/signet/tx/32f4f4e6165e7f8df9b9a762e11a6ca7f16087713e0e3e42352=
021e6bf3800e3</div><div><br />P2A CPFP transaction:<br />https://mempool.sp=
ace/signet/tx/9a3582f03b0ac39cff8ed024cf8f38e4fc4a1ee2ff216badf041bf4572c0d=
03b</div><div><br /></div><div>Code used is here:<br />https://github.com/s=
tutxo/simple_ctv</div><br />Is there anything I am missing here? What are t=
he downsides of this method? Is this how most ctv scripts spends would work=
?</div><div><br />Thanks!<br />stu</div>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
bitcoindev/5565b149-48b7-4823-9363-89cfd70ecf09n%40googlegroups.com?utm_med=
ium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/bitcoind=
ev/5565b149-48b7-4823-9363-89cfd70ecf09n%40googlegroups.com</a>.<br />
------=_Part_23765_1172593453.1734481543797--
------=_Part_23764_2018848505.1734481543797--
|
