summaryrefslogtreecommitdiff
path: root/47/4b01a8d9161b723f3d07317a92d3aaf114046e
blob: e1377cfcf46fe07e93d2d9bb52ad934b19fb9b69 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
Return-Path: <thomas.kerin@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 10585102F
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 11 Feb 2016 22:20:35 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-io0-f169.google.com (mail-io0-f169.google.com
	[209.85.223.169])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8A496161
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 11 Feb 2016 22:20:34 +0000 (UTC)
Received: by mail-io0-f169.google.com with SMTP id 9so71975843iom.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 11 Feb 2016 14:20:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=UXgPcrdLMVQVrWfobHEFQyyOru7j8r1ZyaQvJ6toCCw=;
	b=XmA+8rf3H9zKcgKJbjYoU+rb/wXH1OXG9WWdlMPM/62BMzv62/JgPexHE7fz3eCfYQ
	6yMsXi2SUcuqLtTnGL6QgbU8GOAiMtnY6cuLBsIpletLKuhwoyWVKd4g0qOvYImtsJXe
	wEndsQ2jc2s09qmObDnZif6Au/OCMXJ8qQSx1lomCd7V6TLkqX9l0lr100Rmgbq+SQrB
	ag56tY5ivRkTEwVWFaYEDxkZV9kgtcIcxJMwSXn/s0mv0wVz+0kRQhRWwDL9Mb3iZKyJ
	3qeQP2XGhZWsfgSyNqteQ4Vf8NJMnaq18kJFqaTEiFrYb77QOtTF2d95DXktHp4k/sF/
	d35g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:cc:content-type;
	bh=UXgPcrdLMVQVrWfobHEFQyyOru7j8r1ZyaQvJ6toCCw=;
	b=fvzngvXySGJwY1gJGulfnQCED4FlYDqE9FzoiZSwmU6kutXdxgyd3cj6ZEyF1z2ih0
	Ux5jCWEPn/cwQyiZhVhw2IAPPwdMv2rTzYqsPbTJdgMa4LoRQkr60WP7FD4lmaPrljd4
	iFMnIF7ixYXqRZ//GRZFCO2ChLUQfHyt+3aFzOxZpjEzfy037Cfg3z6lf3E6wh/J5EAU
	xPUpfQ+gXJ3hRc+foASBxRxc3UCsrC0pjr58sXtiAJmiMf1hHc1YyOfoXwSKYWhAjotU
	R/azRVTTV94pTkXl3VYS9Pi6tDW6pWLrjN9p2Y9xBrvMDc4zxbUuIdjMK8eTytd4L77Y
	cijg==
X-Gm-Message-State: AG10YOR8q48BT077cbwsmL41ulS4smyBu9DXhyMfUWOKsroBJkea5ShLyQ6knV9kxagxRboo5SvuC1xnNTPeyA==
MIME-Version: 1.0
X-Received: by 10.107.17.24 with SMTP id z24mr24039741ioi.78.1455229234048;
	Thu, 11 Feb 2016 14:20:34 -0800 (PST)
Received: by 10.107.48.15 with HTTP; Thu, 11 Feb 2016 14:20:33 -0800 (PST)
Received: by 10.107.48.15 with HTTP; Thu, 11 Feb 2016 14:20:33 -0800 (PST)
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
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_IMAGE_ONLY_28,
	HTML_MESSAGE, 
	RCVD_IN_DNSWL_LOW,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
X-Mailman-Approved-At: Fri, 12 Feb 2016 01:49:02 +0000
Cc: Bitcoin Dev <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 <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2016 22:20:35 -0000

--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--