From: Cameron Garnham <da2ce7@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] BIP 21 (modification BIP 20)
Date: Wed, 01 Feb 2012 00:20:10 +1100 [thread overview]
Message-ID: <4F27EA8A.6010506@gmail.com> (raw)
In-Reply-To: <CABsx9T127RTX8Ha1yb4PnTcRSB22EC4+y4QrekZzz=pSvotjHQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 509 bytes --]
On 1/02/2012 00:12, Gavin Andresen wrote:
> RE: BIP 21 versus BIP 20: I like BIP 21; simpler is better.
>
> RE: signing and dating URIs: good ideas. I think we should agree
> that there is consensus around BIP 21 and then after there is some
> experience with signing/dating URIs you should write follow-up BIPs .
>
If we had a self signed URI, we could just pay directly to the public
key (or calculate the bitcoin address from it). It
would no longer require a bitcoin address in the URI.
[-- Attachment #1.2: 0x33B5E7D6.asc --]
[-- Type: application/pgp-keys, Size: 2692 bytes --]
[-- Attachment #1.3: 0x33B5E7D6.asc --]
[-- Type: application/pgp-keys, Size: 2690 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 283 bytes --]
next prev parent reply other threads:[~2012-01-31 13:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 18:50 Gary Rowe
2012-01-30 18:56 ` Luke-Jr
2012-01-30 19:13 ` Gary Rowe
2012-01-30 19:17 ` Luke-Jr
2012-01-31 6:54 ` thomasV1
2012-01-31 13:12 ` Gavin Andresen
2012-01-31 13:20 ` Cameron Garnham [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-31 10:39 [Bitcoin-development] BIP 21 (modification BIP 20)] Pieter Wuille
2012-01-30 18:07 [Bitcoin-development] BIP 21 (modification BIP 20) thomasV1
2012-01-30 18:44 ` Luke-Jr
2012-01-29 23:55 Amir Taaki
2012-01-30 9:13 ` Wladimir
2012-01-31 8:23 ` Andreas Schildbach
2012-01-31 8:35 ` Wladimir
2012-01-31 10:01 ` Gary Rowe
2012-01-31 10:22 ` Wladimir
2012-01-31 11:55 ` Andreas Schildbach
2012-01-31 12:03 ` Wladimir
2012-01-31 10:44 ` Pieter Wuille
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=4F27EA8A.6010506@gmail.com \
--to=da2ce7@gmail$(echo .)com \
--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