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-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RrnJ5-0005h2-25 for bitcoin-development@lists.sourceforge.net; Mon, 30 Jan 2012 09:13:47 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.210.47 as permitted sender) client-ip=209.85.210.47; envelope-from=laanwj@gmail.com; helo=mail-pz0-f47.google.com; Received: from mail-pz0-f47.google.com ([209.85.210.47]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1RrnJ1-0003T7-3P for bitcoin-development@lists.sourceforge.net; Mon, 30 Jan 2012 09:13:47 +0000 Received: by dakf10 with SMTP id f10so3603365dak.34 for ; Mon, 30 Jan 2012 01:13:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.68.189.102 with SMTP id gh6mr40207002pbc.4.1327914817119; Mon, 30 Jan 2012 01:13:37 -0800 (PST) Received: by 10.143.8.11 with HTTP; Mon, 30 Jan 2012 01:13:37 -0800 (PST) In-Reply-To: <1327881329.49770.YahooMailNeo@web121003.mail.ne1.yahoo.com> References: <1327881329.49770.YahooMailNeo@web121003.mail.ne1.yahoo.com> Date: Mon, 30 Jan 2012 10:13:37 +0100 Message-ID: From: Wladimir To: Amir Taaki Content-Type: multipart/alternative; boundary=e89a8ff1bfb0f7674e04b7bb42c3 X-Spam-Score: -0.6 (/) 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1RrnJ1-0003T7-3P Cc: "bitcoin-development@lists.sourceforge.net" 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: Mon, 30 Jan 2012 09:13:47 -0000 --e89a8ff1bfb0f7674e04b7bb42c3 Content-Type: text/plain; charset=UTF-8 I agree with BIP 0021 Wladimir On Mon, Jan 30, 2012 at 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 scheme 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 > > --e89a8ff1bfb0f7674e04b7bb42c3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I agree with BIP 0021

Wladimir