blob: 39893ed7b82c61d126c0ee52316c34c0e8c1d36d (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <naveen.garg@gmail.com>) id 1Xd2fF-0003sW-Tt
for Bitcoin-development@lists.sourceforge.net;
Sat, 11 Oct 2014 19:49:18 +0000
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;
Received: from mail-ig0-f171.google.com ([209.85.213.171])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Xd2fF-0004FE-5d
for Bitcoin-development@lists.sourceforge.net;
Sat, 11 Oct 2014 19:49:17 +0000
Received: by mail-ig0-f171.google.com with SMTP id h15so6455145igd.10
for <Bitcoin-development@lists.sourceforge.net>;
Sat, 11 Oct 2014 12:49:11 -0700 (PDT)
X-Received: by 10.50.18.50 with SMTP id t18mr18167978igd.4.1413056951681;
Sat, 11 Oct 2014 12:49:11 -0700 (PDT)
Received: from [10.0.1.4] ([50.240.247.126])
by mx.google.com with ESMTPSA id mk5sm4755442igb.15.2014.10.11.12.49.10
for <Bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Sat, 11 Oct 2014 12:49:11 -0700 (PDT)
References: <3973916F-EBBC-41F1-8B38-65FA8379CF2B@gmail.com>
From: Naveen Garg <naveen.garg@gmail.com>
Content-Type: text/plain;
charset=us-ascii
X-Mailer: iPhone Mail (10B350)
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)
X-Spam-Score: -1.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
(naveen.garg[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-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: 1Xd2fF-0004FE-5d
Subject: [Bitcoin-development] Distributed anonymous bitcoin client using
your friendly government postal service
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: Sat, 11 Oct 2014 19:49:18 -0000
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.
|
