MIME-Version: 1.0
Reply-To: DKBryant@gmail.com
From: Dan Bryant <dkbryant@gmail.com>
Date: Thu, 21 Dec 2017 16:26:25 -0600
Message-ID: <CAAUFj100ULfTbEorSK2PF5nvW-R_TCMOiboBBEMj+eS5upgU8Q@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="001a113ee03acfde200560e13011"
Subject: [bitcoin-dev] BIP for Legacy Sign Verify functions
Precedence: list

--001a113ee03acfde200560e13011
Content-Type: text/plain; charset="UTF-8"

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]

--001a113ee03acfde200560e13011
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><a href=3D"https://github.com/brianddk/bips/blob/lega=
cysignverify/bip-0xyz.mediawiki" style=3D"font-size:12.8px" target=3D"_blan=
k">https://github.com/brianddk/<wbr>bips/blob/legacysignverify/<wbr>bip-0xy=
z.mediawiki</a><br></div><div><br></div>Although this is a well established=
 functionality, it has never been published in a BIP.=C2=A0 My proposal is =
simply to provide a reference point for future expansion of these capabilit=
ies into new address schemes.<div><br></div><div>Original reference thread =
[Sign / Verify message against SegWit P2SH addresses]</div></div>

--001a113ee03acfde200560e13011--