· via dev.to (home feed)
Ledger enables clear signing on Solana, cutting Jupiter swaps from 13 screens to three
Ledger hardware wallets now describe Solana transactions in plain words instead of raw bytes, covering nine apps and 18 common actions. A dev.to script shows exactly what blind signing used to hide.

On 16 November 2026, Ledger switched on clear signing for Solana, an announcement also reported by Decrypt. People using its hardware wallets with supported apps now see, in plain words, what they are being asked to approve instead of a wall of raw transaction data. According to a dev.to post that examines the change, Ledger says the feature covers nine Solana apps and 18 of the 22 most common actions, starting with the Jupiter aggregator and Kamino, and that it was built together with the Solana Foundation and Anza.
The practical difference is compactness. A Jupiter swap that previously required 13 hard-to-read screens on the device now takes three, showing what you give, what you get, and who you are dealing with. Before this, most Solana DeFi activity on a Ledger required blind signing, a setting that ships off by default and that Ledger's own guide compares to signing a blank check.
What blind signing actually shows
To make the gap concrete, the dev.to author wrote a short Node script with no dependencies beyond Node 18's built-ins, talking to a Solana RPC endpoint over JSON-RPC. It picks a recent Jupiter v6 swap from mainnet, fetches it twice, once base64-encoded and once parsed, and prints the two views side by side: what a blind signer sees on the device, and what a person would actually want to read.
The first view is essentially a hash over raw transaction bytes. As the post puts it, nothing in that output tells you which token leaves your wallet, how much arrives, or where it goes. The second view, reconstructed by the node with full knowledge of every account, reads like a receipt. In one run on 17 November, it showed 1,044.475045 of one token received, 0.00014947 SOL sent, a network fee of 0.000007091 SOL, and the programs the transaction calls.
The part clear signing cannot automate
One detail from that run is instructive. Even with after-the-fact node data, the script printed an unknown program for one of the calls, because its small lookup table had no entry. That is precisely the problem clear signing exists to solve: someone has to describe what a program's instructions mean before any wallet can render them as words. Ledger's documentation, cited in the post, says that outside Ledger's own wallet app this depends on the app's developer and on how you connect. The 18-of-22 coverage figure is therefore a floor that grows only as more apps publish their instruction formats.
The author is also candid about the demo's limits. It decodes transactions that have already landed, whereas a wallet must interpret the unsigned message before signing, a harder job that needs simulation or per-program metadata. The script tracks only balances owned by the fee payer, so swaps routed through intermediate accounts, or wrapped SOL closed within the same transaction, can look odd. And it samples whatever Jupiter swap is recent, so the output differs on every run.
A tooling wrinkle worth noting
The exercise surfaced a side issue for developers. The sampled transaction came back as version 1, and the RPC node rejected the request until the script raised maxSupportedTransactionVersion from 0 to 1. Any tooling still pinned to 0 will start failing on these transactions, a small but real breakage unrelated to the signing change itself.
Why it matters
A hardware wallet is supposed to be the last line of defence, the one screen a compromised computer cannot rewrite. Blind signing quietly removes that guarantee: the user confirms bytes they cannot read, and verifying on the device becomes ceremony rather than a check. Clear signing restores that check for Solana's busiest flows, and the closing advice in the post applies well beyond Solana. App developers should publish what their instructions mean, and design flows where the three numbers that matter, what leaves, what arrives, and where it goes, are visible before anyone signs. Until coverage is universal, some fraction of users will keep approving transactions they would have rejected, had they been able to read them.
- #ledger
- #solana
- #hardware-wallets
- #security
- #defi