blocktools wasm (TypeScript / JavaScript)

Private package ("private": true). Public-data API only: no private keys, no signing of secret material, no wallet-file openers. Build: sh scripts/wasm-check.sh from the repo root (also CI).

Install (path / workspace)

# after wasm-check produces pkg/node and pkg/web
npm install ./bindings/wasm

import init, {
  version, supportedChains, validateAddress, deriveFromXpub, checkTx,
} from "blocktools";
// Node: pkg/node is already wired via package.json "main".
// Web: await init() then call exports (see test-web.mjs).

Stable exports

See EXPORTS.md. The wasm build is scanned so secrets-feature symbols do not appear in the .wasm.

Examples

• Validate: validateAddress("btc", "bc1q...")
• Watch-only: deriveFromXpub(xpub, plan) / path plans from the facade
• Policy: checkTx(...) fail-closed
• Builders: PSBT+memo, EVM transfer, Tron decode — public inputs only

Security

Never pass mnemonics, WIF, or xprv into wasm. For recovery with secrets, use the sealed CLIs (./blocktools run) on an offline machine (docs/SECURITY.md).

Reproducible build

scripts/wasm-build.sh builds the .wasm from a copy of the sources (default build dir /tmp/blocktools-wasm-build, override with BLOCKTOOLS_WASM_BUILD_DIR). Cause of the earlier drift (measured on Linux): this crate is its own cargo workspace, so ../../crates sat outside the workspace root and cargo hashed their absolute path (and so the build dir) into each crate's metadata. The copy now makes its root the workspace (lock = both committed locks merged; the script fails if the resolved dependency tree differs from this crate's own lock), so the path is hashed relative to the root. scripts/wasm-check.sh does a clean rebuild from a second checkout at another path AND another build dir and fails if the sha256 differs. Measured on Linux only. A different CARGO_HOME, toolchain or clang version is untested.