From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id B7B4DFFA for ; Fri, 12 Feb 2016 05:02:09 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from s47.web-hosting.com (s47.web-hosting.com [199.188.200.16]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0E91C15E for ; Fri, 12 Feb 2016 05:02:08 +0000 (UTC) Received: from 119246245241.ctinets.com ([119.246.245.241]:59139 helo=2012R2) by server47.web-hosting.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.86) (envelope-from ) id 1aU5rr-003fA2-EB; Fri, 12 Feb 2016 00:02:07 -0500 From: To: "'Tier Nolan'" References: In-Reply-To: Date: Fri, 12 Feb 2016 13:02:37 +0800 Message-ID: <23e401d16552$996546d0$cc2fd470$@xbt.hk> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_23E5_01D16595.A78AF7D0" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQKZ0cNygh4pHRrrw11uUfSX/C1ivJ2XAOHA Content-Language: en-hk X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server47.web-hosting.com X-AntiAbuse: Original Domain - lists.linuxfoundation.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - xbt.hk X-Get-Message-Sender-Via: server47.web-hosting.com: authenticated_id: jl2012@xbt.hk X-Authenticated-Sender: server47.web-hosting.com: jl2012@xbt.hk X-Source: X-Source-Args: X-Source-Dir: X-From-Rewrite: unmodified, already matched X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,T_REMOTE_IMAGE autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: bitcoin-dev@lists.linuxfoundation.org Subject: Re: [bitcoin-dev] BIP CPRKV: Check private key verify X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Feb 2016 05:02:09 -0000 This is a multipart message in MIME format. ------=_NextPart_000_23E5_01D16595.A78AF7D0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Seems it could be done without any new opcode: =20 Bob is trading b Bitcoins for a altcoins. =20 1. Bob Pays D Bitcoins to =20 IF CLTV DROP CHECKSIG ELSE HASH160 EQUALVERIFY CHECKSIG ENDIF =20 2. Alice pays a altcoins to =20 IF HASH160 EQUALVERIFY CHECKSIG ELSE HASH160 EQUALVERIFY CHECKSIG ENDIF =20 3. Bob pays b Bitcoins to =20 IF CLTV DROP CHECKSIG ELSE HASH160 EQUALVERIFY CHECKSIG ENDIF =20 4. Alice claims output from step 3 and reveals secret A =20 5. Bob claims output from step 2 =20 6. Bob claims output from step 1 and reveals secret B =20 From: bitcoin-dev-bounces@lists.linuxfoundation.org = [mailto:bitcoin-dev-bounces@lists.linuxfoundation.org] On Behalf Of Tier = Nolan via bitcoin-dev Sent: Friday, 12 February, 2016 04:05 To: Bitcoin Dev Subject: [bitcoin-dev] BIP CPRKV: Check private key verify =20 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. =20 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 =20 This email has been sent from a virus-free computer protected by Avast.=20 www.avast.com=20 =20 ------=_NextPart_000_23E5_01D16595.A78AF7D0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Seems it could be done without any new opcode:

 

Bob is trading b Bitcoins for a altcoins.

 

1. Bob Pays D Bitcoins to

 

IF

<now+2days> CLTV DROP <Alice PK> = CHECKSIG

ELSE

HASH160 <hash secret B> EQUALVERIFY <Bob PK> = CHECKSIG

ENDIF

 

2. Alice pays a altcoins to

 

IF

HASH160 <hash secret B> EQUALVERIFY <Alice PK> = CHECKSIG

ELSE

HASH160 <hash secret A> EQUALVERIFY <Bob PK> = CHECKSIG

ENDIF

 

3. Bob pays b Bitcoins to

 

IF

<now+1days> CLTV DROP <Bob PK> = CHECKSIG

ELSE

HASH160 <hash secret A> EQUALVERIFY <Alice PK> = CHECKSIG

ENDIF

 

4. Alice claims output from step 3 and reveals secret = A

 

5. Bob claims output from step 2

 

6. Bob claims output from step 1 and reveals secret = B

 

From:<= /b> = bitcoin-dev-bounces@lists.linuxfoundation.org = [mailto:bitcoin-dev-bounces@lists.linuxfoundation.org] On Behalf Of = Tier Nolan via bitcoin-dev
Sent: Friday, 12 February, 2016 = 04:05
To: Bitcoin Dev = <bitcoin-dev@lists.linuxfoundation.org>
Subject: = [bitcoin-dev] BIP CPRKV: Check private key = verify

 

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.

T= his email has been sent from a virus-free computer protected by Avast. =
www.avast.com =

 

------=_NextPart_000_23E5_01D16595.A78AF7D0--