BSV TypeScript Stack Publishes SDK 3.0.0 and Updated Identity Packages

BSV TypeScript Stack Publishes SDK 3.0.0 and Updated Identity Packages
,

Developer Infrastructure Watch / Developer Tools

In Brief

The BSV TypeScript Stack has published SDK 3.0.0 alongside coordinated updates to its DID, Simple and Overlay Topics packages.

npm records date all four releases to October 3. Publication brings the identity implementation covered by BSV TIMES on October 2 into installable packages, including changes that retire earlier DID-token APIs.

The package release is confirmed. A separate infrastructure-image stage failed in the same workflow and required follow-up work.

News Report

The BSV TypeScript Stack has completed a new npm publication covering its core SDK and related application libraries.

The repository’s release follow-up records 30 packages published during the run. BSV TIMES directly checked npm records and downloaded the published archives for four central versions.

PackagePublished versionRelevant change
@bsv/sdk3.0.0Removes legacy serial-DID token exports
@bsv/did0.3.0Provides identity-key DID resolution and a BRC-52 credential adapter
@bsv/simple0.7.0Updates higher-level identity and credential APIs
@bsv/overlay-topics2.0.0Removes the earlier serial-DID overlay components

The GitHub publication job records success on October 3. This establishes a new milestone after the October 1 source-code merge reported by BSV TIMES two days ago.

Identity Keys and Original Certificate Signatures

The updated DID package can represent a wallet’s identity public key as a did:key identifier and resolve its document deterministically offline.

That identifies the encoded key. It does not establish a person’s identity, demonstrate current control of the private key or determine whether an issuer should be trusted.

The package also provides a BRC-203 adapter for existing encrypted BRC-52 certificates. It preserves the certificate’s original signed bytes and encrypted fields rather than replacing them with newly signed claims.

Applications still need separate decisions about disclosure, issuer trust, credential status and holder authentication. Generic W3C credential verifiers do not automatically support this custom mechanism.

Breaking Changes Require Migration

SDK 3.0.0 removes the earlier CanonicalDIDToken API and associated serial-token helpers. Existing wallet and certificate APIs remain supported.

Overlay Topics 2.0.0 similarly retires the tm_did and ls_did services. Its documentation points developers toward the existing identity-certificate discovery services when those are explicitly configured.

Simple 0.7.0 updates its identity and credential interfaces around the new model.

The migration guide warns against mechanically relabeling historical serial identifiers as identity-key DIDs: the two represent different things. It also states that the retirement itself removes no existing database records, private keys, issued credentials or on-chain records.

Operators must separately review their older clients, service registrations and application mappings.

Package Publication and Server Images Have Different Outcomes

The overall GitHub workflow ended with a failure even though its npm publication job succeeded.

The maintainer’s follow-up explains that seven infrastructure images were not built because of a workflow dependency condition. A correction was merged on October 3, with recovery requiring a separate infrastructure release.

The confirmed package publication therefore does not establish that the corresponding servers have been upgraded or deployed.

Some packaged documentation also retains earlier “candidate” wording. The publication finding here rests on npm records and downloadable package archives.

BSV TIMES Read

The practical change is availability. Developers can now install and pin the coordinated versions, test their applications against them and plan migrations around published artifacts.

That makes the distinction between identifiers, authentication and trusted claims consequential for existing integrations. A key identifier, a valid certificate signature and permission to act each answer a different question.

The release supplies reusable tools for those boundaries. Adoption will depend on applications handling them correctly and operators completing their own service changes.

Developer Context

Ty Everett authored the identity-adapter implementation merged through pull request #716. His related standards work includes BRC-42 — BSV Key Derivation Scheme, and coauthorship of BRC-100, the wallet-to-application interface, with Tone Engel and Brayden Langley.

Deggen, using the GitHub account sirdeggen, triggered the release workflow and authored the follow-up changes addressing infrastructure-image publication.

Source Links

Posted on October 4, 2026

Leave a comment