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
|
Return-Path: <earonesty@gmail.com>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136])
by lists.linuxfoundation.org (Postfix) with ESMTP id 956C2C002D
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 7 Jul 2022 14:05:44 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp3.osuosl.org (Postfix) with ESMTP id 7A0806120E
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 7 Jul 2022 14:05:44 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 7A0806120E
Authentication-Results: smtp3.osuosl.org;
dkim=pass (2048-bit key) header.d=q32-com.20210112.gappssmtp.com
header.i=@q32-com.20210112.gappssmtp.com header.a=rsa-sha256
header.s=20210112 header.b=4n7gS2Ds
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 1.301
X-Spam-Level: *
X-Spam-Status: No, score=1.301 tagged_above=-999 required=5
tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001,
HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001,
RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
autolearn=no autolearn_force=no
Received: from smtp3.osuosl.org ([127.0.0.1])
by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id QIqvEFHsQx-9
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 7 Jul 2022 14:05:41 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 955A660F5F
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com
[IPv6:2a00:1450:4864:20::129])
by smtp3.osuosl.org (Postfix) with ESMTPS id 955A660F5F
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 7 Jul 2022 14:05:40 +0000 (UTC)
Received: by mail-lf1-x129.google.com with SMTP id i18so31288653lfu.8
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 07 Jul 2022 07:05:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=q32-com.20210112.gappssmtp.com; s=20210112;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to
:cc; bh=4tDwXej3XYNdmhOE8K0SBsNP0fWetVtkYhVFcFgYtUA=;
b=4n7gS2DsSfR633KxXB0BolzyhGJST1sRix6SK0TI85/KtanTaKm726ss5z1r2KLB2U
FGVT49PzzIC1aTpgOVKMmM4GihGu3P0OC57e/6jDDiOLKd86T/qJg5DMBZbH7Zrwk8dg
CNo8LHoOR/VoHq+7XxjGkTBMKejcZMy8JNGUEOUzyBmob/jerayIMrGmwU0ub+xA/7BZ
GupkofP0FeDeV88yDyPsUqf2V98Yz41dUOdZ1bo/Mx1mo6a+OrFbiD7kb+ke9JePb0Yt
WuTfQ/bEULARLTmfUCePuXiIt5auns6wb0JbD1+pfNMjRMraYxJdWec/5b6dT7dKluGI
nsTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to:cc;
bh=4tDwXej3XYNdmhOE8K0SBsNP0fWetVtkYhVFcFgYtUA=;
b=BwsBfQl6ASbaO2nvmVQYKB7TDx3fJD9NQFg7pxeyrx8ZVwbGnQS8a7ZOuRjTtN3twt
5iTwC8PGHqzglnvggkAkUTahB5WaEBrk7kGONiZQvq969r5Fdi4YkvDKoHZ1s27Ubb1W
d+H70QuOrAkxnJRQ8SgvjmTUPG9XPAsEcAsnIYgdwebRa1PCyNoseEqDSOwaP05SRaZI
hnAUH6gHx9Kb3VbzvbuC3bTLuV+YZALoTJ8Yhjxyk7fcAGmYn/KetyDjgJ9vWqMbHaOg
3Y5v7cw8c89kFmFYCOU2V5Z9LnLvPUbModSMIaNtk/H6JUUo19PZzQwr1EeYaaHxikJU
DRXA==
X-Gm-Message-State: AJIora+YpkHJRV7WGlw0AuNnJXsTfQGeMb7MmTqfeRU7xbuafbPOcA87
H5gEU9MWAYbbhwC9e0nzMkpurPfV/v6WzzBEX/4COro=
X-Google-Smtp-Source: AGRyM1vwWbn8lxfiHAVy0VIydIyIdqDWMsNl60wOeQdrjZ1PzMrQgQmvbdkP9B2ILnMJFEzXvj2bpchJG9IsB87qaFo=
X-Received: by 2002:a05:6512:4003:b0:47f:97e9:28b8 with SMTP id
br3-20020a056512400300b0047f97e928b8mr29734524lfb.141.1657202738315; Thu, 07
Jul 2022 07:05:38 -0700 (PDT)
MIME-Version: 1.0
References: <CAK_HAC97sfvtkfs=yTt8Z0pi5ZF91n7OcZbu7k4XhdnMJ_PYnA@mail.gmail.com>
<139633828-26b5fcbad80d1ca7046479237716ace3@pmq8v.m5r2.onet>
<CAGpPWDbKjSXKHaUcevzG1DtdP-WksO3Ak+1J2JWTeCG2=3GgLQ@mail.gmail.com>
In-Reply-To: <CAGpPWDbKjSXKHaUcevzG1DtdP-WksO3Ak+1J2JWTeCG2=3GgLQ@mail.gmail.com>
From: Erik Aronesty <erik@q32.com>
Date: Thu, 7 Jul 2022 10:05:25 -0400
Message-ID: <CAJowKgL++JGnKeh5b31ZtT36+ZWANPUp9EJDRzLqCuPXJDS=Hg@mail.gmail.com>
To: Billy Tetrud <billy.tetrud@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="00000000000089ca7105e3379487"
X-Mailman-Approved-At: Thu, 07 Jul 2022 14:43:20 +0000
Subject: Re: [bitcoin-dev] Bitcoin covenants are inevitable
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, 07 Jul 2022 14:05:44 -0000
--00000000000089ca7105e3379487
Content-Type: text/plain; charset="UTF-8"
.
>
> My thoughts on this are that we will need to periodically make some
> software change to adjust a *target amount of investment in security*,
> because the
>
I think perhaps you're underestimating the degree to which utility can be
added to the main chain to encourage fees.
For example, lightning channel open and close transactions are more
valuable, via aggregation, than simple money transfers.
The value of higher utility transactions goes up fairly quickly.
There is no end of the possibility of fee levels in response to increased
utility
Other networks have clearly proven the extremes of this, with rampant fees
appearing rapidly in response to higher utility levels
Because this has already been proven on other networks, we can plan to
gradually increase the utility of on-chain transactions in response to
reward reductions
This should be more than sufficient to offset and maintain sufficient
security
... Hence the title of this thread.
--00000000000089ca7105e3379487
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto"><div><br><div class=3D"gmail_quote"><div dir=3D"ltr" clas=
s=3D"gmail_attr">.</div><blockquote class=3D"gmail_quote" style=3D"margin:0=
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto"><d=
iv dir=3D"ltr"><div><br></div><div>My thoughts on this are that we will nee=
d to periodically make some software change to adjust a *target amount of i=
nvestment in security*, because the</div><div dir=3D"auto"></div></div></di=
v></blockquote></div></div><div dir=3D"auto"><br></div><div dir=3D"auto">I =
think perhaps you're=C2=A0 underestimating the degree to which utility =
can be added to the main chain to encourage fees.</div><div dir=3D"auto"><b=
r></div><div dir=3D"auto">For example, lightning channel open and close tra=
nsactions are more valuable, via aggregation, than simple money transfers.<=
/div><div dir=3D"auto"><br></div><div dir=3D"auto">The value of higher util=
ity transactions goes up fairly quickly.</div><div dir=3D"auto"><br></div><=
div dir=3D"auto">There is no end of the possibility of fee levels in respon=
se to increased utility</div><div dir=3D"auto"><br></div><div dir=3D"auto">=
Other networks have clearly proven the extremes of this, with rampant fees =
appearing rapidly in response to higher utility levels</div><div dir=3D"aut=
o"><br></div><div dir=3D"auto">Because this has already been proven on othe=
r networks, we can plan to gradually=C2=A0 increase the utility of on-chain=
transactions in response to reward reductions</div><div dir=3D"auto"><br><=
/div><div dir=3D"auto">This should be more than sufficient to offset and ma=
intain sufficient security=C2=A0</div><div dir=3D"auto"><br></div><div dir=
=3D"auto">... Hence the title of this thread.</div></div>
--00000000000089ca7105e3379487--
|
