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
|
Return-Path: <symphonicbtc@proton.me>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137])
by lists.linuxfoundation.org (Postfix) with ESMTP id 7BC40C0032
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 10 Oct 2023 01:12:58 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp4.osuosl.org (Postfix) with ESMTP id BB56441686
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 10 Oct 2023 01:12:56 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org BB56441686
Authentication-Results: smtp4.osuosl.org; dkim=pass (2048-bit key,
unprotected) header.d=proton.me header.i=@proton.me header.a=rsa-sha256
header.s=br55wnovxrdwxddrz7cr3iaw5a.protonmail header.b=ijt8Dsab
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level:
X-Spam-Status: No, score=-2.102 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, SPF_HELO_PASS=-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 eqTPoxcs-k1Q
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 10 Oct 2023 01:12:55 +0000 (UTC)
Received: from mail-41103.protonmail.ch (mail-41103.protonmail.ch
[185.70.41.103])
by smtp4.osuosl.org (Postfix) with ESMTPS id CF044409A2
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 10 Oct 2023 01:12:54 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org CF044409A2
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me;
s=br55wnovxrdwxddrz7cr3iaw5a.protonmail; t=1696900361; x=1697159561;
bh=npAo2QB3oAjUtcYcTgX1olGH7/dIc9fSWCS3BClMmTA=;
h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References:
Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID:
Message-ID:BIMI-Selector;
b=ijt8DsabWUhG9H+oJlSU5Oh4rShTAfXLigej6eocdDwdhBN4RghLaj6+EQecJvY+5
Q66X8LKEmpSuSyNvXBo2lvLbX7P7gB+pmuDjPMZ+TlNePq+HhkGfrwSFeSvse5FeTO
Z70oy91kRqxb+mCu9OzYkQN0wexXJQKYXRTDfGURWfBrcrCVoWvqcUFOH7kdN05nCf
ZE0JQhxvByF+PTODhJC2Mnm3Dy4y1LXUqDqFXANmHm0/1FOagPezO7MRt9NXBlp0K+
Wgr/vaY7L10U1Q0IK5nsMGB5ET27F1yKddoXy/VCbMTlmsgq6XDUbUnBRHjuOkxGFt
fi/qmfISk0QUA==
Date: Tue, 10 Oct 2023 01:12:28 +0000
To: Robin Linus <robin@zerosync.org>
From: symphonicbtc <symphonicbtc@proton.me>
Message-ID: <HC0rwsiXAJBptIP0S-a5XNFcNAg5sk0ihUDHkjxfxbDiKZh9idX7UX4I73sZk2iHsXa5rVpI4_4m59B0hiDrYjXKh9wFwJvMZcH6GNZVMek=@proton.me>
In-Reply-To: <CCA561B6-A2DE-46FD-A2F8-98E0C34A3EEE@zerosync.org>
References: <CCA561B6-A2DE-46FD-A2F8-98E0C34A3EEE@zerosync.org>
Feedback-ID: 77757318:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 10 Oct 2023 01:53:02 +0000
Cc: bitcoin-dev@lists.linuxfoundation.org
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:12:58 -0000
Hello Robin,
I'm very interested in this development, as I've been longing for arbitrary=
smart contracts on bitcoin for a while. I've got a couple questions I'd li=
ke to ask, on behalf of myself and some others I've been discussing this wi=
th.
1. Do you have plans to implement a high-level language that can compile do=
wn to this or maybe adapt some existing VM to make these scripts? I'm sure =
many would love to get their hands on something a bit more workable to test=
this out.
2. What are the expected computational costs of establishing the tapleaves =
for these scripts? Is it feasible to do complex things like ECDSA signature=
checking, etc? I worry that the hardware required to use this tech will be=
a barrier in it's widespread use.
3. Would it be possible to implement existing zero-knowledge proof construc=
ts on BitVM, and would that make verification simpler? I.e. instead of veri=
fying your program directly with BitVM, have your program be written in som=
e ZKP VM, and just have the proof verification execute on BitVM
4. What are the expected costs of resolving a fraud for a program? I assume=
this is quite nuanced and has to do with the exact circumstances of the pr=
ogram, but would it be possible for you to provide some examples of how thi=
s might go down for some simple programs to aid comprehension?
Thanks,
Symphonic
Sent with Proton Mail secure email.
------- Original Message -------
On Monday, October 9th, 2023 at 1:46 PM, Robin Linus via bitcoin-dev <bitco=
in-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 verifie=
d, similarly to optimistic rollups. A prover makes a claim that a given fun=
ction evaluates for some particular inputs to some specific output. If that=
claim is false, then the verifier can perform a succinct fraud proof and p=
unish the prover. Using this mechanism, any computable function can be veri=
fied on Bitcoin. Committing to a large program in a Taproot address require=
s significant amounts of off-chain computation and communication, however t=
he resulting on-chain footprint is minimal. As long as both parties collabo=
rate, they can perform arbitrarily complex, stateful off-chain computation,=
without leaving any trace in the chain. On-chain execution is required onl=
y in case of a dispute.
>=20
> https://bitvm.org/bitvm.pdf
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
|
