public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Andreas Schildbach <andreas@schildbach.de>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BIP 21 (modification BIP 20)
Date: Tue, 31 Jan 2012 09:23:40 +0100	[thread overview]
Message-ID: <jg88ed$i85$1@dough.gmane.org> (raw)
In-Reply-To: <1327881329.49770.YahooMailNeo@web121003.mail.ne1.yahoo.com>

Generally I prefer BIP 21 over BIP 20.

I'm neutral on the 'send' parameter - present in both BIPs - which I
don't understand. I think a practical usecase should be given in the BIP.

Also, the 'version' parameter is unclear. What does it mean? Is an oder
defined on versions (1.0b > 1.0)? Why is it an ";" parameter rather than
a normal "&" parameter?


On 01/30/2012 12:55 AM, Amir Taaki wrote:
> Matt Corallo posted a modification of BIP 20 in an earlier email and I
> asked him if he wanted to become the champion of that BIP he submitted.
> 
> It is a modification of BIP 20 sans the alternative non-decimal number
> stuff.
> 
> https://en.bitcoin.it/wiki/BIP_0021
> 
> Right now, I will ask the GUI client implementations like MultiBit or
> Bitcoin-Qt, not different codebases like BitCoinJ or libbitcoin if they
> support BIP 20 or BIP 21. Feel free to raise any objections.
> 
> More weight will be given to GUIs with actual URI sche me
> implementations and it's good to have a general consensus.
> 
> 
> ------------------------------------------------------------------------------
> 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





  parent reply	other threads:[~2012-01-31  8:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-29 23:55 [Bitcoin-development] BIP 21 (modification BIP 20) Amir Taaki
2012-01-30  9:13 ` Wladimir
2012-01-31  8:23 ` Andreas Schildbach [this message]
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
2012-01-30 18:07 thomasV1
2012-01-30 18:44 ` Luke-Jr
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
2012-01-31 10:39 [Bitcoin-development] BIP 21 (modification BIP 20)] 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='jg88ed$i85$1@dough.gmane.org' \
    --to=andreas@schildbach.de \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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