From: Tier Nolan <tier.nolan@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP CPRKV: Check private key verify
Date: Mon, 29 Feb 2016 11:52:39 +0000 [thread overview]
Message-ID: <CAE-z3OWjqQ=UgNRXyxJiTzsW6Ze7Ytwz3kK2HYcC7eLy2jKnow@mail.gmail.com> (raw)
In-Reply-To: <CAE8CtVkuWL7XSEi_CTbrO2Ze7Q9a+V_P6=6cqGMXMouFzCio+Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 483 bytes --]
On Mon, Feb 29, 2016 at 10:58 AM, Mats Jerratsch <matsjj@gmail•com> 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 reference
client? I did a basic one, but it would need tests etc. added.
I think that segregated witness is going to be using up any potential
soft-fork slot for the time being anyway.
[-- Attachment #2: Type: text/html, Size: 946 bytes --]
next prev parent reply other threads:[~2016-02-29 11:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 20:05 Tier Nolan
2016-02-11 22:20 ` Thomas Kerin
2016-02-11 23:04 ` Tier Nolan
2016-02-12 5:02 ` jl2012
2016-02-12 10:05 ` Tier Nolan
2016-02-29 10:58 ` Mats Jerratsch
2016-02-29 11:52 ` Tier Nolan [this message]
2016-04-18 19:03 ` jl2012
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE-z3OWjqQ=UgNRXyxJiTzsW6Ze7Ytwz3kK2HYcC7eLy2jKnow@mail.gmail.com' \
--to=tier.nolan@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox