From: Dan Bryant <dkbryant@gmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] BIP for Legacy Sign Verify functions
Date: Thu, 21 Dec 2017 16:26:25 -0600 [thread overview]
Message-ID: <CAAUFj100ULfTbEorSK2PF5nvW-R_TCMOiboBBEMj+eS5upgU8Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 366 bytes --]
https://github.com/brianddk/bips/blob/legacysignverify/bip-0xyz.mediawiki
Although this is a well established functionality, it has never been
published in a BIP. My proposal is simply to provide a reference point for
future expansion of these capabilities into new address schemes.
Original reference thread [Sign / Verify message against SegWit P2SH
addresses]
[-- Attachment #2: Type: text/html, Size: 580 bytes --]
next reply other threads:[~2017-12-21 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 22:26 Dan Bryant [this message]
2017-12-21 23:09 ` Luke Dashjr
2017-12-21 23:21 ` Dan Bryant
2017-12-22 10:29 ` Aymeric Vitte
2017-12-22 23:06 ` Aymeric Vitte
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=CAAUFj100ULfTbEorSK2PF5nvW-R_TCMOiboBBEMj+eS5upgU8Q@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