Policy & Governance / Developer Tools

In Brief

Several BSV Association toolkits have adopted Apache License 2.0, replacing main license files that restricted software use to BSV Blockchain. The change gives developers and businesses standard open-source terms to assess when reusing code, while historical licensing records and separate patent notices remain relevant.

News Report

Updates merged on November 11, 2026, cover TS Stack, BSV Wallet, Go Wallet Toolbox and the Python SDK. These projects provide components used to build wallets, applications and supporting services on BSV Blockchain.

The reviewed main license files match Apache’s official Version 2.0 text. The changes also introduce copyright notices naming BSV Association, followed by separate patent notices.

What Changes for Software Reuse

Apache 2.0 sets out permissions to copy, modify and distribute software, subject to conditions such as retaining required notices and identifying changed files. Its standard text contains no condition limiting use to BSV Blockchain.

For TS Stack, Apache 2.0 covers the project’s current contributions. Its policy preserves earlier licensing grants and the terms attached to code incorporated from other projects. A package can therefore carry more than one set of licensing obligations.

That distinction matters when assessing reuse: the main license identifies the project’s current licensing policy, while the accompanying records explain which terms apply to particular portions of its code.

What the Patent Notice Says

A separate PATENTS file says BSV Association holds no patent rights and describes the license as applying to copyright. It states that the Association will not assert patent rights against users of the software or derived works, and will secure the same commitment from entities licensing intellectual property to it.

The notice also states that the software comes without a guarantee against infringement. Apache 2.0 itself contains a contributor patent grant, limited to relevant claims that the contributor can license. The published notice does not identify a patent portfolio or establish a transfer of third-party patent ownership.

What Is Available

The changes are visible in the public source repositories. One published package, the mobile wallet toolkit’s version 0.24.3, released on November 11 at 22:15 UTC, also carries the Apache license text. Its repository received the separate patent notice after that package was published.

The scope is specific to the projects reviewed. Teranode’s own repository continues to display Open BSV License Version 6.

BSV TIMES Read

A standard license can give outside developers and businesses a more familiar starting point when considering these tools. The practical value of the transition depends on clear records accompanying the software people actually use: the current license, preserved historical permissions, third-party notices and the stated patent commitments.

For BSV Blockchain’s application ecosystem, the development concerns how its building blocks can be reused and distributed. Consistency between repository policies and published packages will help organizations assess that opportunity.

Developer Context

GitHub contributor sirdeggen submitted the licensing and patent-notice changes reviewed here. The updated copyright notices identify BSV Association.

Source Links

• TS Stack — Apache 2.0 Licensing Change, Pull Request #1560
• TS Stack — Updated Licensing Policy
• BSV Wallet — Licensing Change, Pull Request #101
• Go Wallet Toolbox — Licensing Change, Pull Request #1091
• Python SDK — Licensing Change, Pull Request #243
• TS Stack — Published Patent Notice
• Apache Software Foundation — Apache License, Version 2.0
• npm Registry — Mobile Wallet Toolkit Versions and Publication Dates
• Teranode — Current License

Posted on November 12, 2026 (UTC)