144822d4bf
This commit removes the TxnCount field from the BlockHeader type and updates the tests accordingly. Note that this change does not affect the actual wire protocol encoding in any way. The reason the field has been removed is it really doesn't belong there even though the wire protocol wiki entry on the official bitcoin wiki implies it does. The implication is an artifact from the way the reference implementation serializes headers (MsgHeaders) messages. It includes the transaction count, which is naturally always 0 for headers, along with every header. However, in reality, a block header does not include the transaction count. This can be evidenced by looking at how a block hash is calculated. It is only up to and including the Nonce field (a total of 80 bytes). From an API standpoint, having the field as part of the BlockHeader type results in several odd cases. For example, the transaction count for MsgBlocks (the only place that actually has a real transaction count since MsgHeaders does not) is available by taking the len of the Transactions slice. As such, having the extra field in the BlockHeader is really a useless field that could potentially get out of sync and cause the encode to fail. Another example is related to deserializing a block header from the database in order to serve it in response to a getheaders (MsgGetheaders) request. If a block header is assumed to have the transaction count as a part of it, then derserializing a block header not only consumes more than the 80 bytes that actually comprise the header as stated above, but you then need to change the transaction count to 0 before sending the headers (MsgHeaders) message. So, not only are you reading and deserializing more bytes than needed, but worse, you generally have to make a copy of it so you can change the transaction count without busting cached headers. This is part 1 of #13. |
||
---|---|---|
.gitignore | ||
.travis.yml | ||
bench_test.go | ||
blockheader.go | ||
blockheader_test.go | ||
common.go | ||
common_test.go | ||
cov_report.sh | ||
doc.go | ||
error.go | ||
fakeconn_test.go | ||
fakemessage_test.go | ||
fixedIO_test.go | ||
genesis.go | ||
genesis_test.go | ||
internal_test.go | ||
invvect.go | ||
invvect_test.go | ||
legacy.go | ||
LICENSE | ||
message.go | ||
message_test.go | ||
msgaddr.go | ||
msgaddr_test.go | ||
msgalert.go | ||
msgalert_test.go | ||
msgblock.go | ||
msgblock_test.go | ||
msggetaddr.go | ||
msggetaddr_test.go | ||
msggetblocks.go | ||
msggetblocks_test.go | ||
msggetdata.go | ||
msggetdata_test.go | ||
msggetheaders.go | ||
msggetheaders_test.go | ||
msgheaders.go | ||
msgheaders_test.go | ||
msginv.go | ||
msginv_test.go | ||
msgmempool.go | ||
msgmempool_test.go | ||
msgnotfound.go | ||
msgnotfound_test.go | ||
msgping.go | ||
msgping_test.go | ||
msgpong.go | ||
msgpong_test.go | ||
msgtx.go | ||
msgtx_test.go | ||
msgverack.go | ||
msgverack_test.go | ||
msgversion.go | ||
msgversion_test.go | ||
netaddress.go | ||
netaddress_test.go | ||
protocol.go | ||
protocol_test.go | ||
README.md | ||
shahash.go | ||
shahash_test.go | ||
test_coverage.txt |
btcwire
[] (https://travis-ci.org/conformal/btcwire)
Package btcwire implements the bitcoin wire protocol. A comprehensive suite of
tests with 100% test coverage is provided to ensure proper functionality. See
test_coverage.txt
for the gocov coverage report. Alternatively, if you are
running a POSIX OS, you can run the cov_report.sh
script for a real-time
report. Package btcwire is licensed under the liberal ISC license.
There is an associated blog post about the release of this package here.
This package is one of the core packages from btcd, an alternative full-node implementation of bitcoin which is under active development by Conformal. Although it was primarily written for btcd, this package has intentionally been designed so it can be used as a standalone package for any projects needing to interface with bitcoin peers at the wire protocol level.
Documentation
Full go doc
style documentation for the project can be viewed online without
installing this package by using the GoDoc site here:
http://godoc.org/github.com/conformal/btcwire
You can also view the documentation locally once the package is installed with
the godoc
tool by running godoc -http=":6060"
and pointing your browser to
http://localhost:6060/pkg/github.com/conformal/btcwire
Installation
$ go get github.com/conformal/btcwire
Bitcoin Message Overview
The bitcoin protocol consists of exchanging messages between peers. Each message is preceded by a header which identifies information about it such as which bitcoin network it is a part of, its type, how big it is, and a checksum to verify validity. All encoding and decoding of message headers is handled by this package.
To accomplish this, there is a generic interface for bitcoin messages named
Message
which allows messages of any type to be read, written, or passed
around through channels, functions, etc. In addition, concrete implementations
of most of the currently supported bitcoin messages are provided. For these
supported messages, all of the details of marshalling and unmarshalling to and
from the wire using bitcoin encoding are handled so the caller doesn't have to
concern themselves with the specifics.
Reading Messages Example
In order to unmarshal bitcoin messages from the wire, use the ReadMessage
function. It accepts any io.Reader
, but typically this will be a net.Conn
to a remote node running a bitcoin peer. Example syntax is:
// Use the most recent protocol version supported by the package and the
// main bitcoin network.
pver := btcwire.ProtocolVersion
btcnet := btcwire.MainNet
// Reads and validates the next bitcoin message from conn using the
// protocol version pver and the bitcoin network btcnet. The returns
// are a btcwire.Message, a []byte which contains the unmarshalled
// raw payload, and a possible error.
msg, rawPayload, err := btcwire.ReadMessage(conn, pver, btcnet)
if err != nil {
// Log and handle the error
}
See the package documentation for details on determining the message type.
Writing Messages Example
In order to marshal bitcoin messages to the wire, use the WriteMessage
function. It accepts any io.Writer
, but typically this will be a net.Conn
to a remote node running a bitcoin peer. Example syntax to request addresses
from a remote peer is:
// Use the most recent protocol version supported by the package and the
// main bitcoin network.
pver := btcwire.ProtocolVersion
btcnet := btcwire.MainNet
// Create a new getaddr bitcoin message.
msg := btcwire.NewMsgGetAddr()
// Writes a bitcoin message msg to conn using the protocol version
// pver, and the bitcoin network btcnet. The return is a possible
// error.
err := btcwire.WriteMessage(conn, msg, pver, btcnet)
if err != nil {
// Log and handle the error
}
TODO
- Implement functions for BIP 0014
- Implement alert message decoding/encoding
- Implement bloom filter messages (filterload, filteradd, filterclear, merkleblock) as defined in BIP 0037
GPG Verification Key
All official release tags are signed by Conformal so users can ensure the code has not been tampered with and is coming from Conformal. To verify the signature perform the following:
-
Download the public key from the Conformal website at https://opensource.conformal.com/GIT-GPG-KEY-conformal.txt
-
Import the public key into your GPG keyring:
gpg --import GIT-GPG-KEY-conformal.txt
-
Verify the release tag with the following command where
TAG_NAME
is a placeholder for the specific tag:git tag -v TAG_NAME
License
Package btcwire is licensed under the liberal ISC License.