Mime-Version: 1.0
Date: Mon, 14 Sep 2015 18:57:01 +0000
Content-Type: multipart/alternative;
	boundary="----=_Part_862_559512907.1442257021"
Message-ID: <c5f5105e2d5b9cc1873f84cb0b172285@rainloop.aaawop.com>
From: "Arthur - bitcoin-fr.io" <arthur@bitcoin-fr.io>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] URI scheme for signing and verifying messages
Precedence: list


------=_Part_862_559512907.1442257021
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi,I realized that there isn't any way to ask for a signature (or to veri=
fy a message) as easily you can do when requesting a payment using a bitc=
oin URI scheme (BIP0021).I think a URI scheme to use the signing tools in=
 bitcoin core might be useful, and with a proper consensus it could becom=
e available in most bitcoin clients who already support message signing/v=
erifying and payment url (or QRCode) and enable new uses of bitcoin signa=
tures.A way to gain proper consensus is going through a BIP, so that's wh=
y I'm here: to present my idea publicly before going any further (draft B=
IP and reference implementation).Some thoughts=C2=A0- like BIP0021: "Bitc=
oin clients MUST NOT act on URIs without getting the user's authorization=
." so signing requires the user to manually approve the process=C2=A0- it=
 could use the same URI scheme than BIP0021 with an additional parameter =
(ex: signaction=3D) or use another one like BIP121 (ex: btcsig:)PS : I'll=
 also post a topic in "Development & Technical Discussion" section on Bit=
cointalk=0A=C2=A0--Arthur Bouquet

------=_Part_862_559512907.1442257021
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><meta http-equiv=3D"Content-Type" content=3D"t=
ext/html; charset=3Dutf-8" /></head><body><div data-html-editor-font-wrap=
per=3D"true" style=3D"font-family: arial, sans-serif; font-size: 13px;">H=
i,<div class=3D"de2"></div><div class=3D"de1">I realized that there isn't=
 any way to ask for a signature (or to verify a message) as easily you ca=
n do when requesting a payment using a bitcoin URI scheme (BIP0021).</div=
><div class=3D"de2">I think a URI scheme to use the signing tools in bitc=
oin core might be useful, and with a proper consensus it could become ava=
ilable in most bitcoin clients who already support message signing/verify=
ing and payment url (or QRCode) and enable new uses of bitcoin signatures=
.</div><div class=3D"de1"></div><div class=3D"de2">A way to gain proper c=
onsensus is going through a BIP, so that's why I'm here: to present my id=
ea publicly before going any further (draft BIP and reference implementat=
ion).</div><div class=3D"de1"></div><div class=3D"de2">Some thoughts</div=
><div class=3D"de1">=C2=A0- like BIP0021: "Bitcoin clients MUST NOT act o=
n URIs without getting the user's authorization." so signing requires the=
 user to manually approve the process</div><div class=3D"de2">=C2=A0- it =
could use the same URI scheme than BIP0021 with an additional parameter (=
ex: signaction=3D&lt;verify/sign&gt;) or use another one like BIP121 (ex:=
 btcsig:)</div><div class=3D"de1"></div><div class=3D"de2">PS : I'll also=
 post a topic in "Development &amp; Technical Discussion" section on Bitc=
ointalk<br>=C2=A0</div><div class=3D"de2">--</div><div class=3D"de1">Arth=
ur Bouquet</div></div></body></html>

------=_Part_862_559512907.1442257021--