From: Thomas Kerin <thomas.kerin@gmail•com>
To: "Arthur - bitcoin-fr.io" <arthur@bitcoin-fr•io>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] URI scheme for signing and verifying messages
Date: Tue, 15 Sep 2015 00:51:27 +0100 [thread overview]
Message-ID: <CAHv+tb5ym=bEdGGAYGqKqNXfVCESmt924i+vajavprnBrbhvbg@mail.gmail.com> (raw)
In-Reply-To: <c5f5105e2d5b9cc1873f84cb0b172285@rainloop.aaawop.com>
[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]
I think it would be more akin to bip70. I have a similar proposal, largely
already written up around this. I'm very interested in having this for
multi signature wallets.
On 14 Sep 2015 8:06 pm, "Arthur - bitcoin-fr.io via bitcoin-dev" <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> Hi,
> I realized that there isn't any way to ask for a signature (or to verify a
> message) as easily you can do when requesting a payment using a bitcoin 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 become available in most
> bitcoin clients who already support message signing/verifying and payment
> url (or QRCode) and enable new uses of bitcoin signatures.
> A way to gain proper consensus is going through a BIP, so that's why I'm
> here: to present my idea publicly before going any further (draft BIP and
> reference implementation).
> Some thoughts
> - like BIP0021: "Bitcoin clients MUST NOT act on URIs without getting the
> user's authorization." so signing requires the user to manually approve the
> process
> - it could use the same URI scheme than BIP0021 with an additional
> parameter (ex: signaction=<verify/sign>) or use another one like BIP121
> (ex: btcsig:)
> PS : I'll also post a topic in "Development & Technical Discussion"
> section on Bitcointalk
>
> --
> Arthur Bouquet
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
[-- Attachment #2: Type: text/html, Size: 2287 bytes --]
next prev parent reply other threads:[~2015-09-14 23:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 18:57 Arthur - bitcoin-fr.io
2015-09-14 23:51 ` Thomas Kerin [this message]
2015-09-15 4:03 ` Luke Dashjr
2015-09-15 10:49 ` Arthur - bitcoin-fr.io
2015-09-15 12:08 ` Luke Dashjr
2015-09-15 13:21 ` Arthur - bitcoin-fr.io
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='CAHv+tb5ym=bEdGGAYGqKqNXfVCESmt924i+vajavprnBrbhvbg@mail.gmail.com' \
--to=thomas.kerin@gmail$(echo .)com \
--cc=arthur@bitcoin-fr$(echo .)io \
--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