From: Wladimir <laanwj@gmail•com>
To: bitcoin-list@bluematt•me
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] BIP 0020: URI Scheme
Date: Sat, 28 Jan 2012 09:23:51 +0100 [thread overview]
Message-ID: <CA+s+GJAtRO_PH1oWmT7KOMeDF2L-YvoWkanURYD=keepCaQ9VQ@mail.gmail.com> (raw)
In-Reply-To: <759be3f8-ca4c-4e36-aac1-b3894dda450d@email.android.com>
[-- Attachment #1: Type: text/plain, Size: 2174 bytes --]
I'd state it this way: a spec needs to be minimally complete
The subset implemented by bitcoin-qt allows description of *all* currently
desirable bitcoin transactions.
The rest of the spec is simply other ways to describe the same = redundancy
In case new transaction types are added, the spec obviously needs to be
extended. But not with a zillion ways to write "send XXX coins to YYY".
Anyway, that's my last word about it.
Wladimir
On Sat, Jan 28, 2012 at 3:12 AM, <bitcoin-list@bluematt•me> wrote:
>
>
> Luke-Jr <luke@dashjr•org> wrote:
>
> >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.
> I'm really not gonna reopen this debate. You made a poll that was worded
> in the most biased way I could think of and still lost. The multiple
> implementations were written but you and I know of no sites that actually
> had links to your version.
>
>
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 3250 bytes --]
next prev parent reply other threads:[~2012-01-28 8:23 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
2012-01-28 2:12 ` bitcoin-list
2012-01-28 8:23 ` Wladimir [this message]
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='CA+s+GJAtRO_PH1oWmT7KOMeDF2L-YvoWkanURYD=keepCaQ9VQ@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=bitcoin-list@bluematt$(echo .)me \
/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