> 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.4.1 (8 September 2026) * Current release. Chrome and Firefox packages verified reproducible (153/153 files). * Scanning a Vault's **Bitcoin watch-only** QR by mistake is refused by name, pointing at the sync QR, instead of creating an Ethereum account the Vault could never sign for. * Every key of a `crypto-account` QR is routed by its derivation path before an address is computed. * Linea balances are priced and counted in the home total. ### 2.4.0 * Verified reproducible (Chrome, Edge, Firefox). *Earlier releases (2.2.0, 2.1.x, 2.0.1, 1.1.0, 1.0.0) are listed with their verification status in the repository's `REPRODUCIBLE-BUILD.md`.* ## Vault ### 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. The header's QR button is gone; the bottom bar is the one entry. * **Lock** is red at rest in the bottom bar. * **Extension Sync** is a violet card on the Accounts screen and under every account header (from an account, the QR is built straight away). The sync page opens on an illustrated guide, *Where is the extension in Chrome or Brave?*, folded after the first successful sync; the QR screen shows the account on top, then **What the extension will receive**, one row per chain family with its logo. * **A fixed sign bar** on every review screen: the signing account, **Refuse** and **Sign** always under the thumb. When an unticked confirmation is the only blocker the bar says so, and one tap scrolls to it. * **"Not decoded" is no longer "dangerous":** a fourth, grey level in the verdict strip for calls the Vault cannot read, on every chain. It says what was checked (signing account, network, fees, outflows) and names the contract or program when it is known (Uniswap, 1inch, LI.FI, Aave, Lido, Seaport, Permit2, Jupiter, Raydium, Orca, Cetus, USDT, …). Proven dangers keep their red banner and checkbox. * Real chain logos (Ethereum, Bitcoin, Solana, Tron, Sui, Stellar) 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.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://doc.lockerprotocol.com/reference/changelog.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.