Re: [bitcoin-dev] BIP CPRKV: Check private key verify

2016-04-18 Thread jl2012--- via bitcoin-dev
On Behalf Of Tier Nolan via bitcoin-dev Sent: Monday, 29 February, 2016 19:53 Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org> Subject: Re: [bitcoin-dev] BIP CPRKV: Check private key verify On Mon, Feb 29, 2016 at 10:58 AM, Mats Jerratsch <mat...@gmail.com <ma

Re: [bitcoin-dev] BIP CPRKV: Check private key verify

2016-02-29 Thread Tier Nolan via bitcoin-dev
On Mon, Feb 29, 2016 at 10:58 AM, Mats Jerratsch wrote: > This is actually very useful for LN too, see relevant discussion here > > > http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-November/011827.html > Is there much demand for trying to code up a patch to the

Re: [bitcoin-dev] BIP CPRKV: Check private key verify

2016-02-29 Thread Mats Jerratsch via bitcoin-dev
This is actually very useful for LN too, see relevant discussion here http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-November/011827.html 2016-02-12 11:05 GMT+01:00 Tier Nolan via bitcoin-dev : > On Fri, Feb 12, 2016 at 5:02 AM,

Re: [bitcoin-dev] BIP CPRKV: Check private key verify

2016-02-12 Thread Tier Nolan via bitcoin-dev
On Fri, Feb 12, 2016 at 5:02 AM, wrote: > Seems it could be done without any new opcode: > The assumption was that the altcoin would only accept standard output scripts. Alice's payment in step 2 pays to a non-standard script. This is an improvement over the cut and choose, but

[bitcoin-dev] BIP CPRKV: Check private key verify

2016-02-11 Thread Tier Nolan via bitcoin-dev
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

Re: [bitcoin-dev] BIP CPRKV: Check private key verify

2016-02-11 Thread Tier Nolan via bitcoin-dev
On Thu, Feb 11, 2016 at 10:20 PM, Thomas Kerin wrote: > 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

Re: [bitcoin-dev] BIP CPRKV: Check private key verify

2016-02-11 Thread Thomas Kerin via bitcoin-dev
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

Re: [bitcoin-dev] BIP CPRKV: Check private key verify

2016-02-11 Thread jl2012--- via bitcoin-dev
als secret B From: bitcoin-dev-boun...@lists.linuxfoundation.org [mailto:bitcoin-dev-boun...@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: