BSV TypeScript monorepo for the SDK, wallet tooling, overlays, messaging, middleware, helpers, infra services, docs, and cross-language conformance vectors.

Most applications should start with @bsv/simple or @bsv/sdk. Wallet builders usually start with @bsv/wallet-toolbox. Service operators usually start with the overlay, messaging, middleware, or infra packages.

Prerequisites:

• Node.js >= 22
• pnpm >= 9; this repo is pinned to pnpm@10.33.2

pnpm install
pnpm build
pnpm test

Useful root commands:

To work on one package:

pnpm --filter @bsv/sdk build
pnpm --filter @bsv/sdk test
pnpm --filter @bsv/sdk run test:coverage

These deployable projects are not included in pnpm-workspace.yaml; they keep their original server layout under infra/.

The conformance corpus is the portable contract for other BSV libraries and nodes to test against. Vectors live under conformance/vectors, use conformance/schema/vector.schema.json, and are indexed by conformance/META.json.

Important entry points:

CI publishes the conformance-vectors artifact from main so downstream SDKs can consume the same vector set.

Documentation source lives in docs. The local site lives in docs-site.

pnpm docs:dev
pnpm docs:build
pnpm docs:preview

Package-level docs start at docs/packages/index.md. Architecture docs start at docs/architecture/index.md.

The main CI workflow performs one frozen install and full package build, then runs non-coverage tests and the SDK, DID, wallet-toolbox, VeriFast, and other affected coverage suites in parallel. Wallet-toolbox coverage is split into four deterministic Jest shards, while its formerly network-sensitive monitor suite runs in a fifth isolated lane. The remaining coverage-capable packages are split across two deterministic lanes. Coverage artifacts are normalized and aggregated before one Codecov upload and the optional SonarCloud scan. Packages with a test:coverage script execute their assertions in a coverage lane; packages without one are selected dynamically by scripts/run-ci-tests.mjs, so each affected suite runs once without losing assertions or coverage.

The docs build, infrastructure matrix, dependency review, structural conformance runner, and dedicated TypeScript conformance runner remain independent gates. Superseded runs on the same PR are canceled so runner capacity is spent on the newest commit. The workflow expects the organization secrets already used by the BSV repositories:

• CODECOV_TOKEN
• SONAR_TOKEN

Every LCOV report is normalized to repo-root paths by scripts/normalize-lcov-paths.mjs. Root configuration lives in codecov.yml and sonar-project.properties.

Releases use GitHub Actions with npm OIDC provenance; no static npm token is required. Push a tag matching <package-path>/v* for a package release, or v* for a rare monorepo-wide release. Package tags publish the package at the tagged path; monorepo-wide tags publish packages changed since origin/main.

Each published package must be configured as an npm trusted publisher:

• Owner: bsv-blockchain
• Repository: ts-stack
• Workflow: release.yaml
• Environment: leave blank

Many packages were imported with git subtree and retain their upstream history. When pulling upstream changes, use the actual prefix from the package map:

git subtree pull --prefix=packages/sdk <remote> <branch>

Keep unrelated package history and generated artifacts out of the same change when possible.

See the individual package directories for license terms.