1Sat SDK Merges Mandala Token Template After BRC-162 Consolidation

1Sat SDK Merges Mandala Token Template After BRC-162 Consolidation
,

Token Infrastructure Watch / Developer Tools

In Brief

The 1Sat SDK repository merged a Mandala token template on October 3, adding reusable code for constructing and reading BRC-162 token outputs on BSV Blockchain.

The implementation follows the October 2 standards change that renamed BRC-162 “Mandala Tokens” and withdrew the earlier BRC-92 Mandala Token Protocol.

The merged code operates at the script-template level. Higher-level wallet actions for deployment and sending remain planned.

News Report

Developer David Case, known on GitHub as shruggr, authored and merged the implementation into the 1Sat SDK repository through pull request #82.

The SDK brings together libraries for wallet connections, transaction construction, token operations and application integration. Its architecture separates script templates from the wallet engine and the actions that coordinate complete operations.

The new Mandala class joins the existing BSV21 template in the @1sat/templates package.

Building and Reading Token Outputs

The template provides builders for initial token outputs, outputs carrying token balances, and outputs carrying minting authority. It can also decode a Mandala output into its token identifier, amount, optional payload and underlying spending condition.

Developers can supply different locking scripts. The included unlocking helper is specifically for a P2PKH inner lock, the conventional public-key-hash payment condition.

Token Data Alongside Spending Rules

BRC-162 places token information at the beginning of a transaction output’s script. The token identifier and amount use binary fields that Bitcoin Script can read and construct without parsing JSON.

The spending conditions follow those fields. This allows token balances or minting authority to be combined with conditions such as multiple signatures, covenants or marketplace contracts.

The specification supports two supply models: an initial fixed supply, or an authority output that permits later issuance.

Token accounting remains a responsibility of implementations applying the token protocol. The specification does not introduce a separate token virtual machine into blockchain consensus.

Consolidation Preserves Important Compatibility Boundaries

The preceding standards change brought the Mandala name to BRC-162 and recommended it for new fungible-token issuance. BRC-161 remains the specification for existing BSV-21 tokens using JSON inscriptions.

The October 2 merge left BRC-162’s binary format and rules unchanged.

Withdrawal of BRC-92 also does not convert earlier BRC-92 outputs into BRC-162 outputs. The withdrawal notice explicitly identifies their incompatible on-chain formats, while the earlier specification’s NFT and BoundKeys features are not carried forward.

Wallet Actions Are the Next Step

An issue opened on October 3 records planned deployMandala and sendMandala actions for the SDK’s higher-level action package.

That work would connect the template to fuller wallet operations, including funding, recording created outputs and delivering transfers. The issue remains open, and its stated scope excludes marketplace listing and purchasing.

BSV TIMES has confirmed the source-code merge. A separately published npm package containing this change has not been verified.

BSV TIMES Read

The practical significance is the connection between a shared specification and reusable implementation code.

A common token format becomes easier to integrate when developers can use shared construction and decoding tools. That can reduce repeated work and provide a common place to identify differences between implementations.

The next useful milestones will be package distribution and completed wallet workflows. Those steps will show how the newly consolidated standard becomes accessible to application developers and, eventually, their users.

Developer Context

David Case, publicly identified on GitHub as shruggr, is a coauthor of BRC-162 alongside Deggen.

His related standards work includes:

  • BRC-159 — 1Sat Ordinals — Single-Satoshi Tokens and Origin Tracking, coauthored with Luke Rohenaz.
  • BRC-160 — 1Sat Ordinals — Inscription Envelopes, coauthored with Luke Rohenaz.

Source Links

Posted on October 3, 2026

Leave a comment