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-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Td95J-0004Yd-9e for bitcoin-development@lists.sourceforge.net; Tue, 27 Nov 2012 00:31:33 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1Td95I-0004qU-It for bitcoin-development@lists.sourceforge.net; Tue, 27 Nov 2012 00:31:33 +0000 Received: from ishibashi.localnet (unknown [173.170.188.216]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 906D527A296E; Tue, 27 Nov 2012 00:31:24 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Tue, 27 Nov 2012 00:31:16 +0000 User-Agent: KMail/1.13.7 (Linux/3.5.4-gentoo; KDE/4.8.5; x86_64; ; ) References: In-Reply-To: X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201211270031.18080.luke@dashjr.org> X-Spam-Score: -0.4 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.4 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 AWL AWL: From: address is in the auto white-list X-Headers-End: 1Td95I-0004qU-It 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:31:33 -0000 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. Luke