From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VfQ9Z-0008J4-Js for bitcoin-development@lists.sourceforge.net; Sun, 10 Nov 2013 08:13:53 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.50 as permitted sender) client-ip=209.85.214.50; envelope-from=laanwj@gmail.com; helo=mail-bk0-f50.google.com; Received: from mail-bk0-f50.google.com ([209.85.214.50]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VfQ9Y-00071f-Pu for bitcoin-development@lists.sourceforge.net; Sun, 10 Nov 2013 08:13:53 +0000 Received: by mail-bk0-f50.google.com with SMTP id d7so474248bkh.23 for ; Sun, 10 Nov 2013 00:13:46 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.205.74.69 with SMTP id yv5mr235053bkb.35.1384071226327; Sun, 10 Nov 2013 00:13:46 -0800 (PST) Received: by 10.204.71.206 with HTTP; Sun, 10 Nov 2013 00:13:46 -0800 (PST) In-Reply-To: References: Date: Sun, 10 Nov 2013 09:13:46 +0100 Message-ID: From: Wladimir To: Chris Evans Content-Type: multipart/alternative; boundary=f46d0415595aca2c4504eace3187 X-Spam-Score: -0.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 (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -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: 1VfQ9Y-00071f-Pu Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] idea 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: Sun, 10 Nov 2013 08:13:53 -0000 --f46d0415595aca2c4504eace3187 Content-Type: text/plain; charset=UTF-8 On Sat, Nov 9, 2013 at 9:16 PM, Chris Evans wrote: > maybe add an optional note field to transaction so the receiver knows who > sent the > btc > This has been discussed many times. But in any case: If you encounter this as a problem it means you are re-using addresses, which is discouraged for good reasons. Otherwise, when someone wants to send you BTC they need to request a new receiving address from you. Along with this request they can also send a message, over whatever channel is used to negotiate the payment. If you're just posting a static bitcoin address somewhere for donations, consider it an anonymous (wel, pseudonymous) gift jar. Regards, Wladimir --f46d0415595aca2c4504eace3187 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Sat, Nov 9, 2013 at 9:16 PM, Chris Evans <aa= xiomfinity@gmail.com> wrote:
maybe add an optional note fiel= d to transaction so the receiver knows who sent the
btc

This has been discuss= ed many times. But in any case: If you encounter this as a problem it means= you are re-using addresses, which is discouraged for good reasons.

Otherwise, when someone wants to send you BTC they need= to request a new receiving address from you. Along with this request they = can also send a message, over whatever channel is used to negotiate the pay= ment.

If you're just posting a static bitcoin address som= ewhere for donations, consider it an anonymous (wel, pseudonymous) gift jar= .

Regards,
Wladimir

--f46d0415595aca2c4504eace3187--