technology
Keystone 3 Addresses Parsing for Solana Transactions
By Roll · Chief of Staff · 19 Oct 2026
The hardware wallet firmware released on Oct. 16, 2026 addressed transaction parsing for Solana in the Web3 edition and refined setup steps for both the Web3 and BTC Only editions.
Release Event
What improvements arrived with the hardware wallet firmware released on Oct. 16, 2026? The update focused on two main areas: how the device handled SOL transactions and how users moved through initial setup steps.
The release came from the official GitHub repository for the Keystone 3 firmware. It applied to the Solana-capable hardware wallet and arrived as separate builds matched to each edition.
Parsing Changes
Per the release notes, the firmware improved transaction parsing for SOL in the Web3 edition. This change targeted the way the device read and processed those transactions during use.
The update did not alter other transaction types outside the stated improvement. Users of the Web3 edition received the parsing adjustment as part of the single firmware package for that edition.
Setup Adjustments
The same notes showed that wallet setup steps received refinements in the Web3 edition. The BTC Only edition received identical setup refinements in its own build.
Both editions therefore shared the setup change even though their builds remained separate. The release page confirmed the setup work applied to these two editions only.
Build Structure
The firmware shipped as separate builds for each edition. This structure kept the Web3 edition and the BTC Only edition on distinct packages rather than a combined file.
Each build included a published checksum. Users could compare the checksum on the device itself after download.
Distribution
The release page directed users to the official firmware site at keyst.one/firmware for the files. The page listed the builds and their corresponding checksums for verification.
The Oct. 16, 2026 date marks the point when the firmware became available through that channel. No other distribution method appears in the release documentation.
User Path
Users download the matching build for their edition. They then verify the checksum on the device before proceeding with installation.
The process follows the steps outlined on the release page. The separation of builds means each edition receives only the changes noted for it.
Summary of Scope
The update covered transaction parsing in the Web3 edition and setup steps in both the Web3 and BTC Only editions. All other details remain outside the scope of this release announcement.
NFA.
