From: Naveen Garg <naveen.garg@gmail•com>
To: "Bitcoin-development@lists•sourceforge.net"
<Bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Distributed anonymous bitcoin client using your friendly government postal service
Date: Sat, 11 Oct 2014 14:49:11 -0500 [thread overview]
Message-ID: <052D6026-7B99-4CC0-A5E2-820736A1753F@gmail.com> (raw)
In-Reply-To: <3973916F-EBBC-41F1-8B38-65FA8379CF2B@gmail.com>
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 the transaction, along with private key controlling address of output B. Put it in the mail with instructions to 1 or more greedy people who don't know you.
Does namecoin allow mixing outputs for name registration with pay to hash outputs ? If so, you could use namecoin for anonymous publishing via post. Or just make output A in bitcoin scripted with op_return if its a 40byte tweet.
parent reply other threads:[~2014-10-11 19:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <3973916F-EBBC-41F1-8B38-65FA8379CF2B@gmail.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=052D6026-7B99-4CC0-A5E2-820736A1753F@gmail.com \
--to=naveen.garg@gmail$(echo .)com \
--cc=Bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox