Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <michaelmclees@gmail.com>) id 1YJUcl-0000to-Rr
	for bitcoin-development@lists.sourceforge.net;
	Thu, 05 Feb 2015 22:10:11 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.217.176 as permitted sender)
	client-ip=209.85.217.176; envelope-from=michaelmclees@gmail.com;
	helo=mail-lb0-f176.google.com; 
Received: from mail-lb0-f176.google.com ([209.85.217.176])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YJUck-000064-16
	for bitcoin-development@lists.sourceforge.net;
	Thu, 05 Feb 2015 22:10:11 +0000
Received: by mail-lb0-f176.google.com with SMTP id w7so7878934lbi.7
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 05 Feb 2015 14:10:03 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.112.114.230 with SMTP id jj6mr254355lbb.112.1423174203751;
	Thu, 05 Feb 2015 14:10:03 -0800 (PST)
Sender: michaelmclees@gmail.com
Received: by 10.25.143.79 with HTTP; Thu, 5 Feb 2015 14:10:03 -0800 (PST)
Date: Thu, 5 Feb 2015 16:10:03 -0600
X-Google-Sender-Auth: nl_AI1hnyAEmPDEf7qHZZ2-pNL4
Message-ID: <CALZ14xnKNjw4VeLME08Fk696cJ9k1LRQAWHbV5_29ViN-BV-VA@mail.gmail.com>
From: Michael McLees <michael.nakapay@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=001a1135e748de431f050e5e90ef
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
	(michaelmclees[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: 1YJUck-000064-16
Subject: [Bitcoin-development] Nakapay
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: Thu, 05 Feb 2015 22:10:11 -0000

--001a1135e748de431f050e5e90ef
Content-Type: text/plain; charset=UTF-8

All this talk about URI's, bluetooth, P2P wireless transmissions, etc...
Ultimately, it is about a better user interface. Guys, I've already made
Bitcoin invoicing and payments exceptionally easy with Nakapay. Now if only
there's a wallet developer out there who would integrate it ...

--001a1135e748de431f050e5e90ef
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">All this talk about URI&#39;s, bluetooth, P2P wireless tra=
nsmissions, etc... Ultimately, it is about a better user interface. Guys, I=
&#39;ve already made Bitcoin invoicing and payments exceptionally easy with=
 Nakapay. Now if only there&#39;s a wallet developer out there who would in=
tegrate it ...
</div>

--001a1135e748de431f050e5e90ef--