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
|
Return-Path: <orlovsky@lnp-bp.org>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136])
by lists.linuxfoundation.org (Postfix) with ESMTP id 3CC3AC0032
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 15 Sep 2023 09:31:20 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp3.osuosl.org (Postfix) with ESMTP id 047C160BDE
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 15 Sep 2023 09:31:20 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 047C160BDE
Authentication-Results: smtp3.osuosl.org; dkim=pass (2048-bit key,
unprotected) header.d=lnp-bp.org header.i=@lnp-bp.org header.a=rsa-sha256
header.s=protonmail3 header.b=ifed1Heq
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Level:
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5
tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H5=0.001,
RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
autolearn=ham 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 oQuL8M85a2eS
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 15 Sep 2023 09:31:17 +0000 (UTC)
Received: from mail-4317.proton.ch (mail-4317.proton.ch [185.70.43.17])
by smtp3.osuosl.org (Postfix) with ESMTPS id B30B160B7C
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 15 Sep 2023 09:31:16 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org B30B160B7C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lnp-bp.org;
s=protonmail3; t=1694770273; x=1695029473;
bh=6OBNBEXmIS8hkS0DdRK6DGxlA1/RhZbDITbyk6Vbr6s=;
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=ifed1Heq8+R1o0FdnJcQx+Fpw6HUEYtKxjx1z27YFt6I7pOldfsBwoTcY89KISsKP
u5boGTdXD2Q7mI2JJytwTq/LB1Baz2mjAxJ7/d1LMHTgl7gXKV0EZDJsirvVLGNAgU
nEW/dNm5OtxX/Q7J1m9Jv4uq8N5eiRq8wJknCGjXVHkq0c4A10TIeE5eSl4v7jyuFv
nUrogFjPQC87BPJrpXzuIXLak8O63sVC+aw9YxkKmJ2fTAUN/aJG93Tp0wc/vnGPOA
imS9U6XDDakiyPvi1DeVWfBzcwYBGflRODFqDA3p2TxntSc6ofPvt7qOLjNYFoJj7E
7SMcfbVExGrNA==
Date: Fri, 15 Sep 2023 09:31:10 +0000
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: Dr Maxim Orlovsky <orlovsky@lnp-bp.org>
Message-ID: <fZ1TE57Cb_fD-VmcjtDO8qp9qWEC98m9weorLFkxWjB32H2_C9w5HMNlzHW4TS6SgiKzNN9ScBaiQ6A7SJkJEWQ4CLjzTcwhSysEzqdSCkM=@lnp-bp.org>
In-Reply-To: <CAHUwRvtadqomqDpWBuOwjJR7ftsTpE_-C4mPVAg0j3HqR6vFUw@mail.gmail.com>
References: <XDPm1ve5FC6e68LI_ZK4f_oRGDArvptCDh1ofEXNNZV9TaTQ_XRALF2KIdIknQOw-TXKJHedJ-5xHi0sbipTrF7qIe4ynp2Qxp823BGcXcY=@lnp-bp.org>
<CAHUwRvtadqomqDpWBuOwjJR7ftsTpE_-C4mPVAg0j3HqR6vFUw@mail.gmail.com>
Feedback-ID: 18134079:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Fri, 15 Sep 2023 13:48:53 +0000
Subject: Re: [bitcoin-dev] Trustless 2-way-peg without softfork
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: Fri, 15 Sep 2023 09:31:20 -0000
Hi,
I got a lot of feedback on my proposal -- and it appears that I have to wor=
k on a simpler paper explaining how the proposed generic model ("Prometheus=
") can be applied to a specific case of two-way peg. I have planned this wo=
rk for the next several weeks and will post it to this mailing list once re=
ady.
Kind regards,
Maxim
------- Original Message -------
On Monday, September 11th, 2023 at 5:26 PM, G. Andrew Stone via bitcoin-dev=
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> Any chance of a quick tldr to pique our interest by explaining how exactl=
y this works "and the protocol will reach consensus on whether the state re=
ported by the oracle is correct" in presumably a permissionless, anonymous,=
decentralized fashion, and what caveats there are?
>=20
> Regards,
> Andrew
>=20
> On Sun, Sep 10, 2023 at 4:06=E2=80=AFPM Dr Maxim Orlovsky via bitcoin-dev=
<bitcoin-dev@lists.linuxfoundation.org> wrote:
>=20
> > Hi,
> >=20
> > Several years ago my team from Pandora Project working on censorship-re=
sistant distributed machine learning proposed Prometheus: a protocol for hi=
gh-load computing on top of Bitcoin. The protocol operates as a multi-party=
game setting where an oracle ("worker") is provided with an arbitrary comp=
utationally complex task (any Turing-complete computing, machine learning t=
raining or inference etc) and the network is able to reach a consensus on w=
hether a result reported by the worker is true. The consensus is reached vi=
a optional rounds of verification and arbitrage. The protocol is cryptoecon=
omically-safe, i.e. has a proven Nash equilibrium. The protocol was later t=
ransferred to LNP/BP Standards Association (https://lnp-bp.org) and was kep=
t in a backlog of what can be done in a future as a layer on top of Bitcoin=
.
> >=20
> > I'd like to emphasize that Prometheus works on Bitcoin, requires just s=
everal Bitcoin tx per task, and _doesn't require any soft fork_. All econom=
ic setting is done with Bitcoin as a means of payment, and using existing B=
itcoin script capabilities.
> >=20
> > Link to the paper describing the protocol: <https://github.com/Promethe=
us-WG/prometheus-spec/blob/master/prometheus.pdf>
> >=20
> > Only today I have realized that Prometheus protocol can be used to buil=
d cryptoeconomically-safe (i.e. trustless) 2-way-peg on the Bitcoin blockch=
ain without any soft-forks: a "worker" in such a case acts as an oracle for=
some extra-bitcoin system (sidechain, client-side-validated protocol, zk r=
ollup etc) validating it, and the protocol will reach consensus on whether =
the state reported by the oracle is correct.
> >=20
> > In other words, this is an alternative to BIP-300 and other similar sof=
t-forks having the only purpose of doing 2-way pegs. It also enables the tw=
o-way trustless transfer of Bitcoins between Bitcoin blockchain, RGB and, i=
n a future, potential new layer 1 called "prime" (to learn more about prime=
you can check my Baltic Honeybadger talk <https://www.youtube.com/live/V3v=
vybsc1A4?feature=3Dshared&t=3D23631>).
> >=20
> >=20
> > Kind regards,
> > Dr Maxim Orlovsky
> > Twitter: @dr_orlovsky
> > Nostr: npub13mhg7ksq9efna8ullmc5cufa53yuy06k73q4u7v425s8tgpdr5msk5mnym
> >=20
> > LNP/BP Standards Association
> > Twitter: @lnp_bp
> >=20
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
|
