Practical overview
When it fits
Use Bitiodine when you have local Bitcoin Core block files and want command-line analysis or a foundation for custom parsing work, rather than a hosted block-explorer interface.
Who it is for
- Bitcoin researchers analyzing locally stored block data
- Developers building custom Bitcoin block analyzers or indexers
- Analysts who need address clustering, balances or script-payload extraction from a local chain dataset
Documented uses
- Parse Bitcoin Core block files in chain-height order.
- Group addresses associated with co-spends using a heuristic.
- Calculate balances from surviving address-associated UTXOs.
- Extract OP_RETURN payloads and list recognized addresses.
- Build custom analysis visitors with the tool's visitor architecture.
Requirements & limits
The project is public source code under MIT or Apache-2.0 licensing. Building it requires Rust 1.85 or later.
- Full historical analysis requires unpruned Bitcoin Core data and a consistent snapshot of the block files.
- A trusted explicit chain tip is needed to anchor analysis; cumulative-work selection over supplied files alone does not establish Bitcoin Core's active chain.
- The parser does not validate proof of work, scripts, difficulty transitions or full consensus rules.
- Address clustering is heuristic: clusters indicate possible common ownership, not proof, and documented filtering can both merge unrelated activity and skip some patterns.
- CLI clustering uses SQLite and resumes completed blocks, but its database, indexes and undo records grow with the dataset; memory and disk capacity matter.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Build the Bitiodine command-line tool
Compile the documented release executable from the repository.
Before you start
- Rust 1.85 or later
- The Bitiodine GitHub repository
Steps
Obtain the repository source.
From the repository directory, run the command below.
cargo build --locked --releaseUse the resulting executable at
target/release/bitiodine.
Expected outcome
A release-mode Bitiodine executable is placed in `target/release/bitiodine`.
Guide limitations
- The documented build procedure does not itself configure Bitcoin block data or run an analysis.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 11 October 2026
- Original website title
- mikispag/bitiodine · Official homepage title · retained in its source language

