Skip to content

Releases

v2.3.0-sec.2-ts.1

Choose a tag to compare

@loki-notfound loki-notfound released this 17 Nov 01:19
v2.3.0-sec.2-ts.1
b90ac4b

The first release of zephyr-ts: a TypeScript wallet library for Zephyr, for Node.js, browsers and
Electron. It is monero-ts v0.11.22 (f6569ca6) adapted around the zephyr-backports wallet core
(zephyr-cpp over Zephyr's wallet2), compiled to one WebAssembly module. The core decides keys,
wallet files, transactions, fees and network rules; this library adapts the TypeScript API, the
worker and transport layers and the bridge, and does not change those rules.

zephyr-ts is an independent project, not affiliated with or endorsed by ZephyrProtocol.

Built from

Tag Commit
zephyr v2.3.0-sec.2 8c6a120256b4bd887d6e7167d929d76e3507e0e5
zephyr-cpp v2.3.0-sec.1 3a2ee602ee28e6b7941b617ad4706349ad992641

Both tags belong to the zephyr-backports release set of 2026-11-07 and are signed with the
zephyr-backports release key FB39 94F0 997C A6F0 43D7 2491 9EFF 03F5 27D2 40A1. sec.2 in this
release's version is zephyr's tag number. Toolchain and every other build input are pinned in
bin/pins.sh and listed in manifest.json.

What it does

  • Wallets: create, restore from a seed or keys, open from bytes, serialize, change the password,
    close; one worker per wallet; a forced stop of one wallet.
  • Accounts and subaddresses with labels; balances per asset as maps with bigint amounts.
  • Read-only history of transactions and transfers per asset, with an explicit pool refresh.
  • buildTransfer and buildConversion: build and describe a transaction without sending it.
  • prepareTransfer, prepareConversion, relayPrepared, discardPrepared: relay in two explicit
    steps. What is relayed is exactly what was described; the transaction's bytes never reach
    application JavaScript.
  • Transfers in the four V2 assets (ZPH, ZSD, ZRS, ZYS) and the six conversions between them. The
    library computes no rate: amounts come from the built transaction.
  • Daemon access over a transport that uses no proxy and follows no redirect; fixed error codes and
    diagnostics, no node text in errors.
  • A separate zephyr.wasm with an embedded SHA-256 check; a Node.js entry (require and import)
    and an ES module browser entry that Vite and webpack consume without configuration.

Not part of this release: sweeps, listeners and background synchronization, outputs, key images,
rescans, proofs, multisig, file-system wallets, the daemon and wallet RPC clients, and transactions
in the V1 assets. Read README.md and docs/LIMITATIONS.md in the package before using it with
real funds.

Proven on mainnet

On 2026-11-15 a funded test wallet relayed nine transactions to its own addresses: one transfer
per V2 asset, a transfer with two destinations, and the conversions ZSD to ZPH, ZPH to ZRS, ZSD to
ZYS and ZYS to ZSD. Each was accepted, mined, and after ten confirmations equal to its description
(fee, change, balances, minted amount received). ZPH to ZSD and ZRS to ZPH were refused at build
time by the reserve ratio. Not proven on real data: a refusal by a daemon, a transfer the core
splits, a conversion whose pricing record aged before the relay, the two refused pairs, relay from
a browser or from a wallet in a worker.

Platforms

The package is built on Linux x86_64 and consumed unchanged everywhere. Its offline checks pass
automatically on every commit in Node.js 22, 24 and 26, Chrome, Edge, Firefox, Safari and Electron
43 and 45, on Windows, macOS (Intel and arm64) and Linux; by hand on Windows 10 and on macOS 26 on
an Intel Mac. Everything that needs a daemon is tested on Linux x86_64. Node.js 22 or newer.
docs/PLATFORMS.md in the repository has the table and what is not tested.

Known

  • With the default priority the core chooses the fee tier itself and took the second tier of the
    daemon's estimate once in the nine mainnet transactions; a prepared build states the fee it will
    be charged.
  • In Firefox the worker script's own policy needs 'wasm-unsafe-eval' (docs/DEPLOYMENT.md).
  • One run of the Chromium job of the workflow on Linux ended without a result from the page; twenty
    repetitions of that check on the release build passed, and the cause is not known.

Install

The package is not on the npm registry. Download the tarball, verify it (below) and install it by
path; pin the exact file:

npm install ./loki-notfound-zephyr-ts-2.3.0-sec.2-ts.1.tgz

The version is a semver prerelease by its form, so a range will not select it.

Verify

gpg --import KEYS.asc
gpg --verify SHA256SUMS.asc SHA256SUMS
sha256sum -c SHA256SUMS

KEYS.asc is the maintainer key 31DA 39AB 43E0 CA67 F1F3 A661 BA2A FF22 DF8A 4A13, which also
signs this tag and every commit of the library. The build is reproducible: bin/build.sh and
bin/pack.sh at this tag give this tarball byte for byte (BUILDING.md); it was built on Debian 13
and on Ubuntu 24.04 with identical results.

File SHA-256
loki-notfound-zephyr-ts-2.3.0-sec.2-ts.1.tgz fcd8245e863ffbd516dfd1a0e11d78a849b2c612bd5818edab275f6afb26c0d8
dist/zephyr.wasm inside it 229b1534d60258c4be2f734f89effd38fba7a2ebf8ee7f95c33e96b9eda80333