MIME-Version: 1.0
References: <CALFqKjQkQwuxjeYkGWO_Y_HhNQmJgrjqF3m04hbORV7FSbsi3Q@mail.gmail.com>
	<87h87idpfh.fsf@jb55.com>
In-Reply-To: <87h87idpfh.fsf@jb55.com>
From: Pieter Wuille <pieter.wuille@gmail.com>
Date: Fri, 19 Jul 2019 12:17:38 -0700
Message-ID: <CAPg+sBg-9WMS2dTJswPbWGp6mwMwdit6yL0Pg=WhqEZKp4SpjA@mail.gmail.com>
To: William Casarin <jb55@jb55.com>,
	Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="0000000000000c50e9058e0d95d3"
Subject: Re: [bitcoin-dev] PubRef - Script OP Code For Public Data References
Precedence: list

--0000000000000c50e9058e0d95d3
Content-Type: text/plain; charset="UTF-8"

On Fri, Jul 19, 2019, 12:13 William Casarin via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

>
> Hello Mike,
>
> Mike Brooks via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
> writes:
>
> > Motivation
> >
> > Giving scripts the ability to refer to data on the blockchain will reduce
> > transaction sizes because key material does not have to be repeated in
> > every Script. Users of the network are rewarded with smaller transaction
> > sizes, and miners are able to fit more transactions into new blocks.
> > Pointers are a common feature and it felt like this was missing from
> > Bitcoin Script.
>
> This would incentivize address re-use which would be bad for
> fungibility. It appears you're trying to optimize a use case which is
> already discouraged :(
>

Furthermore, right now block validation does not require access to the
whole historical chain (only to the set of unspent outputs), so a change
like this would massively increase storage requirements for validation.

Cheers,

-- 
Pieter

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

<div dir=3D"auto"><div><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D=
"gmail_attr">On Fri, Jul 19, 2019, 12:13 William Casarin via bitcoin-dev &l=
t;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@list=
s.linuxfoundation.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
"><br>
Hello Mike,<br>
<br>
Mike Brooks via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfo=
undation.org" target=3D"_blank" rel=3D"noreferrer">bitcoin-dev@lists.linuxf=
oundation.org</a>&gt;<br>
writes:<br>
<br>
&gt; Motivation<br>
&gt;<br>
&gt; Giving scripts the ability to refer to data on the blockchain will red=
uce<br>
&gt; transaction sizes because key material does not have to be repeated in=
<br>
&gt; every Script. Users of the network are rewarded with smaller transacti=
on<br>
&gt; sizes, and miners are able to fit more transactions into new blocks.<b=
r>
&gt; Pointers are a common feature and it felt like this was missing from<b=
r>
&gt; Bitcoin Script.<br>
<br>
This would incentivize address re-use which would be bad for<br>
fungibility. It appears you&#39;re trying to optimize a use case which is<b=
r>
already discouraged :(<br></blockquote></div></div><div dir=3D"auto"><br></=
div><div dir=3D"auto">Furthermore, right now block validation does not requ=
ire access to the whole historical chain (only to the set of unspent output=
s), so a change like this would massively increase storage requirements for=
 validation.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Cheers,</di=
v><div dir=3D"auto"><br></div><div dir=3D"auto">--=C2=A0</div><div dir=3D"a=
uto">Pieter</div><div dir=3D"auto"><br></div><div dir=3D"auto"><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote></div></div></div>

--0000000000000c50e9058e0d95d3--