From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1X4e3V-0006FS-D1 for bitcoin-development@lists.sourceforge.net; Tue, 08 Jul 2014 22:40:09 +0000 Received: from mail-lb0-f176.google.com ([209.85.217.176]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1X4e3T-0005Qu-Ux for bitcoin-development@lists.sourceforge.net; Tue, 08 Jul 2014 22:40:09 +0000 Received: by mail-lb0-f176.google.com with SMTP id w7so4386738lbi.21 for ; Tue, 08 Jul 2014 15:40:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=pTLO9tM3cJOhixarPIbDbDo2Gbedcc3A6oHdzpIBzUY=; b=NZRJNWqZgt5ENc2aFJ2mVhuYbuG+QJKDJbGzACwyBmBzw0qT5dRT5OEgs0uh709vzZ pTvJanE0Bjy3JXzMcu5onFJNM6GdJkTPh5gSDaqYDOIq9zGRCsyXKU2x54fobbONznsx 51fD3sSkSWrdVtTQ6qTFaXSO6XRA1j2mdVXlB+BdL3tQt+kqlRKiudMVIbtUDs0mOoUD ez3KWYcBNosmbIkyffdQkFqU2g+Z6UHpJDbJ6ESPbBpHReQiIaCgKaq+OtGZQ5NGBbd9 4w6wQJvQzfZNAsrbw48GeDdUn6uyFHvM4dshjHsQzO0lAD7ynH9a239o66QFrfCq47hB KlzQ== X-Gm-Message-State: ALoCoQkIUwlVZyUscBXky3605e3rxp1xNfvxrOetUb085Coy5Ye3JyDE/eKPd/TiDz7bthbi7Jjy MIME-Version: 1.0 X-Received: by 10.112.17.102 with SMTP id n6mr28439401lbd.39.1404859201143; Tue, 08 Jul 2014 15:40:01 -0700 (PDT) Received: by 10.112.185.6 with HTTP; Tue, 8 Jul 2014 15:40:00 -0700 (PDT) X-Originating-IP: [207.134.53.206] In-Reply-To: <2098096.PBWFJaSQzq@crushinator> References: <53AC0439.9070501@googlemail.com> <2098096.PBWFJaSQzq@crushinator> Date: Wed, 9 Jul 2014 00:40:00 +0200 Message-ID: From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= To: Matt Whitlock Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1X4e3T-0005Qu-Ux Cc: bitcoin-development@lists.sourceforge.net 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: Tue, 08 Jul 2014 22:40:09 -0000 There's this (not sure how complete it is): https://en.bitcoin.it/wiki/Protocol_specification Also there's a good introduction to technical details here: https://bitcointalk.org/index.php?topic=3D375524.0 I hope that is useful. On 7/8/14, 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. > > -------------------------------------------------------------------------= ----- > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Editi= on > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --=20 Jorge Tim=C3=B3n