From: Pavol Rusnak <stick@satoshilabs.com>
To: DKBryant@gmail.com,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Sign / Verify message against SegWit P2SH addresses.
Date: Tue, 19 Dec 2017 22:36:45 +0100 [thread overview]
Message-ID: <52b65bab-ff84-7e21-e35a-f6ebd8106767@satoshilabs.com> (raw)
In-Reply-To: <CAAUFj10gEPBS3nTZ6aJn4UazhcJKPni6_pYGWwOs+QNeDo9NaA@mail.gmail.com>
On 08/12/17 19:25, Dan Bryant via bitcoin-dev wrote:
> I know there are posts, and an issue opened against it, but is there
> anyone writing a BIP for Sign / Verify message against a SegWit address?
Dan, are you still planning to write this BIP?
--
Best Regards / S pozdravom,
Pavol "stick" Rusnak
CTO, SatoshiLabs
next prev parent reply other threads:[~2017-12-19 21:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 18:25 [bitcoin-dev] Sign / Verify message against SegWit P2SH addresses Dan Bryant
2017-12-09 12:57 ` Sjors Provoost
2017-12-19 21:36 ` Pavol Rusnak [this message]
2017-12-19 21:58 ` Mark Friedenbach
2017-12-21 11:19 ` Damian Williamson
2017-12-21 16:29 ` Mark Friedenbach
2017-12-21 17:23 ` Jason Dreyzehner
2017-12-21 22:22 ` Dan Bryant
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=52b65bab-ff84-7e21-e35a-f6ebd8106767@satoshilabs.com \
--to=stick@satoshilabs.com \
--cc=DKBryant@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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