Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <memwallet.info@gmail.com>) id 1XMRYj-0002xY-SE
	for bitcoin-development@lists.sourceforge.net;
	Wed, 27 Aug 2014 00:57:57 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.194 as permitted sender)
	client-ip=209.85.213.194; envelope-from=memwallet.info@gmail.com;
	helo=mail-ig0-f194.google.com; 
Received: from mail-ig0-f194.google.com ([209.85.213.194])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1XMRYj-0003yU-3F
	for bitcoin-development@lists.sourceforge.net;
	Wed, 27 Aug 2014 00:57:57 +0000
Received: by mail-ig0-f194.google.com with SMTP id r2so1528032igi.1
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 26 Aug 2014 17:57:51 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.73.198 with SMTP id n6mr26400371igv.11.1409101071799;
	Tue, 26 Aug 2014 17:57:51 -0700 (PDT)
Received: by 10.107.157.131 with HTTP; Tue, 26 Aug 2014 17:57:51 -0700 (PDT)
Date: Tue, 26 Aug 2014 20:57:51 -0400
Message-ID: <CAKzHBKndU4nHHK=h4=G+hG_t_c77h0DHpeEUK+Kk9q2CsRHEcQ@mail.gmail.com>
From: Mem Wallet <memwallet.info@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=089e011839a6d65c53050191e887
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
	(memwallet.info[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: 1XMRYj-0003yU-3F
Subject: [Bitcoin-development] standardize on bitcoin signed ecies ?
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: Wed, 27 Aug 2014 00:57:58 -0000

--089e011839a6d65c53050191e887
Content-Type: text/plain; charset=UTF-8

Does anyone see a value in a standardized PGP-style message,
which would allow someone performing a bitcoin transaction to
send signed encrypted messages using only public and private
bitcoin keys ?

I'd like to propose a signed encrypted message protocol, in case
someone see's value in encoding such a thing into a BIP.

--089e011839a6d65c53050191e887
Content-Type: text/html; charset=UTF-8

<div dir="ltr"><div><div><div><div><br></div>Does anyone see a value in a standardized PGP-style message,<br>which would allow someone performing a bitcoin transaction to<br></div>send signed encrypted messages using only public and private<br>
bitcoin keys ?<br><br></div>I&#39;d like to propose a signed encrypted message protocol, in case<br></div>someone see&#39;s value in encoding such a thing into a BIP.<br><div><br></div></div>

--089e011839a6d65c53050191e887--