summaryrefslogtreecommitdiff
path: root/2e/d25c8e001652e32762a3f84d1221dcbb20e82d
blob: 36df615464665e4c2ecf2a611cc269e8c3f78038 (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
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
Return-Path: <lloyd.fourn@gmail.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 94A4FC0032
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 10 Oct 2023 01:06:39 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp4.osuosl.org (Postfix) with ESMTP id 67ACA41753
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 10 Oct 2023 01:06:39 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 67ACA41753
Authentication-Results: smtp4.osuosl.org;
 dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com
 header.a=rsa-sha256 header.s=20230601 header.b=Y+vq9i9H
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from smtp4.osuosl.org ([127.0.0.1])
 by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id I2_-tOWE31Ms
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 10 Oct 2023 01:06:38 +0000 (UTC)
Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com
 [IPv6:2607:f8b0:4864:20::82d])
 by smtp4.osuosl.org (Postfix) with ESMTPS id E16BA41730
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 10 Oct 2023 01:06:37 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org E16BA41730
Received: by mail-qt1-x82d.google.com with SMTP id
 d75a77b69052e-4180d962b68so37018421cf.1
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 09 Oct 2023 18:06:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s=20230601; t=1696899996; x=1697504796;
 darn=lists.linuxfoundation.org; 
 h=to:subject:message-id:date:from:in-reply-to:references:mime-version
 :from:to:cc:subject:date:message-id:reply-to;
 bh=M3lyFYIzosadoUduNw38p8t9cg74rQqOzuF811cS4AY=;
 b=Y+vq9i9HTG+qB8qz03ZhCSHFI0mocxHc7FAoTBpSdUTaTbV7Pxh26nX/b/nG1HiO0I
 at/MjNgbqjW37nr+kS0olMVmh5FvYtLYxaXMuBBOKI456cu3D1vyy5+tjA5ytfuzd/Zf
 chBq/92wRJ+DG4KrEHcyH7fkDb+fdpFE43Q5TVC+N6ZKhqifvKw+HVRnMKE5/JBSQed5
 769cW3gyeK2VUrJgx0PUWZIc7LgH3NLw3r9pERPVZs4mZVOm6nFLn3a5DmMAAOdnpxH9
 5VY9INcsajAQiQw+2/g+qHLaYzCZvXwssNgkfYf+Z5OqFJ/5LwjGrEN7M0ulyOdT9dnq
 omkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20230601; t=1696899996; x=1697504796;
 h=to:subject:message-id:date:from:in-reply-to:references:mime-version
 :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
 bh=M3lyFYIzosadoUduNw38p8t9cg74rQqOzuF811cS4AY=;
 b=wV+jADk17hlll+ZFUMDG1Szp6xjPxRFrwiiq+XFlBWQ3XAnpcDMMAjypBoBB3+tsgu
 hb2DF/Xe+Cij2A64L4QrZ3cjF4G2yb44/0devXkGATfjV3A17qIPPFt30yKCsFGHfZ7p
 yG9vhkZdbnYkgN7V7M3tFqidJa73rQcmf/6274qhqwJJ+Duxd4uZI27E1ybnp5+ZlAS6
 cwhsmhkCLOs7VwPu76xqMDwQIkBRqngWV6mmJju500DDNCzhCUBhu+ATyPOUgMZeLy3q
 xANVu41Ujla+E6W/wJoSqXCeSSYTMipvWDaL89kJYY5ejyS3RrQBS1u8kkjne95gksNb
 H5wg==
X-Gm-Message-State: AOJu0YwdOYxoipA6TV2hZpO6arzUCiLE7xincDewdN2iYmzFuFO3E8V7
 NGO+CEoWLh9lz+ecrblPnb0sjJ8adxQ555ccJEEmwWdWz/M=
X-Google-Smtp-Source: AGHT+IF41A0bqII9NYv43ErWluBV7NDIMEYYnddOwSHtc4xIYbmCCu3nc9aEJNgjtwwijHxpfeZCL4Ac9KPw+8meQzw=
X-Received: by 2002:a05:622a:a:b0:417:a2f9:bba6 with SMTP id
 x10-20020a05622a000a00b00417a2f9bba6mr20412205qtw.60.1696899996469; Mon, 09
 Oct 2023 18:06:36 -0700 (PDT)
MIME-Version: 1.0
References: <CCA561B6-A2DE-46FD-A2F8-98E0C34A3EEE@zerosync.org>
In-Reply-To: <CCA561B6-A2DE-46FD-A2F8-98E0C34A3EEE@zerosync.org>
From: Lloyd Fournier <lloyd.fourn@gmail.com>
Date: Tue, 10 Oct 2023 12:06:10 +1100
Message-ID: <CAH5Bsr2XaUfYy+gPiSuQaMcxK43CNsR2apKYMTkF1sX3U9Jzbw@mail.gmail.com>
To: Robin Linus <robin@zerosync.org>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000824c0806075251b4"
X-Mailman-Approved-At: Tue, 10 Oct 2023 01:52:31 +0000
Subject: Re: [bitcoin-dev] BitVM: Compute Anything on Bitcoin
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: Tue, 10 Oct 2023 01:06:39 -0000

--000000000000824c0806075251b4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Robin,

Fascinating result.
Is it possible to give us an example of a protocol that uses BitVM that
couldn't otherwise be built? I'm guessing it's possible to exchange Bitcoin
to someone who can prove they know some input to a binary circuit that
gives some output.

Thanks!

LL

On Tue, 10 Oct 2023 at 01:05, Robin Linus via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Abstract. BitVM is a computing paradigm to express Turing-complete Bitcoi=
n
> contracts. This requires no changes to the network=E2=80=99s consensus ru=
les.
> Rather than executing computations on Bitcoin, they are merely verified,
> similarly to optimistic rollups. A prover makes a claim that a given
> function evaluates for some particular inputs to some specific output. If
> that claim is false, then the verifier can perform a succinct fraud proof
> and punish the prover. Using this mechanism, any computable function can =
be
> verified on Bitcoin. Committing to a large program in a Taproot address
> requires significant amounts of off-chain computation and communication,
> however the resulting on-chain footprint is minimal. As long as both
> parties collaborate, they can perform arbitrarily complex, stateful
> off-chain computation, without leaving any trace in the chain. On-chain
> execution is required only in case of a dispute.
>
> https://bitvm.org/bitvm.pdf
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"ltr"><div>Hi Robin,</div><div><br></div><div>Fascinating result=
.<br></div><div>Is it possible to give us an example of a protocol that use=
s BitVM that couldn&#39;t otherwise be built? I&#39;m guessing it&#39;s pos=
sible to exchange Bitcoin to someone who can prove they know some input to =
a binary circuit that gives some output.<br></div><div><br></div><div>Thank=
s!</div><div><br></div><div>LL<br></div></div><br><div class=3D"gmail_quote=
"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, 10 Oct 2023 at 01:05, Robin=
 Linus via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundat=
ion.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex">Abstract. BitVM is a computin=
g paradigm to express Turing-complete Bitcoin contracts. This requires no c=
hanges to the network=E2=80=99s consensus rules. Rather than executing comp=
utations on Bitcoin, they are merely verified, similarly to optimistic roll=
ups. A prover makes a claim that a given function evaluates for some partic=
ular inputs to some specific output. If that claim is false, then the verif=
ier can perform a succinct fraud proof and punish the prover. Using this me=
chanism, any computable function can be verified on Bitcoin. Committing to =
a large program in a Taproot address requires significant amounts of off-ch=
ain computation and communication, however the resulting on-chain footprint=
 is minimal. As long as both parties collaborate, they can perform arbitrar=
ily complex, stateful off-chain computation, without leaving any trace in t=
he chain. On-chain execution is required only in case of a dispute.<br>
<br>
<a href=3D"https://bitvm.org/bitvm.pdf" rel=3D"noreferrer" target=3D"_blank=
">https://bitvm.org/bitvm.pdf</a><br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>

--000000000000824c0806075251b4--