Entries tagged with this topic. Spans across types and sources — explore connections between people, events, and themes.
10 entries
How Bitcoin nodes find each other, exchange transactions and blocks, and resist network-level attacks across the P2P gossip layer.
Satoshi tells Finney that he cannot receive incoming connections from his location, revealing an operational constraint in the earliest days of the Bitcoin network.
Nicholas Bohm, a retired British solicitor and early Bitcoin user, writes to Satoshi that after installing a new router, his Bitcoin client can no longer connect to the network.
Satoshi advises Bohm to forward port 8333 on his new router so his Bitcoin node can receive incoming connections, explaining that without inbound-capable nodes online, the network fails to function.
Bohm reports to Satoshi that Bitcoin has failed to establish any connections for over a day, despite restarts. He had been maintaining 3-5 node connections prior to July 15th.
Satoshi's candid reply to Bohm's connectivity issue, admitting there may be no other nodes running at that moment. He encourages Bohm to keep his server online so new users have someone to connect to.
Satoshi follows up that he is connected to IP 70.113.114.209 and notes Bohm may have an outgoing-connection issue if not. The IP was later identified as likely Dustin Trammell's in Austin, Texas.
The COPA v Wright record revealed that Nicholas Bohm — previously known only for a January 2009 bitcoin-list bug report — also exchanged a private series of troubleshooting emails with Satoshi.
Satoshi confirms Bitcoin is fully operational and offers to send coins to anyone who tries the software, in response to Michel Bauwens' question on the P2P Research mailing list.
In a podcast interview, security researcher Dustin Trammell (Druid) describes being possibly the second node on the Bitcoin network — seeing only one other node for hours after first connecting.