MIME-Version: 1.0
References: <Q26yJ8xABAnyKIAJ7nAt5er5Tok-tqvbQYhN7Wxh1xdlod-Kg5d7jefrxEgeini54ZIPup3jIGjmTx1gZBKEIjT7mYSQlXcTwG-Olo4pz8E=@protonmail.com>
In-Reply-To: <Q26yJ8xABAnyKIAJ7nAt5er5Tok-tqvbQYhN7Wxh1xdlod-Kg5d7jefrxEgeini54ZIPup3jIGjmTx1gZBKEIjT7mYSQlXcTwG-Olo4pz8E=@protonmail.com>
From: Bram Cohen <bram@chia.net>
Date: Sat, 21 May 2022 08:37:51 -0700
Message-ID: <CAHUJnBCjYpVVsR2gVzsODwVgjmFCsTEmi7=KYAm4i32j5sK3RA@mail.gmail.com>
To: alicexbt <alicexbt@protonmail.com>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="0000000000007446bf05df8764bd"
Subject: Re: [bitcoin-dev] CTV BIP Meeting #9 Notes
Precedence: list

--0000000000007446bf05df8764bd
Content-Type: text/plain; charset="UTF-8"

On Thu, May 19, 2022 at 9:17 AM alicexbt via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

>
> MEV could be one the issues associated with general covenants. There are
> some resources on https://mev.day if anyone interested to read more about
> it.
>

One of the top things to do about MEV is to make all transactions in a
block simultaneous, so for example if you have a price oracle it can be
limited to only reporting one price per block so although it can be
manipulated to either report a high or low price it can't simultaneously do
both. In Bitcoin ordering is strictly enforced but there's a loophole that
things which happen in the same transaction do happen simultaneously, so
future extensions could be made to only sign things they care about and are
okay with transactions getting aggregated just by smushing them together.
That of course requires a new signature opcode, because current signatures
always sign the whole transaction.

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

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, May 19, 2022 at 9:17 AM alicexbt =
via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org=
">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></div><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><di=
v style=3D"font-family:arial;font-size:14px"><br></div><div style=3D"font-f=
amily:arial;font-size:14px"><span>MEV could be one the issues associated wi=
th general covenants. There are some resources on <a rel=3D"noreferrer nofo=
llow noopener" href=3D"https://mev.day" target=3D"_blank">https://mev.day</=
a> if anyone interested to read more about it.</span></div></div></blockquo=
te><div><br></div><div>One of the top things to do about MEV is to make all=
 transactions in a block simultaneous, so for example if you have a price o=
racle it can be limited to only reporting one price per block so although i=
t can be manipulated to either report a high or low price it can&#39;t simu=
ltaneously do both. In Bitcoin ordering is strictly enforced but there&#39;=
s a loophole that things which happen in the same transaction do happen sim=
ultaneously, so future extensions could be made to only sign things they ca=
re about and are okay with transactions getting aggregated just by smushing=
 them together. That of course requires a new signature opcode, because cur=
rent signatures always sign the whole transaction.</div></div></div>

--0000000000007446bf05df8764bd--