btclib.org

Bitcoin cryptography in Python, written to be read.

These libraries grew out of Ferdinando Ametrano’s Bitcoin and Blockchain Technology course (Università di Milano-Bicocca, Politecnico di Milano, Università Statale di Milano, ESSEC Paris) and are used in production today. They are fully type annotated, cite the BIP, RFC or Bitcoin Core function a behaviour comes from, and are still marked beta because they are still refactored whenever that makes them clearer.

The libraries

• btclib-secp256k1 — Python bindings to libsecp256k1, Bitcoin Core’s optimized C library.
• btclib-ecc — elliptic curve arithmetic over any short Weierstrass curve, and the schemes built on it: ECDSA, BIP340 Schnorr, MuSig2, FROST, Diffie-Hellman, commitments and range proofs. For secp256k1 it uses btclib-secp256k1, and tests its own arithmetic against it.
• btclib — bitcoin’s protocol on top of btclib-ecc: addresses, scripts, transactions and blocks.
• btclib-mnemonics — BIP39, SLIP39 and Electrum mnemonics, from the entropy up to the seed, and nothing of bitcoin above it.
• btclib-wallet — from a seed to a signed, broadcast transaction: BIP32 keys, BIP39 and SLIP39 mnemonics, descriptors, PSBT, coin selection.
• bitcoin-core-rpc — a JSON-RPC client for Bitcoin Core, with nothing but the standard library behind it.
• btclib-benchmarks — timings against comparable libraries, kept apart so btclib never depends on them.

Around them

• btclib-node — a bitcoin full node in Python, built on btclib.
• bitcoin-node-tests — Bitcoin Core’s functional tests rewritten on btclib, to test any node against bitcoind.
• bbt — the course material: spreadsheets, notebooks, scripts and a regtest lab.
• portanode — Bitcoin Core and Electrum on a portable disk, for macOS, Windows and Linux.
• .github — this page, and the standard every repository here follows.
• btclib-org.github.io — the site serving this page at btclib.org.

How they depend on each other

An arrow points at what a package depends on, and a dashed one at what only the extra it is labelled with installs. An extra in brackets is one the package asks of what the arrow points at.

Tested against other people’s vectors

The suites answer to vectors published by others (BIPs and SLIPs, Bitcoin Core, HWI, Trezor, RFC 6979), each pinned to its upstream commit and re-checked weekly. Coverage is held at 100%.

Contributing

Issues and pull requests go to each repository; its README and CONTRIBUTING.md say how. A change needs a clean lint gate, a passing suite at full coverage, a signed commit, and a changelog entry where a user would notice.

License

MIT.

---

The btclib organization and its projects are actively supported by DGI and CheckSig.