<div dir="ltr"><div><div><div><div>There was some discussion on the bitcointalk forums about using CLTV for cross chain transfers.<br><br></div>Many altcoins don't support CLTV, so transfers to those coins cannot be made secure. <br><br></div>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.<br><br></div></div>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.<br><div><div><div><div><br><a href="https://github.com/TierNolan/bips/blob/cpkv/bip-cprkv.mediawiki">https://github.com/TierNolan/bips/blob/cpkv/bip-cprkv.mediawiki</a><br></div></div></div></div></div><div id="DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><table style="border-top:1px solid #aaabb6;margin-top:30px">
<tr>
<td style="width:105px;padding-top:15px">
<a href="https://www.avast.com/sig-email" target="_blank"><img src="https://ipmcdn.avast.com/images/logo-avast-v1.png" style="width: 90px; height:33px;"></a>
</td>
<td style="width:470px;padding-top:20px;color:#41424e;font-size:13px;font-family:Arial,Helvetica,sans-serif;line-height:18px">This email has been sent from a virus-free computer protected by Avast. <br><a href="https://www.avast.com/sig-email" target="_blank" style="color:#4453ea">www.avast.com</a>
</td>
</tr>
</table><a href="#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"></a></div>