From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] BIP 0020: URI Scheme
Date: Fri, 27 Jan 2012 20:45:09 -0500 [thread overview]
Message-ID: <201201272045.10787.luke@dashjr.org> (raw)
In-Reply-To: <05d62c81-ef50-4c43-8fa5-65592c8f54a4@email.android.com>
On Friday, January 27, 2012 7:36:31 PM bitcoin-list@bluematt•me wrote:
> It was implemented in the waylaying client with the merge of Bitcoin-Qt for
> drag and drop, and just recently for system URI handling in
> https://github.com/bitcoin/bitcoin/commit/70f55355e29c8e45b607e782c5d76609
> d23cc858.
It's been implemented in many clients for nearly all 2011.
Bitcoin-Qt is just behind the pace. Not relevant.
> However the version on the wiki armed as BIP 20 has a ton of extraneous crap
> in it's number encoding which is not implemented in Bitcoin-Qt since it was
> explicitly voted against at the time the spec was being discussed.
You mean 3 months *after* the spec had a consensus and multiple
implementations.
next prev parent reply other threads:[~2012-01-28 1:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 22:51 Amir Taaki
2012-01-27 23:00 ` Luke-Jr
2012-01-28 0:36 ` bitcoin-list
2012-01-28 1:45 ` Luke-Jr [this message]
2012-01-28 2:12 ` bitcoin-list
2012-01-28 8:23 ` Wladimir
2012-01-28 16:32 ` Andreas Schildbach
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=201201272045.10787.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