> For the complete documentation index, see [llms.txt](https://doc.lockerprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.lockerprotocol.com/reference/changelog.md).

# Changelog

What changed in each release.

## Extension

### 2.5.8 (23 September 2026) - current

The release that carries everything cut since 2.4.8. Versions 2.5.2 to 2.5.7 were built, proven and superseded before any upload, so this is the one you get from the stores.

**A backup node on every chain.** Each mainnet chain now ships with at least two working nodes, from two different operators wherever a second one exists, measured through the wallet's own code before the release. When a node fails or refuses the request, the next one takes over. Existing installs pick up the new lists on their own. The providers are named in [Privacy](https://doc.lockerprotocol.com/reference/privacy.md).

**Solana and Tron sends.** A Solana send leaves more time for the round trip to the Vault. A Tron send whose validity window closed during the QR loop says so and asks you to rebuild it, instead of failing with the node's raw error.

**Developer mode is gone from the store build.** The switch only exists in development builds, and an install that had it on reads it as off. The menu entry for Settings now lists what Settings holds: language, fiat, notifications, auto-lock.

**New chains.** The wallet holds, sends and signs for five more families: **Cosmos** (Cosmos Hub, Osmosis, Injective, THORChain, Stride, Juno), **Aptos**, the **XRP Ledger**, **Litecoin** and **Dogecoin**. Sites that speak Keplr or the Aptos standard (AIP-62) find the wallet on their own.

**XRP tokens.** Issued tokens, trust lines, destination tags and the account reserve, on both sides of the QR.

**Scans stay with the wallet.** A signature asked by a site is scanned on the wallet's own surface, so the site never receives a camera permission. Scanning in the page is one tap away and says what it costs.

**One consent card at a time.** Requests queue instead of stacking, a card always carries the full host, and a refused origin waits 30 seconds before it may ask again.

**Firefox.** The add-on declares that financial data leaves the browser. Firefox 140 and later show that at install; on older versions the wallet asks itself, before its first request, and sends nothing until you answer. Settings has a **Withdraw** row for that consent. Firefox 128 to 139 can also verify the Vault's ed25519 signatures again (Solana, Sui, Stellar, Aptos).

**Safer by construction.** Typed data is read on the fields the signature really commits to; a swap route is held against the quote you accepted; a Bitcoin input travels with the transaction that funded it so the fee can be proven; the password that wraps the trading key is derived with 600 000 PBKDF2 iterations; a QR announcing an absurd number of parts is refused before anything is allocated.

**Fees and amounts.** The advanced gas fields have floors and ceilings with the reason spelled out, an amount too precise for its asset is refused instead of rounded, a replacement that would cost more than twenty times the original fee is refused, and the portfolio total says **Partial** when something it holds has no price.

*Verified reproducible: the Chrome, Edge, Brave and Firefox packages each rebuild 180/180 files bit for bit from a cold archive of the cut commit.*

### 2.5.0 to 2.5.7 (14 to 23 September 2026)

2.5.0 brought the new chain families. 2.5.1 added the XRPL issued-token layer. 2.5.2 answered Mozilla's decision of 18 September (the data declaration and the consent screen) and carried a pre-release audit. 2.5.3 raised the key derivation to 600 000 iterations. 2.5.4 made Bitcoin and Litecoin input amounts provable. 2.5.5 was a security release carrying a two-stage adversarial audit, and 2.5.6 closed four more findings of that audit. 2.5.7 added the backup nodes and removed Developer mode from the store build. None of 2.5.2 to 2.5.7 was uploaded: 2.5.8 replaces them all.

### 2.4.2 to 2.4.8 (11 and 12 September 2026)

Camera-blocked pages hand the scan to the wallet's side panel; the frame counter matches what the Vault reads; the connect screen was rebuilt; a network switch that follows a fresh connect is part of that consent; a disconnect reaches every chain family; the background watchers survive the browser suspending them.

### 2.4.1 (8 September 2026)

Scanning a Vault's **Bitcoin watch-only** QR by mistake is refused by name; every key of a `crypto-account` QR is routed by its derivation path; Linea balances are priced and counted in the home total.

*Earlier releases are listed with their verification status in the repository's `REPRODUCIBLE-BUILD.md`.*

## Vault

### September 2026

**Five more families to sign for.** Cosmos (six chains), Aptos, the XRP Ledger, Litecoin and Dogecoin, each with a review screen of its own that reads the bytes on the device: IBC transfers and their channels, THORChain memos read as the instructions they are, authority grants in red, Aptos key rotations, XRP regular keys, signer lists, partial payments and trust lines.

**Seventeen address rows** per recovery-phrase account, each with its own derivation path, and the same list on the sync page under *What the extension will receive*.

**More honest reviews.** A Bitcoin fee says whether it is proven or only declared; a Solana transaction totals what leaves the account and flags a burn; a Sui review names the sender, the gas payer and every object handed to a call; a Stellar review renders every operation type and its authorizations; a Tron permission change lists the keys, their weights and what they may sign; the line above a request says **Site named by the request (unverified)**, because that is what it is.

**Key handling.** PBKDF2 at 600 000 iterations, and a device that erases itself after 10 wrong passwords in a row (the notice used to say 50 while the code said 10). Every password prompt counts toward those 10, the signing screens included, not only the lock screen.

**Small things that matter.** The round **Sign** button starts the next ceremony as soon as an answer QR is on screen; the scanner is bounded so a QR held in front of the camera cannot freeze the device; a new version never reloads the Vault in the middle of a signature, a backup or a password change, it waits until you leave that screen.

### 2.4.0 (9 September 2026)

* The version is shown under **Settings → Application**.
* **One tap to scan:** the round **Sign** button opens the camera at once.
* **Lock** is red at rest in the bottom bar.
* **Extension Sync** is a violet card on the Accounts screen and under every account header. The sync page opens on an illustrated guide, folded after the first successful sync.
* **A fixed sign bar** on every review screen: the signing account, **Refuse** and **Sign**, always under the thumb.
* **"Not decoded" is no longer "dangerous":** a fourth, grey level in the verdict strip, on every chain.
* Real chain logos bundled with the Vault, everywhere an address is listed.

*The Vault updates itself the next time it is opened online; the banner **A new version is available. Loading...** shows when that happens.*
