f180cfb9cf
In this commit, we add extensive test coverage for the StandardPolicyEnforcer including unit tests for each validation method and property-based tests to verify correctness across a wide range of inputs. The test suite uses a mockGraph implementation that provides the minimal PolicyGraph interface needed for testing. This allows us to test policy logic in isolation without requiring a full txgraph.Graph implementation, making tests faster and easier to understand. Unit Test Coverage: We test each major feature independently with focused scenarios. For RBF signaling, we verify both explicit signaling via sequence numbers and inherited signaling through multiple generations of ancestors. The deep inheritance test confirms that signaling propagates correctly through arbitrarily long transaction chains. The replacement validation tests cover all BIP 125 rules including edge cases like insufficient fee rates, too many evictions, and attempts to spend from parent transactions. Each test uses realistic transaction structures with proper fee calculations. The ancestor and descendant limit tests verify both count and size limits, ensuring we correctly enforce Bitcoin Core's 25-transaction and 101 KB limits. We test both at-limit (passing) and over-limit (failing) scenarios. Fee validation tests cover the minimum relay fee logic and the exponentially decaying rate limiter for low-fee transactions. The rate limiter tests verify both rejection when limits are exceeded and proper decay over time. Property-Based Testing: Using the rapid library, we add three property-based tests that verify invariants across randomized inputs. TestPropertySignalsReplacementTransitive confirms that RBF signaling is correctly inherited through chains of random depth. TestPropertyAncestorLimitEnforced generates chains of varying lengths to ensure limits are enforced at exactly the configured threshold. TestPropertyFeeRateMonotonic verifies fee rate calculations are consistent. These property tests run 100 iterations each with randomized parameters, providing high confidence that the policy enforcement logic handles edge cases correctly. Test coverage: 80-100% across all PolicyEnforcer methods. |
||
|---|---|---|
| .gemini | ||
| .github | ||
| addrmgr | ||
| blockchain | ||
| btcec | ||
| btcjson | ||
| btcutil | ||
| chaincfg | ||
| cmd | ||
| connmgr | ||
| database | ||
| docs | ||
| integration | ||
| limits | ||
| mempool | ||
| mining | ||
| netsync | ||
| ossec | ||
| peer | ||
| release | ||
| rpcclient | ||
| scripts | ||
| txscript | ||
| v2transport | ||
| wire | ||
| .gitignore | ||
| .golangci.yml | ||
| btcd.go | ||
| CHANGES | ||
| config.go | ||
| config_test.go | ||
| doc.go | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| log.go | ||
| Makefile | ||
| params.go | ||
| README.md | ||
| rpcadapters.go | ||
| rpcserver.go | ||
| rpcserver_test.go | ||
| rpcserverhelp.go | ||
| rpcserverhelp_test.go | ||
| rpcwebsocket.go | ||
| sample-btcd.conf | ||
| SECURITY.md | ||
| server.go | ||
| service_windows.go | ||
| signal.go | ||
| signalsigterm.go | ||
| upgrade.go | ||
| upnp.go | ||
| version.go | ||
btcd
btcd is an alternative full node bitcoin implementation written in Go (golang).
This project is currently under active development and is in a Beta state. It is extremely stable and has been in production use since October 2013.
It properly downloads, validates, and serves the block chain using the exact rules (including consensus bugs) for block acceptance as Bitcoin Core. We have taken great care to avoid btcd causing a fork to the block chain. It includes a full block validation testing framework which contains all of the 'official' block acceptance tests (and some additional ones) that is run on every pull request to help ensure it properly follows consensus. Also, it passes all of the JSON test data in the Bitcoin Core code.
It also properly relays newly mined blocks, maintains a transaction pool, and relays individual transactions that have not yet made it into a block. It ensures all individual transactions admitted to the pool follow the rules required by the block chain and also includes more strict checks which filter transactions based on miner requirements ("standard" transactions).
One key difference between btcd and Bitcoin Core is that btcd does NOT include wallet functionality and this was a very intentional design decision. See the blog entry here for more details. This means you can't actually make or receive payments directly with btcd. That functionality is provided by the btcwallet and Paymetheus (Windows-only) projects which are both under active development.
Requirements
Go 1.22 or newer.
Installation
https://github.com/btcsuite/btcd/releases
Linux/BSD/MacOSX/POSIX - Build from Source
-
Install Go according to the installation instructions here: http://golang.org/doc/install
-
Ensure Go was installed properly and is a supported version:
$ go version
$ go env GOROOT GOPATH
NOTE: The GOROOT and GOPATH above must not be the same path. It is
recommended that GOPATH is set to a directory in your home directory such as
~/goprojects to avoid write permission issues. It is also recommended to add
$GOPATH/bin to your PATH at this point.
- Run the following commands to obtain btcd, all dependencies, and install it:
$ cd $GOPATH/src/github.com/btcsuite/btcd
$ go install -v . ./cmd/...
- btcd (and utilities) will now be installed in
$GOPATH/bin. If you did not already add the bin directory to your system path during Go installation, we recommend you do so now.
Updating
Linux/BSD/MacOSX/POSIX - Build from Source
- Run the following commands to update btcd, all dependencies, and install it:
$ cd $GOPATH/src/github.com/btcsuite/btcd
$ git pull
$ go install -v . ./cmd/...
Getting Started
btcd has several configuration options available to tweak how it runs, but all of the basic operations described in the intro section work with zero configuration.
Linux/BSD/POSIX/Source
$ ./btcd
IRC
- irc.libera.chat
- channel #btcd
- webchat
Issue Tracker
The integrated github issue tracker is used for this project.
Documentation
The documentation is a work-in-progress. It is located in the docs folder.
Release Verification
Please see our documentation on the current build/verification process for all our releases for information on how to verify the integrity of published releases using our reproducible build system.
License
btcd is licensed under the copyfree ISC License.