📅 Original date posted:2016-02-12
📝 Original message: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: bitcoin-dev-bounces at lists.linuxfoundation.org [mailto:bitcoin-dev-bounces at lists.linuxfoundation.org] On Behalf Of Tier Nolan via bitcoin-dev
Sent: Friday, 12 February, 2016 04:05
To: Bitcoin Dev <bitcoin-dev at 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.
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.
<https://www.avast.com/sig-email>; www.avast.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160212/055b7677/attachment-0001.html>;
jl2012 at xbt.hk [ARCHIVE] /
npub1kc…wjfw4
2023-06-07 17:49:08
in reply to nevent1q…872p
Author Public Key
npub1kc0zulxt7j4a0ayhzhrz7jk84y7tm4026qcky7w97hlfkxxap24qnwjfw4Published at
2023-06-07 17:49:08Event JSON
{
"id": "6b7cb8805550ab3050f76ee264228ebb9fa1ba6bd19bd78f222c9a3d83d7c43d",
"pubkey": "b61e2e7ccbf4abd7f49715c62f4ac7a93cbdd5ead0316279c5f5fe9b18dd0aaa",
"created_at": 1686160148,
"kind": 1,
"tags": [
[
"e",
"6045e898b383d0c897715fcc05bc14751f115c56975a03880f5f4be9fb31482b",
"",
"root"
],
[
"e",
"60e4526bc70c28dbdf0e8b825bcd5e49fc9f415d611c5e597ef6f2517f4d4d7d",
"",
"reply"
],
[
"p",
"cd7a2cba8fb58a6131210185f2257692f56b666fb24bf9cf016ca8aaa4a4ae01"
]
],
"content": "📅 Original date posted:2016-02-12\n📝 Original message:Seems it could be done without any new opcode:\n\n \n\nBob is trading b Bitcoins for a altcoins.\n\n \n\n1. Bob Pays D Bitcoins to\n\n \n\nIF\n\n\u003cnow+2days\u003e CLTV DROP \u003cAlice PK\u003e CHECKSIG\n\nELSE\n\nHASH160 \u003chash secret B\u003e EQUALVERIFY \u003cBob PK\u003e CHECKSIG\n\nENDIF\n\n \n\n2. Alice pays a altcoins to\n\n \n\nIF\n\nHASH160 \u003chash secret B\u003e EQUALVERIFY \u003cAlice PK\u003e CHECKSIG\n\nELSE\n\nHASH160 \u003chash secret A\u003e EQUALVERIFY \u003cBob PK\u003e CHECKSIG\n\nENDIF\n\n \n\n3. Bob pays b Bitcoins to\n\n \n\nIF\n\n\u003cnow+1days\u003e CLTV DROP \u003cBob PK\u003e CHECKSIG\n\nELSE\n\nHASH160 \u003chash secret A\u003e EQUALVERIFY \u003cAlice PK\u003e CHECKSIG\n\nENDIF\n\n \n\n4. Alice claims output from step 3 and reveals secret A\n\n \n\n5. Bob claims output from step 2\n\n \n\n6. Bob claims output from step 1 and reveals secret B\n\n \n\nFrom: bitcoin-dev-bounces at lists.linuxfoundation.org [mailto:bitcoin-dev-bounces at lists.linuxfoundation.org] On Behalf Of Tier Nolan via bitcoin-dev\nSent: Friday, 12 February, 2016 04:05\nTo: Bitcoin Dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e\nSubject: [bitcoin-dev] BIP CPRKV: Check private key verify\n\n \n\nThere was some discussion on the bitcointalk forums about using CLTV for cross chain transfers.\n\nMany altcoins don't support CLTV, so transfers to those coins cannot be made secure. \n\nI created a protocol. It uses on cut and choose to allow commitments to publish private keys, but it is clunky and not entirely secure.\n\nI 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.\n\n\nhttps://github.com/TierNolan/bips/blob/cpkv/bip-cprkv.mediawiki\n\n\n \u003chttps://www.avast.com/sig-email\u003e \n\nThis email has been sent from a virus-free computer protected by Avast. \n \u003chttps://www.avast.com/sig-email\u003e www.avast.com \n\n \n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160212/055b7677/attachment-0001.html\u003e",
"sig": "a4d3d48aa11f518ab0c92d5ef6eba37d5119ce7b59f051186f251ad5dbb305970b28b12913b575a807e9a6c016512fd54dab2dac77c3578a0dacd2880893492d"
}