From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gmaxwell@gmail.com>) id 1RBJxM-0005Gx-Qh
	for Bitcoin-development@lists.sourceforge.net;
	Wed, 05 Oct 2011 05:23:48 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.47 as permitted sender)
	client-ip=209.85.216.47; envelope-from=gmaxwell@gmail.com;
	helo=mail-qw0-f47.google.com; 
Received: from mail-qw0-f47.google.com ([209.85.216.47])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1RBJxM-0005Pl-4M
	for Bitcoin-development@lists.sourceforge.net;
	Wed, 05 Oct 2011 05:23:48 +0000
Received: by qadc1 with SMTP id c1so1280724qad.34
	for <Bitcoin-development@lists.sourceforge.net>;
	Tue, 04 Oct 2011 22:23:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.73.106 with SMTP id p42mr1642490qcj.185.1317792222409;
	Tue, 04 Oct 2011 22:23:42 -0700 (PDT)
Received: by 10.229.214.144 with HTTP; Tue, 4 Oct 2011 22:23:42 -0700 (PDT)
In-Reply-To: <CAPfzCrS87dJwHC=HQAVcfm8Fm9r5LdENg5s9JUnLuZr+sgh+jg@mail.gmail.com>
References: <CAPfzCrS87dJwHC=HQAVcfm8Fm9r5LdENg5s9JUnLuZr+sgh+jg@mail.gmail.com>
Date: Wed, 5 Oct 2011 01:23:42 -0400
Message-ID: <CAAS2fgTU16E08n7QtDDX0+G8C1q5mXHv14gXxJmaXR7+_vCroA@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Brian McQueen <mcqueenorama@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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
	(gmaxwell[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 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RBJxM-0005Pl-4M
Cc: Bitcoin-development@lists.sourceforge.net
Subject: Re: [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:23:48 -0000

On Wed, Oct 5, 2011 at 1:18 AM, Brian McQueen <mcqueenorama@gmail.com> wrot=
e:
> 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? =C2=A0How will they
> be brought back into the P2P network once they are out?

However you want. The P2P network isn't all the essential to bitcoin.
With patches you can import and export transactions to text from a
regular client.

The distributed algorithm and the block chain are far more essential
to bitcoin than the p2p network is, you could interconnect all bitcoin
systems with morse code operators running spark gap transmitters with
nary an IP packet in sight and it would still be bitcoin.