From: Dan Bryant <dkbryant@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Sign / Verify message against SegWit P2SH addresses.
Date: Fri, 8 Dec 2017 12:25:47 -0600 [thread overview]
Message-ID: <CAAUFj10gEPBS3nTZ6aJn4UazhcJKPni6_pYGWwOs+QNeDo9NaA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 334 bytes --]
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?
I realize it is not a feature in wide use, but I think it still serves an
important purpose, such as when proof of assets are requested.
ref: https://github.com/bitcoin/bitcoin/issues/10542
[-- Attachment #2: Type: text/html, Size: 486 bytes --]
next reply other threads:[~2017-12-08 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 18:25 Dan Bryant [this message]
2017-12-09 12:57 ` Sjors Provoost
2017-12-19 21:36 ` Pavol Rusnak
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=CAAUFj10gEPBS3nTZ6aJn4UazhcJKPni6_pYGWwOs+QNeDo9NaA@mail.gmail.com \
--to=dkbryant@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