From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Signature Blocks and URI Sign Requests
Date: Mon, 2 Apr 2012 20:44:37 -0400 [thread overview]
Message-ID: <201204022044.38861.luke@dashjr.org> (raw)
In-Reply-To: <4F7A1227.7070306@gmail.com>
On Monday, April 02, 2012 4:55:03 PM Alan Reiner wrote:
> Any thoughts? (I have no doubts that there are :) )
IMO, the sign-request URI should be an extension on the existing bitcoin: URI
scheme; this way, sigNeeded can be omitted to imply "sign with a sending
address".
next prev parent reply other threads:[~2012-04-03 0:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 20:55 Alan Reiner
2012-04-03 0:44 ` Luke-Jr [this message]
2012-04-03 18:46 ` Gavin Andresen
2012-04-03 18:55 ` Luke-Jr
2012-04-03 19:42 ` Wladimir
2012-04-03 20:04 ` Peter Vessenes
2012-04-03 21:12 ` Alan Reiner
2012-04-03 23:37 ` Mike Koss
2012-04-04 0:01 ` Alan Reiner
2012-04-04 6:23 ` Wladimir
2012-04-04 8:35 ` Michael Grønager
2012-04-03 20:51 ` Alan Reiner
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=201204022044.38861.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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