path: root/7d/edd42fdc35df82f6f91fb4bbda36568a8a2fbc

Return-Path: <g.andrew.stone@gmail.com>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 3D6ABC0032
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 11 Sep 2023 15:27:06 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp3.osuosl.org (Postfix) with ESMTP id 16D5960A80
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 11 Sep 2023 15:27:06 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 16D5960A80
Authentication-Results: smtp3.osuosl.org;
 dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com
 header.a=rsa-sha256 header.s=20221208 header.b=O3l5xDia
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 smtp3.osuosl.org ([127.0.0.1])
 by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id aIrZ_degJBeo
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 11 Sep 2023 15:27:05 +0000 (UTC)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com
 [IPv6:2607:f8b0:4864:20::42f])
 by smtp3.osuosl.org (Postfix) with ESMTPS id F0E8060A5F
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 11 Sep 2023 15:27:04 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org F0E8060A5F
Received: by mail-pf1-x42f.google.com with SMTP id
 d2e1a72fcca58-68fbd5cd0ceso1077903b3a.1
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 11 Sep 2023 08:27:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s=20221208; t=1694446024; x=1695050824;
 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=nVmn2Zp8o0oghPkaJMoTqF4rp3pHypJqm/gjTDsGdH0=;
 b=O3l5xDiaBDETxS9jc8IQh8Govgd7F1p8ez9OHIJeG9GRGqhajdbGKpvCY6W5FATwPT
 wBg3a4+6Uik/kjjfmlILoCKOBzwz1K4mO8Bkib4mK8smXKdlRRnwYbuB4RtbjCeMtFwJ
 q8ae2JVmR+fUsgtipepSR/GfzSdccZQD3ad4HgPOVQ0kTSlgmNhiRE3iJzJmjF252CTC
 /oV6B1nNnO3FzkkvxJtprV3SRUqcxFkP3lwQ+tRkGQnbEZSm1RGz9mo2YQO8mmaOvHxa
 UHfND4kSfXLcQUTSChKDezKUEfNSvOu5Jqj5twW/l1wMe2jIcEpuOKii0Ih8jX6iZdx/
 hAUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20230601; t=1694446024; x=1695050824;
 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=nVmn2Zp8o0oghPkaJMoTqF4rp3pHypJqm/gjTDsGdH0=;
 b=leOHP8jEL/wTCSeN+WfKi/mzeh3gjZfWXQiAShKPIf/+5vYvF8lGOVyvRzae4pEN81
 kmA3/bgG7roxWJ8Ewc0rL5nXmIJNa6EfGt2tK9cRgcJs+g2al++bzhXILVYFMQtdKiv2
 7coJE3rqDKbkT5ctMKAdRCVwcJwKv0s9gnA0qxJ0iIgpWFaJ7qOSk5RpxAX5HwueMkpx
 Tq1ycP34BbOp7hS5fl9ekv70Q+WMSx9Vtggupr2QEGo5+Ma12XzG13g6lscLZVBdIXU0
 33mcgcPwWUUFAXO5NsROaPj4DVMpirVgIbSjOS0FxQEqldOXV4ZZldJg7EbNZzDOct01
 j61Q==
X-Gm-Message-State: AOJu0YxujbKOa3szO53WsWTWIMcv6Gt0N/pC1gz9koLGdKJbwkJ9ydu2
 ulFxPObmKqAM0HX+wqJ++VUccL++hBEQvAPedaA=
X-Google-Smtp-Source: AGHT+IFy1F+lVp2wi0GIeHRxtbhY9841GbHrzILcKbjeNWp1eCYl0o8KDm4hekBrE+WH5Owqq0twRbJvhwJwu1lX4oc=
X-Received: by 2002:a17:90b:1093:b0:26b:e27:8bc2 with SMTP id
 gj19-20020a17090b109300b0026b0e278bc2mr8782143pjb.45.1694446023890; Mon, 11
 Sep 2023 08:27:03 -0700 (PDT)
MIME-Version: 1.0
References: <XDPm1ve5FC6e68LI_ZK4f_oRGDArvptCDh1ofEXNNZV9TaTQ_XRALF2KIdIknQOw-TXKJHedJ-5xHi0sbipTrF7qIe4ynp2Qxp823BGcXcY=@lnp-bp.org>
In-Reply-To: <XDPm1ve5FC6e68LI_ZK4f_oRGDArvptCDh1ofEXNNZV9TaTQ_XRALF2KIdIknQOw-TXKJHedJ-5xHi0sbipTrF7qIe4ynp2Qxp823BGcXcY=@lnp-bp.org>
From: "G. Andrew Stone" <g.andrew.stone@gmail.com>
Date: Mon, 11 Sep 2023 11:26:52 -0400
Message-ID: <CAHUwRvtadqomqDpWBuOwjJR7ftsTpE_-C4mPVAg0j3HqR6vFUw@mail.gmail.com>
To: Dr Maxim Orlovsky <orlovsky@lnp-bp.org>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000585d74060516f575"
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: Mon, 11 Sep 2023 15:27:06 -0000

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

Any chance of a quick tldr to pique our interest by explaining how exactly
this works "and the protocol will reach consensus on whether the state
reported by the oracle is correct" in presumably a permissionless,
anonymous, decentralized fashion, and what caveats there are?

Regards,
Andrew

On Sun, Sep 10, 2023 at 4:06=E2=80=AFPM Dr Maxim Orlovsky via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Hi,
>
> Several years ago my team from Pandora Project working on
> censorship-resistant distributed machine learning proposed Prometheus: a
> protocol for high-load computing on top of Bitcoin. The protocol operates
> as a multi-party game setting where an oracle ("worker") is provided with
> an arbitrary computationally complex task (any Turing-complete computing,
> machine learning training or inference etc) and the network is able to
> reach a consensus on whether a result reported by the worker is true. The
> consensus is reached via optional rounds of verification and arbitrage. T=
he
> protocol is cryptoeconomically-safe, i.e. has a proven Nash equilibrium.
> The protocol was later transferred to LNP/BP Standards Association (
> https://lnp-bp.org) and was kept in a backlog of what can be done in a
> future as a layer on top of Bitcoin.
>
> I'd like to emphasize that Prometheus works on Bitcoin, requires just
> several Bitcoin tx per task, and _doesn't require any soft fork_. All
> economic setting is done with Bitcoin as a means of payment, and using
> existing Bitcoin script capabilities.
>
> Link to the paper describing the protocol: <
> https://github.com/Prometheus-WG/prometheus-spec/blob/master/prometheus.p=
df
> >
>
> Only today I have realized that Prometheus protocol can be used to build
> cryptoeconomically-safe (i.e. trustless) 2-way-peg on the Bitcoin
> blockchain 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 rollup etc) validating it, and the protocol will reach
> consensus on whether the state reported by the oracle is correct.
>
> In other words, this is an alternative to BIP-300 and other similar
> soft-forks having the only purpose of doing 2-way pegs. It also enables t=
he
> two-way trustless transfer of Bitcoins between Bitcoin blockchain, RGB an=
d,
> in 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/V3vvybsc1A4?feature=3Dshared&t=3D23631>).
>
>
> Kind regards,
> Dr Maxim Orlovsky
> Twitter: @dr_orlovsky
> Nostr: npub13mhg7ksq9efna8ullmc5cufa53yuy06k73q4u7v425s8tgpdr5msk5mnym
>
> LNP/BP Standards Association
> Twitter: @lnp_bp
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"ltr"><div>Any chance of a quick tldr to pique our interest by e=
xplaining how exactly this works &quot;and the protocol will reach consensu=
s on whether the state reported by the oracle is correct&quot; in presumabl=
y a permissionless, anonymous, decentralized fashion, and what caveats ther=
e are?</div><div><br></div><div>Regards,</div><div>Andrew<br></div></div><b=
r><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, =
Sep 10, 2023 at 4:06=E2=80=AFPM Dr Maxim Orlovsky via bitcoin-dev &lt;<a hr=
ef=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linux=
foundation.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex">Hi,<br>
<br>
Several years ago my team from Pandora Project working on censorship-resist=
ant distributed machine learning proposed Prometheus: a protocol for high-l=
oad computing on top of Bitcoin. The protocol operates as a multi-party gam=
e setting where an oracle (&quot;worker&quot;) is provided with an arbitrar=
y computationally complex task (any Turing-complete computing, machine lear=
ning training or inference etc) and the network is able to reach a consensu=
s on whether a result reported by the worker is true. The consensus is reac=
hed via optional rounds of verification and arbitrage. The protocol is cryp=
toeconomically-safe, i.e. has a proven Nash equilibrium. The protocol was l=
ater transferred to LNP/BP Standards Association (<a href=3D"https://lnp-bp=
.org" rel=3D"noreferrer" target=3D"_blank">https://lnp-bp.org</a>) and was =
kept in a backlog of what can be done in a future as a layer on top of Bitc=
oin.<br>
<br>
I&#39;d like to emphasize that Prometheus works on Bitcoin, requires just s=
everal Bitcoin tx per task, and _doesn&#39;t require any soft fork_. All ec=
onomic setting is done with Bitcoin as a means of payment, and using existi=
ng Bitcoin script capabilities.<br>
<br>
Link to the paper describing the protocol: &lt;<a href=3D"https://github.co=
m/Prometheus-WG/prometheus-spec/blob/master/prometheus.pdf" rel=3D"noreferr=
er" target=3D"_blank">https://github.com/Prometheus-WG/prometheus-spec/blob=
/master/prometheus.pdf</a>&gt;<br>
<br>
Only today I have realized that Prometheus protocol can be used to build cr=
yptoeconomically-safe (i.e. trustless) 2-way-peg on the Bitcoin blockchain =
without any soft-forks: a &quot;worker&quot; in such a case acts as an orac=
le for some extra-bitcoin system (sidechain, client-side-validated protocol=
, zk rollup etc) validating it, and the protocol will reach consensus on wh=
ether the state reported by the oracle is correct.<br>
<br>
In other words, this is an alternative to BIP-300 and other similar soft-fo=
rks having the only purpose of doing 2-way pegs. It also enables the two-wa=
y trustless transfer of Bitcoins between Bitcoin blockchain, RGB and, in a =
future, potential new layer 1 called &quot;prime&quot; (to learn more about=
 prime you can check my Baltic Honeybadger talk &lt;<a href=3D"https://www.=
youtube.com/live/V3vvybsc1A4?feature=3Dshared&amp;t=3D23631" rel=3D"norefer=
rer" target=3D"_blank">https://www.youtube.com/live/V3vvybsc1A4?feature=3Ds=
hared&amp;t=3D23631</a>&gt;).<br>
<br>
<br>
Kind regards,<br>
Dr Maxim Orlovsky<br>
Twitter: @dr_orlovsky<br>
Nostr: npub13mhg7ksq9efna8ullmc5cufa53yuy06k73q4u7v425s8tgpdr5msk5mnym<br>
<br>
LNP/BP Standards Association<br>
Twitter: @lnp_bp<br>
<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>

--000000000000585d74060516f575--