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-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YQHt6-0001Du-I5 for bitcoin-development@lists.sourceforge.net; Tue, 24 Feb 2015 15:59:08 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.181 as permitted sender) client-ip=74.125.82.181; envelope-from=oleganza@gmail.com; helo=mail-we0-f181.google.com; Received: from mail-we0-f181.google.com ([74.125.82.181]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YQHt4-0000rY-KY for bitcoin-development@lists.sourceforge.net; Tue, 24 Feb 2015 15:59:08 +0000 Received: by wesu56 with SMTP id u56so26066849wes.10 for ; Tue, 24 Feb 2015 07:59:00 -0800 (PST) X-Received: by 10.180.106.103 with SMTP id gt7mr31680082wib.59.1424793540569; Tue, 24 Feb 2015 07:59:00 -0800 (PST) Received: from ?IPv6:2a01:e35:8a2c:a630:e173:16cf:defa:f3e? ([2a01:e35:8a2c:a630:e173:16cf:defa:f3e]) by mx.google.com with ESMTPSA id y3sm20959404wju.14.2015.02.24.07.58.57 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 24 Feb 2015 07:58:59 -0800 (PST) From: Oleg Andreev Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <771EF431-6644-4BE4-B39C-CA73CFC18DB4@gmail.com> Date: Tue, 24 Feb 2015 16:58:57 +0100 To: Bitcoin Dev Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) 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 (oleganza[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: 1YQHt4-0000rY-KY Subject: [Bitcoin-development] Providing Payment Request within URI 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, 24 Feb 2015 15:59:08 -0000 Hi, I wonder if there is a standard way to put Payment Request data into = bitcoin: URI or directly into QR code. The goal is to allow device to = generate a multi-output payment request on its own, without relying on = the server and x509 certificates. When scanned via QR code from, say, = POS, it's pretty secure, so no additional authentication needed. I'd like something like this:=20 bitcoin:?r=3Ddata:// If there's no standard for that, would it be a good idea to extend BIP72 = this way?=