MIME-Version: 1.0
In-Reply-To: <CAE-z3OUpaMLxF9dGttzLUd6tG+nO18FMo3LZqr7taASVmrEumg@mail.gmail.com>
References: <CAE-z3OUpaMLxF9dGttzLUd6tG+nO18FMo3LZqr7taASVmrEumg@mail.gmail.com>
Date: Thu, 11 Feb 2016 22:20:33 +0000
Message-ID: <CAHv+tb7CMEpR9hLp6pJE9Nt=j5zvChNr1CvDXn8Pb-d2sRZSEA@mail.gmail.com>
From: Thomas Kerin <thomas.kerin@gmail.com>
To: Tier Nolan <tier.nolan@gmail.com>
Content-Type: multipart/alternative; boundary=001a113edb1c8ff51d052b85f5bb
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP CPRKV: Check private key verify
Precedence: list

--001a113edb1c8ff51d052b85f5bb
Content-Type: text/plain; charset=UTF-8

I wonder if this is possible as a soft fork without using segwit?
Increasing the sigop count for a NOP would be a hard fork, but such a
change would be fine with a new segwit version. It might require specific
support in the altcoin, which might be troublesome..
On 11 Feb 2016 20:05, "Tier Nolan via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> There was some discussion on the bitcointalk forums about using CLTV for
> cross chain transfers.
>
> Many altcoins don't support CLTV, so transfers to those coins cannot be
> made secure.
>
> I created a protocol.  It uses on cut and choose to allow commitments to
> publish private keys, but it is clunky and not entirely secure.
>
> I created a BIP draft for an opcode which would allow outputs to be locked
> unless a private key was published that matches a given public key.
>
> https://github.com/TierNolan/bips/blob/cpkv/bip-cprkv.mediawiki
> <https://www.avast.com/sig-email> This email has been sent from a
> virus-free computer protected by Avast.
> www.avast.com <https://www.avast.com/sig-email>
> <#-1229186329_DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>

--001a113edb1c8ff51d052b85f5bb
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">I wonder if this is possible as a soft fork without using se=
gwit? Increasing the sigop count for a NOP would be a hard fork, but such a=
 change would be fine with a new segwit version. It might require specific =
support in the altcoin, which might be troublesome..</p>
<div class=3D"gmail_quote">On 11 Feb 2016 20:05, &quot;Tier Nolan via bitco=
in-dev&quot; &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">b=
itcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br type=3D"attribution"=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div><div><div>There =
was some discussion on the bitcointalk forums about using CLTV for cross ch=
ain transfers.<br><br></div>Many altcoins don&#39;t support CLTV, so transf=
ers to those coins cannot be made secure.=C2=A0 <br><br></div>I created a p=
rotocol.=C2=A0 It uses on cut and choose to allow commitments to publish pr=
ivate keys, but it is clunky and not entirely secure.<br><br></div></div>I =
created a BIP draft for an opcode which would allow outputs to be locked un=
less a private key was published that matches a given public key.<br><div><=
div><div><div><br><a href=3D"https://github.com/TierNolan/bips/blob/cpkv/bi=
p-cprkv.mediawiki" target=3D"_blank">https://github.com/TierNolan/bips/blob=
/cpkv/bip-cprkv.mediawiki</a><br></div></div></div></div></div><div><table =
style=3D"border-top:1px solid #aaabb6;margin-top:30px">
	<tr>
		<td style=3D"width:105px;padding-top:15px">
			<a href=3D"https://www.avast.com/sig-email" target=3D"_blank"><img src=
=3D"https://ipmcdn.avast.com/images/logo-avast-v1.png" style=3D"width:90px;=
min-height:33px"></a>
		</td>
		<td style=3D"width:470px;padding-top:20px;color:#41424e;font-size:13px;fo=
nt-family:Arial,Helvetica,sans-serif;line-height:18px">This email has been =
sent from a virus-free computer protected by Avast. <br><a href=3D"https://=
www.avast.com/sig-email" style=3D"color:#4453ea" target=3D"_blank">www.avas=
t.com</a>
		</td>
	</tr>
</table><a href=3D"#-1229186329_DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width=
=3D"1" height=3D"1"></a></div>
<br>_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">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>
<br></blockquote></div>

--001a113edb1c8ff51d052b85f5bb--