btclib-node
btclib-node is a full node bitcoin implementation written in Python and based on btclib.
To install, or upgrade:
python -m pip install --upgrade btclib-node
Python 3.14 or newer: pyproject.toml's requires-python says so and
says why, and pip refuses the wheel below it rather than installing
something that will not import. btclib-node is the command this puts
on PATH; btclib-node -h lists every option, spelled the way Bitcoin
Core spells its own. Read Security before running the node — the
classifier is 3 - Alpha and the JSON-RPC listener is not something to
expose.
A checkout of main is a cycle in progress, declaring the month with no
day, so it is not the same thing as what pip installs;
CONTRIBUTING.md has how to work from one.
Running a node
Running a node is what comes after
pip install: the command against each of the four chains, pointing it
at a peer of your own, reading its progress, the RPC methods it
answers, what it validates and what it does not, and what a mainnet
sync has actually been measured to cost.
Security
The JSON-RPC listener binds every interface and authenticates nothing — SECURITY.md carries that and the rest of what is known and recorded rather than a vulnerability to report again, and how to report one that is not already there.
Contributing
CONTRIBUTING.md's last section has the commands, and
they are the ones CI runs: uv sync builds the environment, uv run pytest is the suite and its coverage floor, and the lint gate is
.pre-commit-config.yaml run as lint.yml runs it. uv is the only tool
that has to be installed; it fetches the interpreter and every dependency
group itself.
REVIEWING.md is what a pull request here is answered against.
Links
- Source: https://github.com/btclib-org/btclib-node
- Releases: https://github.com/btclib-org/btclib-node/releases
- CHANGELOG.md for what changed, and
RELEASE_NOTES.md for what a release asks a user
to act on.
pyproject.tomlbetween releases declares the month a cycle is open on rather than a version anybody can install, andCONTRIBUTING.md's A release path, and what it has published is what that shape is for - REPOSITORY.md for the settings that live outside the tree
The btclib organization and its projects are actively supported by DGI and CheckSig.
Release files for btclib-node 2026.9.24
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| btclib_node-2026.9.24.tar.gz | 1.1 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| btclib_node-2026.9.24-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 MB
Release files / btclib_node-2026.9.24.tar.gz
| Download URL | btclib_node-2026.9.24.tar.gz |
|---|---|
| Size | 1.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5d631fe4d5793ab84d00b9121817fe8e0c3485a653d0d56c4fce240d1696f5c5
|
|
BLAKE2b-256 checksum How to use checksums |
f0bcd3aec7fb878f4d00091962e17651cba3cace474ff64290980a4bcdde1ba9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.
Transparency logRelease files / btclib_node-2026.9.24-py3-none-any.whl
| Download URL | btclib_node-2026.9.24-py3-none-any.whl |
|---|---|
| Size | 279.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
67fe634bbab60f6fb0004316196923defbc71017c4b967129035b53c8b81031d
|
|
BLAKE2b-256 checksum How to use checksums |
706fe8622faa69d47f5627ba9ac203023e34a34ceb2e80223045d94f632850f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.
Transparency log