From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Rs90X-0002uM-DD for bitcoin-development@lists.sourceforge.net; Tue, 31 Jan 2012 08:24:05 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of m.gmane.org designates 80.91.229.3 as permitted sender) client-ip=80.91.229.3; envelope-from=gcbd-bitcoin-development@m.gmane.org; helo=plane.gmane.org; Received: from plane.gmane.org ([80.91.229.3]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1Rs90T-0005P0-UH for bitcoin-development@lists.sourceforge.net; Tue, 31 Jan 2012 08:24:05 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Rs90M-0000RP-0F for bitcoin-development@lists.sourceforge.net; Tue, 31 Jan 2012 09:23:54 +0100 Received: from e179074086.adsl.alicedsl.de ([85.179.74.86]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 31 Jan 2012 09:23:53 +0100 Received: from andreas by e179074086.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 31 Jan 2012 09:23:53 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: bitcoin-development@lists.sourceforge.net From: Andreas Schildbach Date: Tue, 31 Jan 2012 09:23:40 +0100 Message-ID: References: <1327881329.49770.YahooMailNeo@web121003.mail.ne1.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: e179074086.adsl.alicedsl.de User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111229 Thunderbird/9.0 In-Reply-To: <1327881329.49770.YahooMailNeo@web121003.mail.ne1.yahoo.com> X-Spam-Score: -0.4 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_HELO_PASS SPF: HELO matches SPF record 1.1 DKIM_ADSP_ALL No valid author signature, domain signs all mail -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1Rs90T-0005P0-UH Subject: Re: [Bitcoin-development] BIP 21 (modification BIP 20) X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 08:24:05 -0000 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