Documentation
The blocktools docs, rendered from the repo. Search everything, or pick a page.
- Chain table
Source of truth: crates/core/src/chains.rs. Known-answer vectors come from scripts/kat-chains.py, an independent base58check that uses only hashlib,…
- Claims
Every blocktools number and security claim, the command that measured it, and where it was measured.
- blocktools: design
blocktools is a set of small Unix command-line tools that recover keys from old wallet files and sign transactions. The tools run inside a sealed,…
- Exit codes (D1-14)
Each tool prints one JSON status line. Its exit code comes from that status through blocktools_io::exit_code:
- Paths: RPC in, tools piped, RPC out
Each path is a short sh script in recipes/paths/ with numbered stages. Data comes from a node, moves through blocktools on stdout and files, and when a…
- Offline policy file
tx-verify --policy FILE, tx-sign --policy FILE and wasm checkTxPolicy(tx, chain, json) check a transaction against declarative rules before signing.…
- Refusals and status codes
Every blocktools status and failure code, what causes it and what to do.
- rpc: talk to node and wallet RPC endpoints
rpc is a small host-side network tool that works as a pipe filter, in the style of netcat. It sends one call, or a stdin batch, to a node or wallet…
- Security
blocktools security: threat model, sealed runs, and what is and is not protected.
- Cookbook (by wallet type and chain)
blocktools cookbook by wallet type and chain: an index of the executable recipes.
- Getting started
Getting started with blocktools: install from the v0.1.1 release or from source, then your first sealed run on public test data.
- Library API guide (Rust)
Crate: blocktools (facade). Default features are public-data only — no private keys, no filesystem wallet openers, no sockets.
- blocktools wasm (TypeScript / JavaScript)
See EXPORTS.md. The wasm build is scanned so secrets-feature symbols do not appear in the .wasm.
- Troubleshooting / FAQ
Common errors and what to do.