lbcd/peer
Dave Collins 089611a61b
peer: No error log on unexpected EOF.
This modifies the error handling path in the peer read loop such that it
will no longer log an error when the error is io.ErrUnexpectedEOF.  This
is being done because that error is almost always the result of a peer
being remotely disconnected and thus it isn't useful information to log.

However, since it might actually be due to a malformed message, a reject
message is still queued up to be sent back to the peer (which will
simply be discarded if the peer disconnected) before it is disconnected.

While it would be ideal to only log if it's not due to a disconnect, and
the code already attempts to handle that, it's not 100% possible to
detect upon the read returning an error without attempting to read again
which will not happen until the next loop iteration.
2016-11-10 19:00:37 -06:00
..
doc.go multi: Fix several misspellings in the comments. 2016-02-25 11:17:12 -06:00
example_test.go peer: rename peer.Connect to AssociateConnection 2016-10-21 14:13:18 -05:00
export_test.go peer: Refactor peer code into its own package. 2015-10-23 06:17:29 +05:30
log.go multi: Simplify code per gosimple linter. 2016-11-03 13:00:35 -05:00
log_test.go peer: Refactor peer code into its own package. 2015-10-23 06:17:29 +05:30
mruinvmap.go Optimize by removing defers 2016-10-18 17:56:51 -04:00
mruinvmap_test.go chainhash: Abstract hash logic to new package. (#729) 2016-08-08 14:04:33 -05:00
mrunoncemap.go Optimize by removing defers 2016-10-18 17:56:51 -04:00
mrunoncemap_test.go peer: Refactor peer code into its own package. 2015-10-23 06:17:29 +05:30
peer.go peer: No error log on unexpected EOF. 2016-11-10 19:00:37 -06:00
peer_test.go wire: Make NewMsgTx accept the tx version. 2016-10-27 14:09:29 -05:00
README.md docs: Make various README.md files consistent. 2015-10-23 14:51:36 -05:00

peer

[Build Status] (https://travis-ci.org/btcsuite/btcd) ![ISC License] (http://img.shields.io/badge/license-ISC-blue.svg) [GoDoc] (http://godoc.org/github.com/btcsuite/btcd/peer)

Package peer provides a common base for creating and managing bitcoin network peers.

This package has intentionally been designed so it can be used as a standalone package for any projects needing a full featured bitcoin peer base to build on.

Overview

This package builds upon the wire package, which provides the fundamental primitives necessary to speak the bitcoin wire protocol, in order to simplify the process of creating fully functional peers. In essence, it provides a common base for creating concurrent safe fully validating nodes, Simplified Payment Verification (SPV) nodes, proxies, etc.

A quick overview of the major features peer provides are as follows:

  • Provides a basic concurrent safe bitcoin peer for handling bitcoin communications via the peer-to-peer protocol
  • Full duplex reading and writing of bitcoin protocol messages
  • Automatic handling of the initial handshake process including protocol version negotiation
  • Asynchronous message queueing of outbound messages with optional channel for notification when the message is actually sent
  • Flexible peer configuration
    • Caller is responsible for creating outgoing connections and listening for incoming connections so they have flexibility to establish connections as they see fit (proxies, etc)
    • User agent name and version
    • Bitcoin network
    • Service support signalling (full nodes, bloom filters, etc)
    • Maximum supported protocol version
    • Ability to register callbacks for handling bitcoin protocol messages
  • Inventory message batching and send trickling with known inventory detection and avoidance
  • Automatic periodic keep-alive pinging and pong responses
  • Random nonce generation and self connection detection
  • Proper handling of bloom filter related commands when the caller does not specify the related flag to signal support
    • Disconnects the peer when the protocol version is high enough
    • Does not invoke the related callbacks for older protocol versions
  • Snapshottable peer statistics such as the total number of bytes read and written, the remote address, user agent, and negotiated protocol version
  • Helper functions pushing addresses, getblocks, getheaders, and reject messages
    • These could all be sent manually via the standard message output function, but the helpers provide additional nice functionality such as duplicate filtering and address randomization
  • Ability to wait for shutdown/disconnect
  • Comprehensive test coverage

Installation and Updating

$ go get -u github.com/btcsuite/btcd/peer

Examples

License

Package peer is licensed under the copyfree ISC License.