From: Mike Hearn <mike@plan99•net>
To: Matt Whitlock <bip@mattwhitlock•name>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Protocol Specification
Date: Wed, 9 Jul 2014 13:57:58 +0200 [thread overview]
Message-ID: <CANEZrP1uuPReuOR=0PS5bff43umk-PP9OgYd-MTycFLsqnTp9g@mail.gmail.com> (raw)
In-Reply-To: <2098096.PBWFJaSQzq@crushinator>
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
On Tue, Jul 8, 2014 at 10:04 PM, Matt Whitlock <bip@mattwhitlock•name>
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.
[-- Attachment #2: Type: text/html, Size: 1270 bytes --]
next prev parent reply other threads:[~2014-07-09 11:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 11:30 Krzysztof Okupski
2014-07-03 1:21 ` Isidor Zeuner
[not found] ` <CANVdSAqEyqavSHea3uhzVWGKQU0UHGZDVqEiF3Ox2XkhwM=zpA@mail.gmail.com>
2014-07-07 17:57 ` JMOlmos GMail
2014-07-08 15:29 ` Chris D'Costa
2014-07-08 20:04 ` Matt Whitlock
2014-07-08 21:08 ` Aaron Voisine
2014-07-08 22:40 ` Jorge Timón
2014-07-09 11:57 ` Mike Hearn [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-14 14:44 Krzysztof Okupski
2014-07-14 17:16 ` Jeff Garzik
2014-07-14 9:54 Krzysztof Okupski
2014-07-14 10:41 ` sickpig
2014-07-14 11:26 ` Mike Hearn
2014-07-14 11:41 ` Wladimir
2014-07-14 11:49 ` Mike Hearn
2014-07-14 12:25 ` sickpig
2014-07-14 12:37 ` Mike Hearn
2014-07-14 20:51 ` sickpig
2014-07-09 9:34 Krzysztof Okupski
2014-05-18 13:35 Krzysztof Okupski
2014-05-18 14:38 ` Adam Back
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANEZrP1uuPReuOR=0PS5bff43umk-PP9OgYd-MTycFLsqnTp9g@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bip@mattwhitlock$(echo .)name \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox