MIME-Version: 1.0
References: <CAPg+sBgKY-nmL=x+LVubtB0fFBAwd-1CDHT7zhidX8p9DLSGyg@mail.gmail.com>
	<CAAt2M1-DTzKct-NU9TotxDve8vLe5HFYxHZbq+t_A69C1nL-PA@mail.gmail.com>
	<CAAS2fgRnd8WDPYturJZk5T-Q8KVbr4ZVOHq4s-UDOwL0KnBuRA@mail.gmail.com>
In-Reply-To: <CAAS2fgRnd8WDPYturJZk5T-Q8KVbr4ZVOHq4s-UDOwL0KnBuRA@mail.gmail.com>
From: Natanael <natanael.l@gmail.com>
Date: Thu, 24 May 2018 11:32:23 +0200
Message-ID: <CAAt2M19BMdD4SM1vOvt1pe+3dCspwFwECgk7ZEQFVHHA3Q_8Jw@mail.gmail.com>
To: Gregory Maxwell <greg@xiph.org>
Content-Type: multipart/alternative; boundary="000000000000e4820c056cf05471"
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Should Graftroot be optional?
Precedence: list

--000000000000e4820c056cf05471
Content-Type: text/plain; charset="UTF-8"

Den tor 24 maj 2018 01:45Gregory Maxwell <greg@xiph.org> skrev:

> I am having a bit of difficulty understanding your example.
>
> If graftroot were possible it would mean that the funds were paid to a
> public key.  That holder(s) of the corresponding private key could
> sign without constraint, and so the accoutability you're expecting
> wouldn't exist there regardless of graftroot.
>
> I think maybe your example is only making the case that it should be
> possible to send funds constrained by a script without a public key
> ever existing at all.  If so, I agree-- but that wasn't the question
> here as I understood it.
>

I have to admit I not an expert on this field, so some of my concerns might
not be relevant. However, I think Wuille understood my points and his reply
answered my concerns quite well. I'm only asking for the optional ability
to prove you're not using these constructions (because some uses requires
committing to an immutable script), and that already seems to exist. So for
the future implementations I only ask that this ability is preserved.

I think such a proof don't need to be public (making such a proof in
private is probably often better), although optionally it might be. A
private contract wouldn't publish these details, while a public commitment
would do so.

>

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

<div dir=3D"auto"><div><br><br><div class=3D"gmail_quote"><div dir=3D"ltr">=
Den tor 24 maj 2018 01:45Gregory Maxwell &lt;<a href=3D"mailto:greg@xiph.or=
g">greg@xiph.org</a>&gt; skrev:</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I am having a bit of difficulty understanding your example.<br>
<br>
If graftroot were possible it would mean that the funds were paid to a<br>
public key.=C2=A0 That holder(s) of the corresponding private key could<br>
sign without constraint, and so the accoutability you&#39;re expecting<br>
wouldn&#39;t exist there regardless of graftroot.<br>
<br>
I think maybe your example is only making the case that it should be<br>
possible to send funds constrained by a script without a public key<br>
ever existing at all.=C2=A0 If so, I agree-- but that wasn&#39;t the questi=
on<br>
here as I understood it.<br></blockquote></div></div><div dir=3D"auto"><br>=
</div><div dir=3D"auto">I have to admit I not an expert on this field, so s=
ome of my concerns might not be relevant. However, I think Wuille understoo=
d my points and his reply answered my concerns quite well. I&#39;m only ask=
ing for the optional ability to prove you&#39;re not using these constructi=
ons (because some uses requires committing to an immutable script), and tha=
t already seems to exist. So for the future implementations I only ask that=
 this ability is preserved.=C2=A0</div><div dir=3D"auto"><br></div><div dir=
=3D"auto">I think such a proof don&#39;t need to be public (making such a p=
roof in private is probably often better), although optionally it might be.=
 A private contract wouldn&#39;t publish these details, while a public comm=
itment would do so.=C2=A0</div><div dir=3D"auto"><div class=3D"gmail_quote"=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">
</blockquote></div></div></div>

--000000000000e4820c056cf05471--