BTC Toolkit is a free, open-source command-line program for developers, students and power users who want to read and check Bitcoin data from a terminal without running a full Bitcoin node. It suits anyone building or testing Bitcoin tools who wants to confirm transactions, addresses and block details personally. The source code is published under the MIT license on GitHub.
The tool reads the chain through the Mempool.space public API, or through your own Mempool instance if you run one. Some checks happen locally: address checksums are verified offline, and a transaction can be tested against its block's Merkle proof and proof of work. The project notes builds for Windows, but macOS and Linux are the platforms it lists explicitly, so check the releases page before committing to a Windows setup.
How Merkle Proofs and Proof of Work Support a Transaction Check
A transaction on Bitcoin is recorded in a block, and that block is linked to earlier blocks through proof of work, the computational effort miners spend to produce valid blocks. A Merkle proof is a compact path of hashes showing that a transaction belongs to a block's list of transactions, without needing every other transaction in that block.
BTC Toolkit uses these structures to check what it can by calculation. If the data it receives for a transaction matches the block's Merkle root, and the block header meets its proof-of-work target, the tool has evidence that the transaction is included in a validly mined block.
This kind of check is narrower than it sounds. It confirms internal consistency with the data the tool fetched. It does not establish that a transaction is final or free from double-spend risk. Treat the output as one input into your own judgment, and compare confirmation information from other sources when money is at stake.
Public API or Your Own Mempool Instance: Choosing a Data Source
Every lookup BTC Toolkit makes needs chain data from somewhere. By default that is the Mempool.space public API, which is convenient because you install nothing else and can start querying quickly.
Public services have trade-offs. Your queries reach a third-party server, which can see which addresses and transactions you look at, and the service may rate-limit requests or change over time. Running your own Mempool instance moves the data source under your control, at the cost of setting up and maintaining that service.
For most readers, the public API is the practical starting point. Teams handling sensitive research, or those who want consistent results from infrastructure they operate, have good reason to consider a self-hosted instance. The checks themselves stay the same; only the origin of the raw data changes.
Real-World Scenarios for Developers and Analysts
BTC Toolkit fits a few recurring jobs. A developer building a wallet can confirm that a test address generated by their code is well formed before using it in a test suite. A support engineer who receives a transaction ID from a customer can look up the block and any OP_RETURN data without opening a browser.
Analysts and students benefit from scripting. Because the tool is driven by subcommands, a short shell script can pull fee data at intervals and log it for later comparison. Scripted lookups are easy to archive and review, which helps when you want to test a hypothesis about fee behavior.
It is less useful for everyday payments. Someone who only wants to check a balance or send coins will be better served by a wallet app or a block explorer. BTC Toolkit is built for inspection and verification, not for holding funds.
Key features
Chain data from Mempool.space or your own node-backed instance
Offline address checksum validation
Transaction checks against Merkle proof and proof of work
Subcommands for transactions, addresses, fees and blocks
No dependencies and no Bitcoin Core
Supported coins
The documentation mentions Bitcoin (BTC) and Liquid, the Bitcoin sidechain, as supported networks. Proof-of-work checks are tied to SHA-256, the algorithm Bitcoin mining uses. The documentation also mentions the Coldcard hardware wallet, so the tool can be used alongside that device during research, though it is not a substitute for the device's own software.
How to install BTC Toolkit on Windows
- 1
Get the program from the official source
Download only from the official website or the GitHub Releases page for the project at github.com/devdavidejesus/btc-toolkit. Choose the latest release, currently v1.8.2, and avoid unofficial mirrors or forks you cannot trace back to the repository.
- 2
Verify the file before running it
If the release page publishes a SHA-256 checksum or a signature, compare it with your download before you run anything. On Windows, open PowerShell or Command Prompt, run certutil -hashfile followed by the file name, and compare the output with the published value. A mismatch means you should not run the file.
- 3
Install a supported Python version
Install Python 3.11 or newer from python.org. The program has no third-party packages, so there is no package installation step beyond Python itself. Check your version by running python --version in a terminal.
-
Extract the files and run a first lookup
Extract the archive into a folder, open a terminal in that folder, and start the program with your Python interpreter. Run a simple subcommand such as fees to confirm that network access to the fee data works before you move on to address and transaction checks.
System requirements
- Python 3.11 or newer, as a supported version
- No third-party Python packages or Bitcoin Core installation needed
- Internet access to the Mempool.space API for network lookups, or access to your own Mempool instance
How to use BTC Toolkit
BTC Toolkit is driven entirely from the terminal, so the workflow is a set of short lookups. Start with the simplest check and move toward transaction verification as you get comfortable with the output.
- Open a terminal, such as Windows Terminal or PowerShell, in the folder where you extracted the program.
- Check a Bitcoin address with the addresses subcommand. This runs the offline checksum test, so you can catch a typo before pasting the address into a wallet.
- Look up a transaction with the txs subcommand. Note the block it belongs to, since the verification steps depend on that block's data.
- Inspect block details with the blocks subcommand, including any OP_RETURN data attached to transactions.
- Run fees to see recommended fee rates from the Mempool.space fee endpoint, then compare them with the fee your wallet suggests.
For exact arguments and options, read the repository readme that accompanies the release you downloaded, since syntax can change between versions.
Pros & cons
- Free and released under the MIT license, with source code on GitHub
- No third-party dependencies and no Bitcoin Core requirement
- Offline address checksum validation catches typos before you send anything
- Transaction checks against Merkle proof and proof of work add a layer of verification
- Can use your own Mempool instance if you want more control over data sources
- Command-line only, with no graphical interface
- macOS and Linux are the platforms listed explicitly; Windows builds need checking on the releases page
- Network lookups depend on the Mempool.space API or on a Mempool instance you run yourself
- Designed for inspection and verification, so it is not a wallet for everyday payments
Is BTC Toolkit safe?
BTC Toolkit is open source under the MIT license, so you can review the code before running it. Download only from the official website or the GitHub repository, and verify the SHA-256 checksum or signature if the release provides one. Forks and unofficial copies can differ from the original, so avoid them. The program's documented functions are read-only checks of public chain data. Still, never enter a seed phrase or private key on third-party websites, and be wary of any tool that asks for one. Check the latest version on the official website before you install an update.
- Official source only. Download from github.com/devdavidejesus/btc-toolkit. Ignore ads and lookalike domains.
- Check the SHA-256. Compare the installer hash with the value the developer publishes before running it.
- Never share your seed phrase. No developer, support agent or website — including CryptApps — will ever ask for it.
Alternatives
BTC Toolkit differs from most tools in this catalog because it is a small verification utility rather than a development environment. Nigiri sets up a local Bitcoin and Liquid network for testing, which means running infrastructure on your own machine. BTC Toolkit does not need a node at all, because it queries Mempool.space or your Mempool instance. RPC services such as Alchemy, Infura and QuickNode provide node access for applications, while Postman helps you test JSON-RPC endpoints directly. Rusty's guide covers how to store bitcoin, so it complements rather than replaces a checker. Choose BTC Toolkit when your main need is quick, terminal-based verification.
Specifications
- Price
- Free
- Type
- Open source
- License
- MIT
- Latest version
- v1.8.2
- Last update
- 22 Oct 2026
- Windows support
- Likely (builds for Windows; check releases)
- Source code
- github.com/devdavidejesus/btc-toolkit
Frequently asked questions
Yes, BTC Toolkit is free and open source under the MIT license. The source code is available on GitHub, where you can read it, build it and adapt it under the terms of that license. There are no listed fees for using the program itself, though network lookups depend on the Mempool.space API or on your own Mempool instance.
The project notes that builds for Windows exist, but macOS and Linux are the platforms it lists explicitly. Check the releases page to confirm that a Windows build is available for the version you want. If you run into problems on Windows, compare your setup with the platforms the project documents before reporting an issue.
No. BTC Toolkit works without Bitcoin Core, and it has no third-party dependencies. It reads chain data through the Mempool.space public API or your own Mempool instance, so you do not need to run a full node. You only need a supported Python version and an internet connection for network lookups.
The documentation mentions Bitcoin (BTC) and Liquid. Bitcoin is the main focus, and Liquid is listed alongside it. Proof-of-work checks are tied to SHA-256, which is the algorithm Bitcoin uses. If you need support for other networks, check the repository for current information before relying on the tool.
Partly. Address checksums are verified offline, so you can catch typos without sending the address anywhere. Transaction lookups and fee data require network access, either to the Mempool.space API or to your own Mempool instance. A valid checksum confirms only that the address is well formed, not that it is active.
Yes. The program can read chain data from your own Mempool instance instead of the public API. This gives you more control over which service receives your queries. Setting up and maintaining that instance is your responsibility, so plan for the upkeep before you switch data sources.
You need Python 3.11 or newer, which the project lists as a supported version. No additional Python packages are required, so you can install Python and run the program directly. Check your installed version with python --version in a terminal before you start.
Verdict
BTC Toolkit is a good fit for developers, students and technically minded Bitcoin users who want to verify transactions, addresses, fees and blocks from the command line. It is free, open source and has no dependencies beyond Python. Its checks are narrower than a full audit, and it is not a wallet. If you need a quick, scriptable checker and are comfortable in a terminal, it is worth testing. If you need a graphical tool or a place to hold funds, look elsewhere.