1Sat SDK Publishes Mandala Wallet Actions and Payments to Metanet Handles

Token Infrastructure Watch / Developer Tools

In Brief

1Sat SDK has published wallet actions for creating, sending and receiving Mandala tokens, alongside support for payments in the BSV token to readable Metanet handles. The changes merged on October 4 and are present in @1sat/actions version 0.0.233, published the same day. Live interoperability and desktop integration still need further work.

News Report

From script templates to wallet actions

The development follows the Mandala script template that BSV TIMES covered on October 3. That earlier integration supplied the building blocks for constructing and reading token scripts. The new actions connect those building blocks to wallet operations.

Pull request #88 adds deployMandala, sendMandala and syncMandalaInbox. Deployment supports both fixed supply and an authority output for subsequent issuance, with each token identified by the transaction output that created it.

Sending resolves a BRC-169 handle, prepares the transfer and delivers it through an encrypted message. Receiving checks the envelope signature, content integrity and token identifier before passing the transaction to the wallet. A message is acknowledged only after successful processing.

The npm registry records the publication of @1sat/actions 0.0.233 on October 4 at 08:21 UTC. Inspection of the distributed package confirms that the Mandala actions and the new handle-payment code are included.

Payments to readable handles

Pull request #89 extends the SDK’s sendBsv action to BRC-169 handles. A destination such as @alice@example.com resolves to the recipient’s identity and messagebox, allowing a payment to be addressed by a readable name.

The sender prepares a protected transaction without broadcasting it and delivers a signed envelope. The recipient’s wallet is responsible for processing and broadcasting the payment. This separates delivery to the recipient from submission to BSV Blockchain.

The implementation also distinguishes explicit Metanet handles from existing paymail-style inputs. An explicit @handle@domain uses BRC-169. A bare handle@domain checks whether the domain supports handles and can otherwise follow the existing paymail route.

Receipt is exposed through syncMetanetInbox and connected to the 1sat messagebox sync command.

Remaining integration work

Mandala transaction delivery uses proposed BRC-232, which remains an open draft. Its inclusion in the SDK does not settle the specification.

The Mandala merge notes describe tests using simulated components, without network calls, and explicitly leave compatibility with the default messagebox server’s BRC-231 CBOR interface unverified.

Desktop coverage is also partial. The send dialog gained handle support, but the separate full-page send view was unchanged, and the desktop application did not gain an automatic inbox poller. The verified milestone is publication of the developer package; complete desktop use and live interoperability require further validation.

BSV TIMES Read

The practical advance is that token creation, recipient resolution and transaction receipt now have reusable actions within the SDK. That can reduce the custom work required to build applications around Mandala on BSV Blockchain.

The next evidence to watch is successful live delivery between compatible wallets and messageboxes, followed by complete wallet interfaces. Those steps will show how readily the published components translate into everyday use.

Developer Context

David Case (shruggr) authored both merged pull requests. His related standards work includes:

BRC-162 — Mandala Tokens, coauthored with Deggen.
BRC-159 — 1Sat Ordinals: Single-Satoshi Tokens and Origin Tracking, coauthored with Luke Rohenaz.
BRC-160 — 1Sat Ordinals: Inscription Envelopes, also coauthored with Luke Rohenaz.

Source Links

Posted on October 5, 2026