BSV TypeScript Stack Updates Harden BRC-100 Byte Transport and Peer Authentication

Developer Stack Watch / Developer Tools

In Brief

The official BSV TypeScript stack has received a new group of package releases spanning the SDK, Message Box client, authentication middleware and Wallet Toolbox. A central focus is preserving BRC-100 transaction data consistently as it moves between wallets, messaging systems and web services, while the authentication layer adds tighter limits around pending requests, response sizes and protocol timeouts.

News Report

A new group of releases across the official BSV TypeScript stack is tightening compatibility between wallets, peer-to-peer messaging and authenticated application services.

The August 20 release window includes @bsv/sdk 2.4.1, @bsv/message-box-client 2.4.1 and @bsv/auth-express-middleware 2.2.2. @bsv/wallet-toolbox 2.9.0, the TypeScript reference implementation of the BRC-100 wallet interface, was also published during the same period.

The packages are maintained together inside the BSV TypeScript monorepo, which brings SDK primitives, wallet tooling, messaging, overlays, middleware, infrastructure services and cross-language conformance work under a common development structure.

One of the clearest themes in the new package documentation is byte-format compatibility at the BRC-100 boundary.

The SDK’s CreateActionResult can represent Atomic BEEF transaction data as either a conventional numeric byte array or a Uint8Array. Its BRC-29 remittance handling accepts both representations and emits a portable numeric-array settlement artifact so that the same transaction bytes can move through HTTP, WebSocket, Message Box and JSON transports without changing representation unexpectedly.

That distinction matters in JavaScript and TypeScript applications because binary typed arrays do not always retain the same shape when passed through ordinary JSON serialization. A transaction that is correct at the wallet layer can therefore become difficult for another component to interpret if the transport boundary does not normalize the bytes consistently.

Message Box Client 2.4.1 applies the same compatibility approach to peer payments and other remittance flows. Its payment client accepts both the historical numeric-array form and binary Uint8Array transaction results, while messages retain a portable JSON byte-array representation.

The client also retains compatibility with older records in which typed-array bytes were serialized as objects with numeric keys. Malformed, sparse or out-of-range byte records are rejected before they are passed into the wallet, while the original message remains available for retry or recovery rather than being silently consumed.

The same Message Box library provides authenticated store-and-forward messaging across browser and Node.js environments, with support for HTTP polling, authenticated WebSockets, peer payments, token-settlement adapters, permissions and message-delivery services.

The authentication side has also been tightened.

@bsv/auth-express-middleware 2.2.2, which implements BRC-103 peer-to-peer mutual authentication over the BRC-104 HTTP transport, explicitly preserves BRC-100 byte fields in handshake and buffered JSON responses across numeric arrays, Uint8Array and older numeric-key JSON representations.

The middleware also places finite limits around authentication state. Its defaults include a 30-second protocol timeout, no more than 1,000 pending authenticated requests per process, and an 8 MiB limit for application responses buffered for BRC-104 signing.

When those limits are exceeded, the middleware is designed to fail closed rather than leave authentication state accumulating without bounds. For horizontally scaled services where separate requests can reach different server instances, it also supports a shared asynchronous session manager rather than assuming all authentication state remains inside one process.

The broader @bsv/wallet-toolbox 2.9.0 package was published in the same release window. Wallet Toolbox connects the BSV SDK’s cryptographic and transaction primitives to persistent storage, network services, monitoring and signing flows and serves as the TypeScript reference implementation around the BRC-100 wallet interface.

These are library releases rather than new consumer applications. Developers still need to update dependencies and test the packages within their own wallet, messaging and server environments before users benefit from the changes.

Their significance lies primarily at the boundaries between components. A wallet, messaging client and authenticated service may all implement the same standards, but interoperability also depends on preserving the exact transaction data and protocol state as information moves from one component to another.

BSV TIMES Read

Infrastructure matures not only by adding capabilities, but by removing small inconsistencies between the layers that already exist. BRC-100 wallets, BRC-29 payments, Message Box communication and BRC-103/104 authentication increasingly operate as parts of the same application stack, so byte representation, request cleanup and bounded protocol state become important interoperability concerns rather than implementation details. These releases are not visually dramatic, but they strengthen the connective tissue that allows independently built applications and services to use the same underlying standards reliably.