Usually, when a full Bitcoin client such as bitcoind, Bitcoin-QT, or Multibit start on a fresh installation, they connect "to the network" to download the blockchain. If someone has multiple computers or devices, they could end up downloading the whole blockchain several times. This puts a lot of stress on their connection and extra clients on the network that could get their data locally.

Have any clients implemented a standardized way to exchange blockchain data locally, without going over the Internet?

I imagine this would work something like how BitTorrent local peer discovery works, where two clients on the same subnet discover each other through multicast groups and then negotiate transfer of data.

1 Answer 1


The Bitcoin.org client can be launched with the -connect= parameter.

Simply have it connect to another local node and no outside connectivity occurs.

But once it is caught up to the latest block, the amount of bandwidth is relatively trivial. There's no reason to do this to save bandwidth once a node has been brought current.

  • Would there be any merit to an automatic discovery and download? Or would it be better to rely on communication among users about the availability of other nodes on the same network? An example I see is a college network, where nodes are likely to exist but be unknown, as opposed to a home network, where a user will know if they are running Bitcoin on another computer.
    – Colin Dean
    Nov 20, 2012 at 17:32
  • 1
    Bitcoin is a financial app (i.e., money is involved. As such, you don't cut corners.) A node is best secured when run in a manner in which it gets blocks from randomly selected peers. This approach does cause performance that is less than you can get if you manually connect to other local nodes but you would only do so if you trusted those nodes. In a college environment, you would not want to trust getting all your blocks from peers within that network. Again, security is of greater importance than efficient use of bandwidth. Nov 23, 2012 at 8:13
  • That's an excellent point that I had not considered, that security trumps efficiency. However, given the nature of the blockchain, how difficult would it be for a malicious peer to distribute a fake blockchain if our client would eventually contact the outside world for updates, or even an initial portion of the blockchain?
    – Colin Dean
    Nov 23, 2012 at 22:04

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.