Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1X4qVh-0005KD-Bi for bitcoin-development@lists.sourceforge.net; Wed, 09 Jul 2014 11:58:05 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.174 as permitted sender) client-ip=209.85.214.174; envelope-from=mh.in.england@gmail.com; helo=mail-ob0-f174.google.com; Received: from mail-ob0-f174.google.com ([209.85.214.174]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1X4qVg-0006cK-6J for bitcoin-development@lists.sourceforge.net; Wed, 09 Jul 2014 11:58:05 +0000 Received: by mail-ob0-f174.google.com with SMTP id va2so7901637obc.5 for ; Wed, 09 Jul 2014 04:57:58 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.60.125.195 with SMTP id ms3mr46021922oeb.40.1404907078702; Wed, 09 Jul 2014 04:57:58 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.35.234 with HTTP; Wed, 9 Jul 2014 04:57:58 -0700 (PDT) In-Reply-To: <2098096.PBWFJaSQzq@crushinator> References: <53AC0439.9070501@googlemail.com> <2098096.PBWFJaSQzq@crushinator> Date: Wed, 9 Jul 2014 13:57:58 +0200 X-Google-Sender-Auth: jglE4wEUOmrOkyFhAX1PO-OSI54 Message-ID: From: Mike Hearn To: Matt Whitlock Content-Type: multipart/alternative; boundary=047d7b33cf285e5c4804fdc16bb5 X-Spam-Score: -0.5 (/) 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 (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1X4qVg-0006cK-6J Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Bitcoin Protocol Specification X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2014 11:58:05 -0000 --047d7b33cf285e5c4804fdc16bb5 Content-Type: text/plain; charset=UTF-8 On Tue, Jul 8, 2014 at 10:04 PM, Matt Whitlock wrote: > Is anyone working on a similar specification document for Satoshi's P2P > protocol? I know how blocks and transactions are structured and verified, > but I'm interested in knowing how they're communicated over the network. There's a high level guide here: https://bitcoin.org/en/developer-guide#p2p-network It's not a protocol specification however, more a lay-of-the-land type description. The protocol is not very complicated however. The wiki page describes it adequately. It's basically just a framing mechanism with excessively aggressive checksumming, a version handshake, an inventory mechanism to cut down on bandwidth usage, the alerts, and that's about it. --047d7b33cf285e5c4804fdc16bb5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= ue, Jul 8, 2014 at 10:04 PM, Matt Whitlock <bip@mattwhitlock.name&= gt; wrote:
Is anyone working on a similar specification document for = Satoshi's P2P protocol? =C2=A0I know how blocks and transactions are st= ructured and verified, but I'm interested in knowing how they're co= mmunicated over the network.

There's a high level guide here:


It's not a protocol specification however, more a lay-of-the-land type = description. The protocol is not very complicated however. The wiki page de= scribes it adequately. It's basically just a framing mechanism with exc= essively aggressive checksumming, a version handshake, an inventory mechani= sm to cut down on bandwidth usage, the alerts, and that's about it.
--047d7b33cf285e5c4804fdc16bb5--