Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <gavinandresen@gmail.com>) id 1V7uaS-0002aq-I4 for bitcoin-development@lists.sourceforge.net; Fri, 09 Aug 2013 21:51:08 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.174 as permitted sender) client-ip=74.125.82.174; envelope-from=gavinandresen@gmail.com; helo=mail-we0-f174.google.com; Received: from mail-we0-f174.google.com ([74.125.82.174]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1V7uaQ-0005WZ-PU for bitcoin-development@lists.sourceforge.net; Fri, 09 Aug 2013 21:51:08 +0000 Received: by mail-we0-f174.google.com with SMTP id q54so3944514wes.19 for <bitcoin-development@lists.sourceforge.net>; Fri, 09 Aug 2013 14:51:00 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.234.100 with SMTP id ud4mr7341149wjc.44.1376085060612; Fri, 09 Aug 2013 14:51:00 -0700 (PDT) Received: by 10.194.82.198 with HTTP; Fri, 9 Aug 2013 14:51:00 -0700 (PDT) In-Reply-To: <52052D8F.90706@gmail.com> References: <5AC3FA1D9B1F4FA0A2FE9A67333642B5@LAPTOPAIR> <51C21035.9080407@gmail.com> <53E406CF0D93498DAECAAE061555B7C9@LAPTOPAIR> <51C234FA.5030909@gmail.com> <9600E3D1DDC24D1391C1E4433F71684D@LAPTOPAIR> <CANEZrP3ZcQEPOPrO_O2-tdLZUSezj1nbhtVFt1e77KEwzhfZ-A@mail.gmail.com> <51CB08EE.1050403@gmail.com> <52052D8F.90706@gmail.com> Date: Sat, 10 Aug 2013 07:51:00 +1000 Message-ID: <CABsx9T2unkmFczDen0mq+L1J5TOTzSuvsvuQ0-e4uRBM1bp+Ew@mail.gmail.com> From: Gavin Andresen <gavinandresen@gmail.com> To: Alan Reiner <etotheipi@gmail.com> 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 (gavinandresen[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: 1V7uaQ-0005WZ-PU Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Optional "wallet-linkable" address format (Re-request) X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Fri, 09 Aug 2013 21:51:08 -0000 As Mike said: the payment protocol doesn't use bitcoin addresses under the covers. It is also designed to be easily extensible, so if you want the server to send the wallet software a public key and multiplier, then add "publickey" and "multiplier" optional fields to the PaymentDetails (or maybe Output) message. -- -- Gavin Andresen