Mike Hearn [ARCHIVE] on Nostr: 📅 Original date posted:2014-07-09 📝 Original message:On Tue, Jul 8, 2014 at ...
📅 Original date posted:2014-07-09
📝 Original message:On Tue, Jul 8, 2014 at 10:04 PM, Matt Whitlock <bip at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140709/b2fb0530/attachment.html>;
📝 Original message:On Tue, Jul 8, 2014 at 10:04 PM, Matt Whitlock <bip at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140709/b2fb0530/attachment.html>;