Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.171 as permitted sender)
	client-ip=209.85.213.171; envelope-from=naveen.garg@gmail.com;
	helo=mail-ig0-f171.google.com; 
References: <3973916F-EBBC-41F1-8B38-65FA8379CF2B@gmail.com>
From: Naveen Garg <naveen.garg@gmail.com>
Content-Type: text/plain;
	charset=us-ascii
Message-Id: <052D6026-7B99-4CC0-A5E2-820736A1753F@gmail.com>
Date: Sat, 11 Oct 2014 14:49:11 -0500
To: "Bitcoin-development@lists.sourceforge.net"
	<Bitcoin-development@lists.sourceforge.net>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: [Bitcoin-development] Distributed anonymous bitcoin client using
	your friendly government postal service
Precedence: list

Make a transaction with two outputs.  Output A is your payee.  Output B is a=
 fee to whoever transmits the transaction to the network.  Sign and print th=
e transaction, along with private key controlling address of output B.  Put i=
t in the mail with instructions to 1 or more greedy people who don't know yo=
u.  =20

Does namecoin allow mixing outputs for name registration with pay to hash ou=
tputs ?  If so, you could use namecoin for anonymous publishing via post.  O=
r just make output A in bitcoin scripted with op_return if its a 40byte twee=
t.