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; 
MIME-Version: 1.0
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
Cc: Bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Transaction Delivery and Storage
Precedence: list

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.