1Sat SDK Publishes Coordinated BRC-100 Wallet Stack Updates Across Core Packages

Wallet Stack Watch / Developer Tools

In Brief

The 1Sat development stack has received a broad coordinated package update spanning its BRC-100 wallet engine, browser and server implementations, application connection layer, transaction actions, React components and command-line tooling. The release wave strengthens 1Sat’s increasingly unified developer stack for ordinals, tokens and wallet-based applications, although BSV TIMES has not established that it represents completion of the separate BRC-147/BRC-150 interoperability work currently under development.

News Report

The 1Sat SDK has published a coordinated series of updates across much of its developer and wallet infrastructure, with new versions appearing across the core packages used to build BRC-100-compatible applications, browser wallets, server wallets and 1Sat Ordinals services.

The current npm registry shows recent releases including:

@1sat/wallet — v0.0.104
@1sat/actions — v0.0.198
@1sat/connect — v0.0.89
@1sat/react — v0.0.86
@1sat/wallet-browser — v0.0.90
@1sat/wallet-node — v0.0.70
@1sat/wallet-remote — v0.0.61
@1sat/wallet-server — v0.0.46
@1sat/client — v0.0.50
@1sat/templates — v0.0.31
@1sat/types — v0.0.40
@1sat/cli — v0.0.100

The packages were published as part of the same recent release cycle rather than as isolated updates. (npm)

The 1Sat SDK has evolved into a modular development stack around 1Sat Ordinals, BSV20/21 tokens and BRC-100 wallet infrastructure.

Its current architecture separates wallet functionality into multiple deployment models. @1sat/wallet provides the main BRC-100 wallet engine, while wallet-browser provides browser-side storage, wallet-node provides a Node/Bun implementation, and wallet-remote allows applications to use a remotely hosted wallet-storage service.

The recently published @1sat/wallet-server provides the corresponding server-side storage layer. Its documentation describes a BRC-100 wallet-storage RPC service that can authenticate clients either through BRC-100 mutual authentication or through a trusted proxy configuration. (npm)

Higher in the stack, @1sat/connect provides wallet connection through browser extensions or a popup flow, while @1sat/react exposes wallet integration through React components and hooks.

@1sat/actions provides reusable transaction operations, while the command-line package exposes wallet, ordinal, token, identity and other actions to scripts and developers without requiring a graphical application.

The current CLI, for example, supports wallet initialization and balances, ordinal listing and inscription, BSV21 token operations, identity functions and a generic action executor capable of invoking registered 1Sat actions programmatically. (npm)

This architecture is particularly relevant to the ongoing effort to make 1Sat Ordinals compatible with the wider BRC-100 wallet model.

BRC-147 defines a common 1sat basket profile for holding, listing, transferring and importing 1-satoshi ordinal outputs through existing BRC-100 methods. BRC-150 adds a provenance model intended to allow the current ordinal output to be verified back to its origin using BEEF transaction evidence rather than requiring trust in a global ordinal indexer. (Beersy)

The present 1Sat tooling already exposes similar architectural concepts. Existing 1Sat wallet documentation uses a 1sat basket for ordinal outputs and relies on standard BRC-100 operations including listOutputs, createAction and internalizeAction. (npm)

That does not by itself prove that the newest packages fully implement every requirement of BRC-147 or BRC-150.

Earlier this month, 1Sat developer David Case said work was underway to bring 1sat-sdk up to date with BRC-147 and related standards following a demonstration of moving 1Sat Ordinals into a BRC-100 wallet. BSV TIMES therefore continues to treat completed cross-wallet interoperability and full provenance support as a separate technical milestone rather than infer completion from package version changes alone.

What can now be verified is that the 1Sat project has published a broad new set of interoperating packages around a common wallet, application, service and tooling architecture.

The development surface also extends beyond conventional user-facing wallets. The repository describes its actions as self-describing operations for agents and tooling, while the CLI provides machine-readable JSON output and programmable access to more than 30 actions. (GitHub)

BSV TIMES Read

The significance of this release is less about any one package version than about the shape of the stack that is emerging.

1Sat Ordinals began with specialized tools for inscriptions and tokenized outputs. The newer architecture increasingly places those capabilities inside a common wallet framework where an application can connect to a wallet, request an action, manage an output through a defined basket and use the same underlying interfaces whether the wallet is running in a browser, on a server or through a remote service.

That matters for interoperability. Specialized assets become easier to use across applications when they no longer require a completely separate wallet architecture.

The ongoing BRC-147 and BRC-150 work is an important part of that direction because it attempts to define how a 1Sat Ordinal can be held and verified using the same BRC-100 interfaces available to other wallet applications.

The newest package releases should not yet be described as proof that this interoperability work is finished. They do, however, show a rapidly developing implementation stack converging around that shared architecture.