Bitcoin Institute

A bitcoin UDP P2P protocol extension

1 messages BitcoinTalk Jeff Garzik March 23, 2013 — March 23, 2013

Here is a rough draft implementation of a UDP P2P protocol extension
for bitcoin:

     https://github.com/jgarzik/bitcoin/tree/udp
     http://yyz.us/bitcoin/udp-v0.patch

Protocol specification (such that it is):

  • UDP, bound to same port as TCP P2P (normally 8333)
  • Active, simultaneous TCP P2P connection required (useful against DoS and other attacks)
  • Same message format as TCP P2P, same pchMessageStart conventions, etc. (my CNetMessage pull req would be helpful here)
  • Multiple P2P messages per UDP packet permitted
  • Max UDP packet size 100*1024 bytes
  • Advertises NODE_UDP in nServices
  • New “getudpcook” TCP P2P command returns a “udpcook” message, containing a yummy cookie
  • UDP P2P commands “inv”, “tx” and “addr” are handled as if received via TCP
  • UDP P2P command “udpsub” sets a mask, that subscribes to one or more data broadcasts.
  • When USM_INV_BCAST mask bit is set, receive “inv” messages via UDP rather than TCP.

Project and design goals (or, why do this?):

  • It is theorized that UDP may be useful for some messages we broadcast throughout the network
  • A productive discussion STARTS with code, otherwise discussion continues forever.
  • Investigate improving “inv” relay speed
  • Investigate unconditional “tx” broadcasting via UDP, as “inv” alternative, for small tx’s.
  • Investigate improving block relay speed (or perhaps block header relay speed)
  • Open up new design avenues, for P2P patterns more suited to UDP than TCP in general.

It must be emphasize that this is supposed to be a starting point, not a set-in-stone requirement that This Is How The Protocol Must Look.  I don’t think we will know how the UDP protocol should look until after testing and experimentation, or even if it is a good idea at all.