From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Td9BA-0004Rj-J5 for bitcoin-development@lists.sourceforge.net; Tue, 27 Nov 2012 00:37:36 +0000 X-ACL-Warn: Received: from mail-gh0-f175.google.com ([209.85.160.175]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Td9B9-0003hQ-G1 for bitcoin-development@lists.sourceforge.net; Tue, 27 Nov 2012 00:37:36 +0000 Received: by mail-gh0-f175.google.com with SMTP id z2so1218085ghb.34 for ; Mon, 26 Nov 2012 16:37:29 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=hyL0IsroZRduyq0pbiL1Qy5racxPSl5quCLUFoHTzH0=; b=oWfd7i4CGxwyO6hmoP4qiwd4blifHo44rSTe0LRveSHhq6Q3imijOPswY3CeBZpkVc ztPgh5OExbfXguljw1//R1pTNJe2JlnZCaslB6AVgNLxzVUS+21ffxJBMgeLSo4kXpIx e+hMmrwJMd+QZa3tdzu6n2ijnKtUmtoUQRlcg/Vr0kBW01BXFFgBCN34gOpxWZkNYu4u /MnlypSsDHF35GuGi1WOq2MT0eh6kI7IGNH3zwHoyCALiMAAMm6SDnp4Hv6qSlOVxOY5 xTbQ66rqsozs15dw3rHl/ZNvlTGB2nw9ye5t9YXZfSerwfnmVwLLdQ9/k0b5IB3hf+q2 WZGw== MIME-Version: 1.0 Received: by 10.236.92.172 with SMTP id j32mr13489781yhf.37.1353976649625; Mon, 26 Nov 2012 16:37:29 -0800 (PST) Received: by 10.101.69.3 with HTTP; Mon, 26 Nov 2012 16:37:29 -0800 (PST) In-Reply-To: <201211270031.18080.luke@dashjr.org> References: <201211270031.18080.luke@dashjr.org> Date: Mon, 26 Nov 2012 16:37:29 -0800 Message-ID: From: Rick Wesson To: Luke-Jr Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkNkbmLpak9p6PpdumxmbYFUakMBlPNp5c5PYjIR1YQAb7GOzDMjTajaxd/AsO6r/3+kqMU X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1Td9B9-0003hQ-G1 Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Payment Protocol Proposal: Invoices/Payments/Receipts 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, 27 Nov 2012 00:37:36 -0000 On Mon, Nov 26, 2012 at 4:31 PM, Luke-Jr wrote: > On Tuesday, November 27, 2012 12:02:42 AM Rick Wesson wrote: >> Another nifty thing is that it can associate a cert to a domain and a >> payment address, if one were to put said address in the DNS :) >> >> Now I am sure the majority of the bitcoin user-base desires anonymity, >> but as a merchant I would like to be knowable and wouldn't mind it if >> my identity and those of my transactions were "known" and associated >> both with my domains and x.509 cert. In most commercial transactions >> (which include many of those that leverage invoices) identity is >> important, at least for the merchant. > > Anonymity isn't a feature we claim to have, nor a goal of the project for the > most part. Using a single Bitcoin address has many problems besides non- > anonymity: your customers are denied basic privacy and there is no good way to > guarantee the user who says he paid you really did (since transaction ids are > public record, anyone can claim they sent it). > > In short, it is for the most part considered a rule to always use a unique > address per transaction or at least per customer. putting payment addresses in the DNS does not require that only a single address be used. This is an assumption and a possible use case, but there is no requirement that payment addresses must be 1:1 associated. -rick