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
|
Return-Path: <robin@zerosync.org>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 899E1C0032
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 9 Oct 2023 14:04:55 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id 5EB2441521
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 9 Oct 2023 14:04:55 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 5EB2441521
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5
tests=[BAYES_40=-0.001, SPF_HELO_NONE=0.001, 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 5y7qu8_Q1ihT
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 9 Oct 2023 14:04:54 +0000 (UTC)
X-Greylist: delayed 1106 seconds by postgrey-1.37 at util1.osuosl.org;
Mon, 09 Oct 2023 14:04:54 UTC
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 09B4D41478
Received: from www382.your-server.de (www382.your-server.de [78.46.146.228])
by smtp2.osuosl.org (Postfix) with ESMTPS id 09B4D41478
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 9 Oct 2023 14:04:53 +0000 (UTC)
Received: from sslproxy06.your-server.de ([78.46.172.3])
by www382.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384
(Exim 4.94.2) (envelope-from <robin@zerosync.org>)
id 1qpqaX-000HPd-Fa
for bitcoin-dev@lists.linuxfoundation.org; Mon, 09 Oct 2023 15:46:25 +0200
Received: from [2001:9e8:8a56:a200:4dce:fcb5:a987:a853] (helo=smtpclient.apple)
by sslproxy06.your-server.de with esmtpsa
(TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92)
(envelope-from <robin@zerosync.org>) id 1qpqaX-000Ccw-9Q
for bitcoin-dev@lists.linuxfoundation.org; Mon, 09 Oct 2023 15:46:25 +0200
From: Robin Linus <robin@zerosync.org>
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Message-Id: <CCA561B6-A2DE-46FD-A2F8-98E0C34A3EEE@zerosync.org>
Date: Mon, 9 Oct 2023 15:46:24 +0200
To: bitcoin-dev@lists.linuxfoundation.org
X-Mailer: Apple Mail (2.3654.120.0.1.13)
X-Authenticated-Sender: robin@zerosync.org
X-Virus-Scanned: Clear (ClamAV 0.103.10/27056/Mon Oct 9 09:40:11 2023)
X-Mailman-Approved-At: Mon, 09 Oct 2023 14:05:30 +0000
Subject: [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: Mon, 09 Oct 2023 14:04:55 -0000
Abstract. BitVM is a computing paradigm to express Turing-complete =
Bitcoin contracts. This requires no changes to the network=E2=80=99s =
consensus rules. 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=
|
