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
|
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 <mcqueenorama@gmail.com>) id 1RBJrr-00018Y-UI
for Bitcoin-development@lists.sourceforge.net;
Wed, 05 Oct 2011 05:18:07 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.210.175 as permitted sender)
client-ip=209.85.210.175; envelope-from=mcqueenorama@gmail.com;
helo=mail-iy0-f175.google.com;
Received: from mail-iy0-f175.google.com ([209.85.210.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RBJrr-0005EX-8O
for Bitcoin-development@lists.sourceforge.net;
Wed, 05 Oct 2011 05:18:07 +0000
Received: by iadx2 with SMTP id x2so1988737iad.34
for <Bitcoin-development@lists.sourceforge.net>;
Tue, 04 Oct 2011 22:18:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.82.12 with SMTP id z12mr3707502ibk.36.1317791881991; Tue,
04 Oct 2011 22:18:01 -0700 (PDT)
Received: by 10.231.148.141 with HTTP; Tue, 4 Oct 2011 22:18:01 -0700 (PDT)
Date: Tue, 4 Oct 2011 22:18:01 -0700
Message-ID: <CAPfzCrS87dJwHC=HQAVcfm8Fm9r5LdENg5s9JUnLuZr+sgh+jg@mail.gmail.com>
From: Brian McQueen <mcqueenorama@gmail.com>
To: Bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=ISO-8859-1
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
(mcqueenorama[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
0.0 T_TO_NO_BRKTS_FREEMAIL To: misformatted and free email service
-0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RBJrr-0005EX-8O
Subject: [Bitcoin-development] Transaction Delivery and Storage
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, 05 Oct 2011 05:18:08 -0000
I see the Contracts wiki page talking about,
1) Transactions passed around outside the P2P network ...
2) ... transaction ... not broadcast right away
How are transactions created, stored and transmitted? How will they
be brought back into the P2P network once they are out?
B
--
Make a Small Loan, Make a Big Difference - Check out Kiva.org to Learn How!
|
