From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1V7Bgx-0007R2-82 for bitcoin-development@lists.sourceforge.net; Wed, 07 Aug 2013 21:54:51 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.223.181 as permitted sender) client-ip=209.85.223.181; envelope-from=pieter.wuille@gmail.com; helo=mail-ie0-f181.google.com; Received: from mail-ie0-f181.google.com ([209.85.223.181]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1V7Bgw-0006lQ-Aw for bitcoin-development@lists.sourceforge.net; Wed, 07 Aug 2013 21:54:51 +0000 Received: by mail-ie0-f181.google.com with SMTP id x14so469946ief.26 for ; Wed, 07 Aug 2013 14:54:45 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.124.10 with SMTP id me10mr646900igb.40.1375912484939; Wed, 07 Aug 2013 14:54:44 -0700 (PDT) Received: by 10.50.73.74 with HTTP; Wed, 7 Aug 2013 14:54:44 -0700 (PDT) In-Reply-To: <20130807214757.GA45156@giles.gnomon.org.uk> References: <20130807214757.GA45156@giles.gnomon.org.uk> Date: Wed, 7 Aug 2013 23:54:44 +0200 Message-ID: From: Pieter Wuille To: Roy Badami Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.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 (pieter.wuille[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -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: 1V7Bgw-0006lQ-Aw Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Payment Protocol: BIP 70, 71, 72 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: Wed, 07 Aug 2013 21:54:51 -0000 I see payment URIs rather as a replacement for bitcoin: URI rather than an extension. It solves everything they did in a much cleaner way, Given that bitcoin: have gotten some traction, we probably want to reuse the moniker, but replace the rest entirely. In other words, if a request is specified, nothing else should be. There is just no useful way to combine them either - payments generalize destinations to arbitrary scripts, messages are handled inline, amounts are defined inline. And if you want to rely on the payment infrastructure to work, you cannot risk people using the old-style static address in the URI. On Wed, Aug 7, 2013 at 11:47 PM, Roy Badami wrote: > Very brief comment on BIP 72: > > I wonder if there should be some discussion included in the > specification as to how the BIP 21 amount, message and label > parameters should be processed when the payment protocol is used. > > Presumably amount should be completely ignored? But is the total > amount requestd by the PaymentRequest required to match the amount > parameter (when present)? Is the client permitted to complain if they > don't? > > And what about message? Presumably the memo from PaymentDetails > should take precedence, but if it's not present, and message is? > > I think this is an area perhaps more suited to SHOULDs and MAYs rather > than MUSTs, but it is probably worthy of mention... > > roy > > ------------------------------------------------------------------------------ > Get 100% visibility into Java/.NET code with AppDynamics Lite! > It's a free troubleshooting tool designed for production. > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development