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
|
Delivery-date: Tue, 04 Mar 2025 19:26:28 -0800
Received: from mail-yb1-f191.google.com ([209.85.219.191])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBCXZ3LX45UKRBWUIT67AMGQECULWHXI@googlegroups.com>)
id 1tpfOt-0000CL-MY
for bitcoindev@gnusha.org; Tue, 04 Mar 2025 19:26:28 -0800
Received: by mail-yb1-f191.google.com with SMTP id 3f1490d57ef6-e54d9b54500sf9200540276.3
for <bitcoindev@gnusha.org>; Tue, 04 Mar 2025 19:26:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1741145181; x=1741749981; darn=gnusha.org;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-sender:mime-version
:subject:message-id:to:from:date:sender:from:to:cc:subject:date
:message-id:reply-to;
bh=MbdG3wi7KLXp39yv8IzC6HGK4YIpFfE7Y1voDqocF5c=;
b=q5mA66tzWd1J+oiVJlUflwfR7Egj48OtI06Bxm4V6xLWO6U7H2czRLN1QtzZizXbDX
nqSVW8xjCWze8Lv9ltJF+xG3Id06H0nygG8gXkpNUu+URBt141e6l0BjOCRMPaenyJb3
Q6LRYYVKRCW8t9Zuu6EnTEs9RKmscFrAHzlodoZDeI5BNbRffxJukyYXsILLI6TGT/z3
89JDX5N0AGQ92kKPVAazJGM4+VEHTg8PEsaCcZ+pKwXK0cBjKSGLy+VAG6PuifhPOwVg
kDrxBZ/EmEi6zaLjIkgs1eQ7y4g++HzGHOR2fb+DsGe0cMXOE/Pzlw+WOLt1tWd+Al3Q
zCyg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20230601; t=1741145181; x=1741749981; darn=gnusha.org;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-sender:mime-version
:subject:message-id:to:from:date:from:to:cc:subject:date:message-id
:reply-to;
bh=MbdG3wi7KLXp39yv8IzC6HGK4YIpFfE7Y1voDqocF5c=;
b=koj6YOD4AulGqb08fMZj/huxuX8nUydpSG9yJV0VC3cQHQOmCMb+r+n3dVdzuOhTUc
73tCJGKDM45KbVTQ4gH1u4jTwgCZVHWidgzT3iHfN2u5pVRrg5CcAE+DgZlrk/e8YmJw
nX8Gah7crXqaOe4klwt9EUqiUdM5ykg44bteXYpeMy8y7p2fNwraMT1TeJ0J2o3I1GJy
XZSBQeaDSy9lch44eU0AZfgQKxyDe5yxoZjgPNgcM84RvKugKYMyYfkyF63KxgERVRbP
N8EGB5Rj+HFrB3hWRFS7gZv0iJ+WmukUxofD4mBY/JKxlCuTSJMwhNcRjXnH2L/405Wm
NgBA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1741145181; x=1741749981;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-sender:mime-version
:subject:message-id:to:from:date:x-beenthere:x-gm-message-state
:sender:from:to:cc:subject:date:message-id:reply-to;
bh=MbdG3wi7KLXp39yv8IzC6HGK4YIpFfE7Y1voDqocF5c=;
b=o1OtBkBJb9HJNpBU+roR7bavRzdXYg6hZydn+mzqYBCdwCI352TRldc5kuRPBOcbPV
U2LmLIMUyHnKmaGIFIMtTkmLqKGU4InhsJMTfTNQmax3sKY7cwFoyg/nzEhPNsK7Y7Fk
+DeiUK1AAeLNJTbEhB4jvRjWhRiq9g4JPsVJpsc/eydotZty6+r1UvmZYba8M2qyGkg8
1HUQEmT5zKMTXYjsmcrRaeoMsXp/69YcYu/kXKCLQP6rxghl+U3SEcSJGyrm7JvVWh8y
pVc7P52yqWSH6mTMww+ACnbZd7Ypwew+3BD+7ih/9hHLMPO285KDCq0DDpCcwL3tBrnA
aOUw==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=1; AJvYcCXXFpoPmwc/WSlKAA0pwIdCKvwHfuM+NBtk2JAEI3sUEue/sSy53n6o0UHoW/3X84iXHs0lPa6Ua1tG@gnusha.org
X-Gm-Message-State: AOJu0YzXaEbN6Sp19GnKswbu6KTs+FSWy9BjHSMbr0d3luOgY6HXV3rJ
dDico980DcnlInZegMxLa0lQNsC/uz+vRCnUs1GO86Xpp850s9Fa
X-Google-Smtp-Source: AGHT+IEsTRuV93mrN6NgmkKxoLqigQRBo65/AIEqrVt0Hkh1vD9KDMuF/L09/6KWvucddLcjsmrewQ==
X-Received: by 2002:a05:6902:1244:b0:e5d:d128:e6cc with SMTP id 3f1490d57ef6-e611e35f2d5mr1884051276.37.1741145181510;
Tue, 04 Mar 2025 19:26:21 -0800 (PST)
X-BeenThere: bitcoindev@googlegroups.com; h=Adn5yVGcl76jv/FVd/CtqQq6G2lIeMg4JyUxca/NnHZS5EO58Q==
Received: by 2002:a25:dccb:0:b0:e5b:423e:3be6 with SMTP id 3f1490d57ef6-e60cebfc5d2ls2477094276.1.-pod-prod-08-us;
Tue, 04 Mar 2025 19:26:18 -0800 (PST)
X-Received: by 2002:a05:690c:64c1:b0:6f9:45de:408f with SMTP id 00721157ae682-6fda30f8de1mr27722457b3.35.1741145178134;
Tue, 04 Mar 2025 19:26:18 -0800 (PST)
Received: by 2002:a05:690c:3388:b0:6ef:590d:3213 with SMTP id 00721157ae682-6fda287d365ms7b3;
Tue, 4 Mar 2025 19:23:00 -0800 (PST)
X-Received: by 2002:a05:690c:708d:b0:6f2:9533:8fba with SMTP id 00721157ae682-6fda2fe2f79mr23327067b3.1.1741144979477;
Tue, 04 Mar 2025 19:22:59 -0800 (PST)
Date: Tue, 4 Mar 2025 19:22:59 -0800 (PST)
From: Sergio Demian Lerner <sergio.d.lerner@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <3e49d257-7d44-4c19-a157-eb479ca0a4b9n@googlegroups.com>
Subject: [bitcoindev] ESSPI: ECDSA/Schnorr Signed Program Input for BitVMX
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_13936_515486276.1741144979230"
X-Original-Sender: sergio.d.lerner@gmail.com
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: -0.5 (/)
------=_Part_13936_515486276.1741144979230
Content-Type: multipart/alternative;
boundary="----=_Part_13937_1551497950.1741144979230"
------=_Part_13937_1551497950.1741144979230
Content-Type: text/plain; charset="UTF-8"
Hello!
I'd like to present to bitcoin-dev an improvement to the BitVMX protocol
that enables the optimistic verification of long proofs (i.e. STARKs) on
Bitcoin without soft forks.
Here is the abstract and paper links:
https://bitvmx.org/files/esspi-ecdsa-input-bitvmx.pdf
*Abstract*
The BitVM and BitVMX protocols have long relied on inefficient one-time
signature (OTS) schemes like Lamport and Winternitz for signing program
inputs. These schemes exhibit significant storage overheads, hindering
their practical application. This paper introduces ESSPI, an optimized
method leveraging ECDSA/Schnorr signatures to sign the BitVMX program
input. With Schnorr signatures we achieve an optimal 1:1 data expansion,
compared to the current known best ratio of 1:200 based on Winternitz
signatures. To accomplish this we introduce 4 innovations to BitVMX: (1) a
modification of the BitVMX CPU, adding a challengeable hashing core to it,
(2) a new partition-based search to detect fraud during hashing, (3) a new
enhanced transaction DAG with added data-carrying transactions with a
fraud-verifying smart-contract and (4) a novel timelock-based method for
proving data availability to Bitcoin smart contracts. The enhanced BitVMX
protocol enables the verification of uncompressed inputs such as SPV
proofs, NiPoPoWs, or longer computation integrity proofs, such as STARKs.
Best, Sergio.
--
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/3e49d257-7d44-4c19-a157-eb479ca0a4b9n%40googlegroups.com.
------=_Part_13937_1551497950.1741144979230
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hello!<br />I'd like to present to bitcoin-dev an improvement to the BitVMX=
protocol that enables the optimistic verification of long proofs (i.e. STA=
RKs) on Bitcoin without soft forks.<br /><br />Here is the abstract and pap=
er links: <a href=3D"https://bitvmx.org/files/esspi-ecdsa-input-bitvmx.pdf=
">https://bitvmx.org/files/esspi-ecdsa-input-bitvmx.pdf</a><br /><br /><b>A=
bstract</b><br /><br />The BitVM and BitVMX protocols have long relied on i=
nefficient one-time signature (OTS) schemes like Lamport and Winternitz for=
signing program inputs. These schemes exhibit significant storage overhead=
s, hindering their practical application. This paper introduces ESSPI, an o=
ptimized method leveraging ECDSA/Schnorr signatures to sign the BitVMX prog=
ram input. With Schnorr signatures we achieve an optimal 1:1 data expansion=
, compared to the current known best ratio of 1:200 based on Winternitz sig=
natures. To accomplish this we introduce 4 innovations to BitVMX: (1) a mod=
ification of the BitVMX CPU, adding a challengeable hashing core to it, (2)=
a new partition-based search to detect fraud during hashing, (3) a new enh=
anced transaction DAG with added data-carrying transactions with a fraud-ve=
rifying smart-contract and (4) a novel timelock-based method for proving da=
ta availability to Bitcoin smart contracts. The enhanced BitVMX protocol en=
ables the verification of uncompressed inputs such as SPV proofs, NiPoPoWs,=
or longer computation integrity proofs, such as STARKs.<br /><br />Best, S=
ergio.
<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/3e49d257-7d44-4c19-a157-eb479ca0a4b9n%40googlegroups.com?utm_med=
ium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/bitcoind=
ev/3e49d257-7d44-4c19-a157-eb479ca0a4b9n%40googlegroups.com</a>.<br />
------=_Part_13937_1551497950.1741144979230--
------=_Part_13936_515486276.1741144979230--
|
