Repository navigation
Airlock 0.2.0
Warning
Not ready for production, and not formally audited. This is a prototype that handles private keys and signs transactions. Do not use it to hold or move real funds. Read the disclaimer first.
Which file to download
Airlock is the online app: it holds a vault, builds and submits transactions, and answers the browser extension. Airlock Offline is for a second device kept off the network: it reviews and signs, and opens no connection of its own. Transactions go between the two as QR codes or pasted text.
| For | Download |
|---|---|
| Windows, Airlock | airlock-0.2.0-windows-x64-setup.exe: the installer. It downloads WebView2 while installing if Windows has none |
| Windows, Airlock, on a machine that cannot download WebView2 | airlock-0.2.0-windows-x64-setup-full.exe: the same, with WebView2 inside (about 190 MB more) |
| Windows, Airlock, without installing | airlock-0.2.0-windows-x64-portable.zip: unzip and run airlock.exe |
| Windows, Airlock Offline | airlock-offline-0.2.0-windows-x64-setup.exe needs WebView2 already, as Windows 11 has it. airlock-offline-0.2.0-windows-x64-setup-full.exe has it inside, for a machine that has never been online. airlock-offline-0.2.0-windows-x64-portable.zip runs without installing |
| Mac with Apple Silicon | airlock-0.2.0-macos-arm64.dmg, airlock-offline-0.2.0-macos-arm64.dmg. Intel Macs are not built |
| Debian, Ubuntu and their kin, x86-64 | airlock-0.2.0-linux-amd64.deb, airlock-offline-0.2.0-linux-amd64.deb |
| Other x86-64 Linux | airlock-0.2.0-linux-x86_64.AppImage, airlock-offline-0.2.0-linux-x86_64.AppImage. The system needs WebKitGTK (libwebkit2gtk-4.1), as Ubuntu and Fedora desktops have |
| Android 14 and later, arm64 phones | airlock-mobile-0.2.0-android-arm64.apk: online or offline, chosen in the app |
| Signing for websites in Chrome, Edge or Brave | airlock-extension-0.2.0.zip, with Airlock on the same computer. See the browser extension |
| The browser bridge on its own | bridge-host-0.2.0-windows-x64.exe, bridge-host-0.2.0-macos-arm64.tar.gz. Only if you need it apart from the app: Airlock's installers, portable zip, Mac app and Linux packages already have it |
| Checking the files | SHA256SUMS.txt and airlock-0.2.0.sigstore.json. See checking a download |
| Licences of the IDL files the apps ship | THIRD-PARTY-NOTICES.md |
Opening it the first time
None of the apps is signed by a publisher Windows, macOS or Android knows, so each of them warns the first time.
- Windows shows "Windows protected your PC" (SmartScreen). Choose More info, then Run anyway. If Airlock is already running, quit it from its tray icon before installing a new version: with Close to tray on, closing the window leaves it running.
- macOS 15 and later says Apple could not verify the app is free of malware, and offers only Done and Move to Trash. Choose Done, then open System Settings → Privacy & Security, choose Open Anyway beside the app's name, and confirm with your password. Or, in Terminal:
xattr -dr com.apple.quarantine "/Applications/Airlock.app". macOS asks for the camera again after each update. For the standalonebridge-hosttarball, runxattr -d com.apple.quarantine bridge-hostafter unpacking it. - Android installs an APK from outside a store only once you allow it: when you open the file, Android asks to let the app you opened it from (your browser or file manager) install unknown apps. Allow it, go back, and install. A new version installs over the old one and keeps its data.
- Linux: install the
.debwithsudo apt install ./airlock-0.2.0-linux-amd64.deb. Make the AppImage executable (chmod +x) and run it. For a Ledger or Trezor, install the udev rules first: see hardware wallets on Linux.
The browser extension
The extension shows websites a Solana wallet and forwards their requests to Airlock on the same computer, which holds the keys and asks you. It is not in a store yet, so it is loaded from the zip:
- Install Airlock (the online app) on the computer. The Windows installer registers the browser bridge unless you untick it. Otherwise, or on a Mac or Linux, open Airlock and press Install the browser bridge on its Extension chip, beside the network chip in the sidebar.
- Unzip
airlock-extension-0.2.0.zipinto a folder you will keep: the browser loads the extension from that folder every time it starts. - Open the browser's extensions page:
chrome://extensionsin Chrome,edge://extensionsin Edge,brave://extensionsin Brave. - Turn on Developer mode.
- Choose Load unpacked, and select the folder you unzipped (the one with
manifest.jsonin it). - Restart the browser. Then start Airlock, unlock it and set it to Online.
To update it, unzip the new version over the same folder and press the extension's reload button on the extensions page. Firefox is not supported yet: the bridge registers itself for Firefox, but the zip is made for Chromium browsers, and Firefox keeps an unsigned extension only until it restarts.
Checking a download
SHA256SUMS.txt has the SHA-256 of every file. Compare it with the file you downloaded:
sha256sum airlock-0.2.0-linux-amd64.deb # Linux
shasum -a 256 airlock-0.2.0-macos-arm64.dmg # macOS
Get-FileHash airlock-0.2.0-windows-x64-setup.exe # Windows PowerShellEach file also has a provenance attestation: a signed statement that it was built by this repository's workflow from the tagged commit. With GitHub's CLI:
gh attestation verify airlock-0.2.0-windows-x64-setup.exe --repo tiago18c/airlockTo check it with cosign instead, without a GitHub account, see releasing. Both prove where a file was built. Neither is what Windows, macOS or Android check before running it.
What's new in 0.2.0
0.1.0 was tagged on 2026-11-09 and never published, so this is the first release. It has everything listed under 0.1.0 in the changelog as well as what is listed here.
Before you update
For anyone who ran a nightly build, or built Airlock before this release:
- On Linux and macOS, the data folder moved to where the platform keeps app data:
~/.local/share/airlockon Linux (or$XDG_DATA_HOME/airlock),~/Library/Application Support/airlockon macOS. A folder at~/airlockis moved there on first start, with nothing for you to do. - Authorizations of a programmatic signer signed on devnet before 2026-11-09 no longer run. Sign them again.
- Airlock Offline and the phone's offline mode now read transactions as mainnet's, where they read them as devnet's. To sign for devnet, choose it under Read transactions for in Settings.
Added
Platforms and installing
- Airlock and Airlock Offline for Macs with Apple Silicon, as disk images, and the browser extension's native host for macOS. They are not notarized by Apple yet, so the first launch is refused: open the app once, then choose Open Anyway in System Settings → Privacy & Security. macOS asks for the camera again after each update. The app has the browser bridge inside it: install it from the Extension status once Airlock is in Applications.
- Linux builds: a
.deband an AppImage of the online and the airgap app, for x86-64. The online app has the browser bridge in it; install it from the Extension status. - The Windows installer now asks whether to install the browser bridge, which lets the Airlock extension reach the app. It is on unless you untick it, and uninstalling Airlock removes it. The portable zip carries it too.
- When no browser is connected, the Extension status at the bottom of the sidebar offers Install the browser bridge, for when you skipped it in the installer, and Get the extension, which opens the latest release with the steps to load the extension.
Templates and Build
- Templates on Build. Templates, at the top of Build, opens a list of ready-made transactions beside a reader for the one you pick, as Programs reads an IDL: its questions, every instruction it writes with every field and where each value comes from, and its file as text, with Copy. Sixteen ship with the app: Create a token, Create a Token-2022 token (with a name and symbol, a transfer fee, a close authority, a permanent delegate, non-transferable tokens or a first supply, each a box to tick), Mint tokens, and the ones listed after this. Use this template opens it; with nothing on Build, the same templates are listed under the instructions to open at once. A template asks a few questions and writes the instructions for you; the new mint's key is made on this device. Everything it fills in itself is listed under Fixed by this template and Worked out, and Review and Sign reads the transaction as it reads any other, naming only the template it came from, under its title. Rent is read from your node; in Airlock Offline you type it. Show as blocks turns a filled template into ordinary instructions to change further.
- Your own templates. Save as template, beside Clear on Build, keeps the instructions on Build as a template: give it a name, and for each field keep its value, ask for it each time, or use the wallet in use or the fee payer. Fields you ask for that hold the same value become one question, and a key made on Build for a new account is made again each time. Your templates are listed under the built-in ones as "yours", and can be exported or removed from the reader. Templates are kept on this device only.
- Templates as text. In the Templates dialog, New template opens a short example to write your own from, with comments that say what each part is; Edit changes one of yours, Edit a copy starts one of yours from any template, and Import a template opens a
.tomlfile the same way. Beside the text, as you type, you see the questions it asks and every instruction it writes, or why it is not a template yet, with its line; whether it fits the network in use; and whether its name is taken: a built-in template's name is refused, and one of yours asks to be replaced. Save keeps the text exactly as you typed it, comments and all, and changing the name of one of yours renames it. Leaving with changes not saved asks first. A file that holds control characters or the invisible characters that change the direction of text is refused, naming its line. On a phone, where there is no file picker, a template goes between devices as text: Copy it from its Text tab and paste it into New template. - A Create a Raydium pool template, on devnet. It creates two tokens, mints a supply of each to the wallet in use, and opens a Raydium constant-product pool between them, depositing the amounts you give. You type the supply and the deposit in each token's own units. The pool lines the two mints up by address, so you do not have to, and its address is worked out from the fee tier and the mints. Devnet's fee-tier config 0 is filled in until you change it.
- An Upgrade a program template. It deploys the build in a buffer to a program, sending the buffer's lamports where you say. Two boxes add to the same transaction: Update its IDL copies the IDL a
program-metadatabuffer holds into the program's IDL account and closes the buffer, and Update its verified build rewrites the recordsolana-verifykeeps of the repository, commit and build arguments. The program data account and the IDL account are worked out from the program. It can be used on every network; its two boxes on mainnet and devnet. - Names and symbols for classic tokens. The Add a name and symbol to a token template gives a Token program token a name, a symbol and a link with Metaplex Token Metadata, where wallets and explorers look for them, and Create a token can add them as it makes the mint. On mainnet.
- Create an NFT makes an NFT on Metaplex Token Metadata, the classic standard: one token in your wallet, with its name, link, royalty and, if you like, the collection it claims. On mainnet.
- Core NFTs and collections. Create a Core NFT and Create a Core collection make them on Metaplex Core, with the NFT added to a collection of yours if you choose. On mainnet and devnet.
- Compressed NFTs. Create a compressed NFT tree makes a Bubblegum tree, its size chosen from the ones the programs accept and its rent read from the node, and Mint a compressed NFT mints into it. On mainnet and devnet.
- Create a vesting or payment stream locks tokens with Streamflow and unlocks them to a recipient on a schedule, amounts typed in the token's own units. On mainnet.
- Stake with Marinade. Four templates: Stake SOL with Marinade, Unstake mSOL now, Unstake mSOL in a few days and Claim a Marinade unstake ticket. On mainnet.
- Build fills arguments that hold several fields, and lists. An argument made of fields, such as the verify program's build record, is asked for one field at a time, and a list is typed as JSON,
["--library-name", "my_program"], or left blank for none. A struct inside a list or an option is typed as JSON, an enum whose choices hold values by its name or as JSON, and a fixed-size name such as Streamflow's as text, so instructions that hold one, such as Bubblegum's mints, can be built.
Wallet tools
- Migrate wallet, in the menu at the end of the Wallets header, moves what a wallet holds to another address: to rotate a key, or to move from a plain key to a programmatic signer, a Vector account or a multisig. Pick the wallet and where it goes, a wallet of this vault or a pasted address, which is checked first and needs its last characters typed when nothing shows anyone uses it. Then tick what moves, by group and item: token accounts (each moved or burned, empty ones closed), stake accounts (both authorities handed over), nonce accounts (closed), and the SOL, sent last and exact to the lamport, so a plain key is left empty. The steps are signed one after another. A multisig step that still needs approvals waits until it has executed. Afterwards it lists what on this device still names the old wallet, and offers to rename it.
- Manage tokens, in the menu at the end of the Wallets header and on Portfolio, burns and closes a wallet's token accounts to get their rent back. Pick the wallet, and it lists its token accounts, ticks the empty ones and those of tokens you flagged, and gives each closed account's rent (about 0.002 SOL) back to the wallet. A burn asks you to type "burn" first. It works for every kind of wallet, up to about 50 accounts per transaction (about 12 for a multisig or programmatic signer), and Next step on the landed dialog builds the next one.
- Portfolio shows token logos. Each logo is downloaded once, from the address the Tokens API names for it and without your key, and kept on this device. A token the Tokens API flags as passing itself off as another keeps its lettered avatar.
Squads and program deploys
- Program deploys and upgrades read as sentences when you sign: who upgrades which program from which buffer and where the buffer's spare lamports go, who writes into which buffer at which offset, who hands over the authority of a program or buffer (and that leaving the new authority out makes it final), who closes what and where its lamports go, and by how many bytes a program grows. The inspector reads a program, its program data and a buffer by what they are: the program data account, the authority and the deploy slot, without the program bytes after them. It also shows the hash of the code a program runs (read from its program data) or a buffer holds, in full and with a copy button, to compare with what
solana-verify get-program-hashorget-buffer-hashprints for a build you trust. - The Squads clear signing program's instructions read as sentences on devnet: a vote that carries what the proposal stores names the proposal, the transaction, the multisig, the member and the vote, and the checks of a buffer's, an account's or a program's hash show the hash in full, to compare with what
solana-verifyprints. - A Squads approval that carries what its proposal holds is shown in full, on a device with no network too: when the vote comes with the Squads clear signing check, the chain refuses it unless the proposal holds exactly the instructions shown, so Review and Sign lists them, warns of what they do as for any other instruction, and asks for no "I have checked" box. A program upgrade among them shows the hash of the build its buffer must hold, to compare with what
solana-verify get-buffer-hashprints, or warns when nothing checks the buffer. - Review and Sign can add what a Squads proposal holds to your approval, on devnet, when the vote has to be signed on another device or a hardware wallet: Add what the proposal holds rebuilds the approval so it carries every instruction the proposal stores (and the hash of the build a program upgrade deploys), and the chain refuses the vote unless the proposal holds exactly those. The device that signs then reads what it approves from the transaction alone. The member can be that key itself, a programmatic signer it is the authority of, or a Vector wallet it controls. It changes the transaction and costs a little more compute, and it works for one vote on its own, on a recent blockhash: not with the execution in the same transaction, not when several members approve together, and not on a durable nonce.
- Recording a program's verified build reads as a sentence when you sign, on mainnet and devnet: who states that which program is built from which repository at which commit, with the
solana-verifyversion, the build arguments and the deploy slot under it. Updating and closing such a record read the same way.
Programs that now read as a sentence
Airlock ships the IDL of each of these programs, so their instructions are put in words on Review and Sign, in a site's request and in History. Where a line says an amount is in the token's own units, it is written as the token counts it (1.5 USDC), with the decimals read from the mint; base units are the whole number the program stores (1500000). Programs are grouped by family.
Jupiter
- Jupiter swaps read as a sentence when you sign: who swaps how much of which token for the quoted amount of which other, and the slippage allowed, with the platform fee and any account the output is sent to listed under it. Amounts are in the token's own units (1.5, not 1,500,000), from its mint as your node reads it. Jupiter's IDL now ships with the app, so it is not fetched from the chain.
- Jupiter Perpetuals trades read as a sentence when you sign: who opens, increases, reduces or closes which long or short position, by how much in US dollars, with the collateral and the price limit, and where the payout goes. Requests, limit orders and take-profit or stop-loss orders say that a keeper executes them later, with their trigger price. Buying JLP, swapping through the JLP pool and borrowing against JLP read the same way. JLP amounts and the collateral of a request are in the token's own units; other token amounts, such as an instant trade's collateral or a swap's amounts, are in base units.
- Jupiter Lend Earn deposits and withdrawals read as a sentence when you sign: who deposits how much of which token to earn and which account receives the jlTokens, who withdraws how much of which token to which account, and who redeems how many jlTokens, with any minimum or maximum the transaction sets. Amounts are in the token's own units, from its mint as your node reads it. A withdrawal of everything shows as a very large number (18,446,744,073,709.551615 for a token with six decimals), which is how the transaction asks for all of it.
- Jupiter Lend Borrow positions read as a sentence when you sign: who opens a position and where its NFT goes, and who changes the collateral and debt of which position in the vault of which two tokens, with the collateral change and the debt change shown in each token's own units (positive deposits or borrows, negative withdraws or repays) and the accounts that pay and receive. A request to withdraw all collateral or repay all debt shows as a very large negative number, which is how the transaction asks for all of it. Liquidations show who repays up to how much of which debt.
- Jupiter Lend's liquidity layer reads as a sentence inside Jupiter Lend transactions: which market, vault, pool or flashloan account changes its supply and borrowing of which token by how much, in the token's own units (positive supplies or borrows, negative withdraws or repays), and which accounts receive withdrawn and borrowed tokens. Its admin instructions (interest rate curves, token fees, protocol limits, pausing, revenue) show a title and labelled settings, with rates in percent.
- Jupiter Lend DEX swaps and smart vault deposits read as a sentence when you sign: who swaps exactly how much for at least how much between which two tokens in which pool (in base units, with the direction shown), and who deposits or withdraws how much of each token as smart collateral, or borrows or repays smart debt, in the tokens' own units with the share limits the transaction sets. Pool settings (fees, price ranges, limits) show a title and labelled values in percent.
Meteora
- Meteora DLMM swaps and liquidity read as a sentence when you sign: who swaps how much from which token account for at least how much into which other, in which pool; who adds up to how much of each token to which position, removes what share of it, claims its fees, closes it, or places and cancels a limit order. Liquidity amounts are in the token's own units (1.5, not 1,500,000), from its mint as your node reads it; swap and limit order amounts are in base units, because the instruction does not say which of the pool's two tokens goes in. Meteora DLMM's IDL now ships with the app, so it is not fetched from the chain.
- Meteora DAMM v2 swaps and liquidity read as a sentence when you sign: who swaps how much from which token account for at least how much into which other, in which pool; who adds or removes liquidity of which position, paying at most or receiving at least how much of each token; and who claims fees, creates a pool, or opens, closes or locks a position. Liquidity limits are in the token's own units (1.5, not 1,500,000), from its mint as your node reads it. Swap amounts are in base units, because the instruction does not say which of the pool's two tokens goes in. Meteora's IDL now ships with the app, so it is not fetched from the chain.
- Meteora bonding curve trades and launches read as a sentence when you sign, on launchpads such as Believe and Jupiter Studio: who swaps from which token account into which other on which pool, and how much goes in for at least how much out; who launches which token under which name; and who claims a partner's or creator's trading fees, at most how much of each token and to which account. Fee limits are in the token's own units (1.5, not 1,500,000), from its mint as your node reads it. Swap amounts are in base units, because the instruction does not say which of the pool's two tokens goes in. Withdrawing surplus or leftover tokens and moving a finished curve into a Meteora pool read the same way.
- Meteora vault deposits and withdrawals read as a sentence when you sign: who deposits how much into which vault for at least how many of its LP tokens, who burns how many LP tokens to withdraw at least how much, and how much the vault's operator moves into or out of a lending strategy. LP token amounts are in the token's own units, from its mint as your node reads it; amounts of the vault's own token are in base units, because the instruction does not name its mint. Meteora's IDL now ships with the app, so it is not fetched from the chain.
- Meteora DAMM v1 swaps and liquidity read as a sentence when you sign: who swaps how much from which token account for at least how much into which other, in which pool; who adds liquidity paying at most how much of each token, or in any ratio for at least how many LP tokens; who burns how many LP tokens for at least how much of both tokens or of one; and who creates a pool, locks liquidity or claims the fees of locked liquidity. LP token amounts and a new pool's deposits are in the token's own units, from its mint as your node reads it; swap and liquidity token amounts are in base units, because the instruction does not name the mints. Meteora's IDL now ships with the app, so it is not fetched from the chain.
Raydium
- Raydium LaunchLab trades read as a sentence when you sign, on letsbonk.fun and the other launchpads built on it: who buys or sells how much of which token, for at least or at most how much of SOL or whatever token the pool is sold for, in which pool, with the fee accounts listed under it. Amounts are in the tokens' own units. Creating a token and its pool reads with the token's name and symbol (its curve settings are in the token's smallest units), and claiming creator fees, platform fees and vested tokens read the same way.
- Raydium AMM v4 pools read as a sentence when you sign: how much a swap pays in and the least it accepts (or the most it pays for an exact amount out), from which token account into which other in which pool, how much of each token a deposit may take, how many LP tokens a withdrawal burns, and what a new pool starts with. Swap amounts are in base units. In older swaps, deposits and withdrawals the token accounts are listed by number, because those take several account orders.
- Swaps through Raydium's router read as a sentence on mainnet too, as they did on devnet: who swaps how much from which token account for at least how much into which other through a route of pools, or receives an exact amount for at most how much, and the wrapping of SOL and closing of its account that Raydium's app adds around a swap. Amounts are in base units.
Pump
- Withdrawals from a Pump referral vault read as a sentence when you sign: who withdraws from which of their referral vaults, in SOL or in the token named under it. The instruction carries no amount (it pays out what the vault holds), so none is shown. Pump.fun creator fee sharing reads the same way, on mainnet and devnet: who sets up fee sharing for which coin, and who sets the shareholders of its creator fees, with each shareholder's share listed under it in basis points (10,000 is all of it). Creating a social fee account or a donation account for a coin, and forwarding its fees, read the same way.
- PumpSwap trades read as a sentence when you sign: who buys or sells how much of which token for at most or at least how much of the other, and in which pool, for the older trades and the newer, smaller ones alike. Creating a pool, adding and removing liquidity, and collecting and paying out fees read the same way. Amounts are in the token's own units (1.5, not 1,500,000), from its mint as your node reads it. A swap through several pools at once names the account it spends from and the account it pays into, with its amounts in base units.
- Pump.fun trades read as a sentence when you sign: who buys or sells how much of which coin on its bonding curve, for at most or at least how much SOL or of the token the coin is paired with, and who creates which coin, with its name, mint and creator. Amounts are in the token's own units (1.5, not 1,500,000), from its mint as your node reads it. A buy that may stop short when the curve runs out says so. Fee sweeps read too, and so do the bonding curve legs of a PumpSwap multi-hop swap, with their amount in base units.
Kamino
- Kamino Lend deposits, withdrawals and loans read as a sentence when you sign: who deposits how much of which token into which reserve as collateral of which obligation, withdraws up to how many collateral tokens and redeems them for which token into which account, borrows or repays how much of which token, takes or repays a flash loan, or creates an obligation. Amounts are in the token's own units (1.5, not 1,500,000), from its mint as your node reads it; where a withdrawal or repayment asks for everything, it shows the largest possible number, and the field says so. Kamino Lend's IDL now ships with the app, so it is not fetched from the chain.
- Kamino Farms stakes and rewards read as a sentence when you sign: who stakes how much of which token in which farm, unstakes how many stake shares, withdraws the unstaked tokens into which account, claims which reward token into which account, or creates or closes a farm account. Staked amounts are in the token's own units (1.5, not 1,500,000), from its mint as your node reads it; where a stake asks for the whole balance, it shows the largest possible number, and the field says so. Unstaked amounts are in stake shares, and the stake Kamino Lend sets for a position is in base units. Kamino Farms' IDL now ships with the app, so it is not fetched from the chain.
- Kamino Vault deposits and withdrawals read as a sentence when you sign: who deposits up to how much of which token into which vault and where the shares go, or burns up to how many shares to withdraw which token into which account, from the vault's available tokens and which reserve. A vault manager's changes read too: allocations to reserves, settings, fees collected or given up, and admin handovers. Token and share amounts are in their own units (1.5, not 1,500,000), from the mints your node reads; where a withdrawal asks for all your shares, it shows the largest possible number, and the field says so. Kamino Vault's IDL now ships with the app, so it is not fetched from the chain.
- Kamino Liquidity deposits and withdrawals read as a sentence when you sign: who deposits up to how much of each of a strategy's two tokens and which account receives the shares, deposits what a token account holds beyond an amount kept back after a swap, or burns how many shares for both tokens into which accounts. Token and share amounts are in the token's own units (1.5, not 1,500,000), from its mint as your node reads it. Strategy keepers' and admins' actions read too: investing, opening positions, collecting fees and rewards, vault swaps (in base units) and setting changes (by number). Kamino Liquidity's IDL now ships with the app, so it is not fetched from the chain.
Metaplex
- Metaplex NFT and token metadata read as a sentence when you sign: who transfers how many of which NFT or token from which owner to which, who is made or removed as a delegate of which kind (sale, transfer, locked transfer to a single address, utility, staking, standard, collection, data, print and the others) over which token, locks and unlocks, burns and mints, new metadata with its name, symbol, link, royalty in percent and update authority, updates (a new update authority shows when control changes hands), collection and creator verification, and print editions. The new data of an update shows on one line, with the royalty in basis points.
- Metaplex Candy Machine mints read as a sentence when you sign: who mints which NFT of which collection from which candy machine through which candy guard, with the guard group and the accounts the guards use (where a payment goes among them) listed under it. The price is not in the transaction: the candy guard's stored guards decide it, and the sentence says so. A launch owner's creation, update, wrapping and unwrapping of a candy machine, handover of authority and closing of a candy guard read as a sentence too; the guards themselves show as bytes.
- Metaplex Candy Machine setup reads as a sentence when you sign: who creates a candy machine of how many items for which collection, with its symbol, royalty in percent and authority, who adds items (their names and links show under it), updates it, sets its collection or token standard, hands its authority or its mint authority to another account, and closes it. A mint it makes for a Candy Guard names the NFT, the collection, the owner and who pays. The token standard shows as a number (0 for an NFT, 4 for a programmable NFT).
- Metaplex rule sets read as a sentence when you sign: who creates or updates their rule set, writes it in parts or makes room for it, and, inside a programmable NFT transfer or delegation, which rule set is checked for which operation on which NFT, with the accounts the rules check listed under it. The rules themselves show as bytes.
- Metaplex Core NFTs read as a sentence when you sign: which asset is transferred to whom, burned, created (its name and link, its collection, owner and update authority) or updated, and every change to its plugins, which is how control over a Core asset is granted: which plugin is added, changed or removed, and who is given or loses authority over it, such as a freeze, transfer or burn delegate. A new update authority shows as a field that says it takes control. Plugins chosen when an asset is created show by kind only, without their settings or the address of who controls them.
- Compressed NFT transfers, mints and burns read as a sentence when you sign: which NFT (its tree and leaf number) moves from which owner to which new owner, who mints an NFT with which name to whom in which tree (with its symbol, link, royalty as a percent and creators listed under it), burns, delegations, freezes, redemptions, creator and collection verifications, and the creation of a tree with its depth and buffer size. The hashes that identify an NFT in its tree show as hex under labels that say what they are.
Staking and liquid staking
- Marinade staking reads as a sentence when you sign: who stakes how much SOL, or which stake account, for mSOL and where the mSOL goes; who unstakes how much mSOL at once through Marinade's liquidity pool or orders a delayed unstake, and where the SOL goes; claiming a delayed unstake; withdrawing mSOL as a stake account and who controls it; and adding or removing liquidity in the mSOL-SOL pool. mSOL and LP token amounts are in the token's own units, from its mint as your node reads it.
- Liquid staking deposits and withdrawals read as a sentence when you sign, for JitoSOL and the other tokens of pools on the SPL Stake Pool program: who deposits how much SOL, or which stake account, into which pool, for pool tokens sent where, and at least how many when a minimum is set; who burns how many pool tokens to withdraw SOL or a stake account, where it goes and who controls the new stake account. A pool manager's changes of fees, manager, staker and deposit or withdrawal authorities read the same way. Pool token amounts are in the token's own units, from the pool mint as your node reads it.
- Sanctum LST deposits and withdrawals read as a sentence when you sign, for single-validator pools and for multi-validator ones (JupSOL and others): who deposits how much SOL, or which stake account, into which pool, for pool tokens sent where; who burns how many pool tokens to withdraw SOL or a stake account, where it goes and who controls the new stake account. Pool token amounts are in the token's own units, from the pool mint as your node reads it. The pool manager's instructions and the deposits and withdrawals that set a minimum still read raw.
- Jito vault deposits and withdrawals read as a sentence when you sign (the vaults behind kySOL, ezSOL, fragSOL and others): how much of the vault's token you deposit for at least how many receipt tokens, and where the vault's fee goes; how many receipt tokens a withdrawal request locks in its ticket, to be paid out after a full epoch; paying out a ticket; and handing a ticket to someone else. A vault's own settings read too: fees in percent, its deposit cap, its admin roles, and stake delegated to or taken back from operators. The amount you deposit and the receipt tokens a withdrawal locks are in base units; the minimum you receive is in the receipt token's own units.
- Jito restaking reads as a sentence when you sign: registering an operator or a node consensus network, adding a vault to an operator or a network, each side opting in to or out of the other (after a full epoch of warm-up or cooldown), activating a slasher, an operator's fee in percent, handing over an operator or a network and its roles, and letting another account move a token an operator or a network holds.
- Sanctum Infinity swaps and INF deposits and withdrawals read as a sentence when you sign: who swaps how much of which liquid staking token, from and to which token accounts, for at least or at most how much of which other; who deposits how much of an LST for at least how much INF, or burns how much INF for at least how much of an LST. Amounts are in each token's own units, from the mints as your node reads them. The pool admin's changes of LSTs, fees, authorities and rebalances read the same way.
- Jito tip distribution reads as a sentence when you sign: a validator opening its account for an epoch's MEV tips, with its commission as a percentage and who decides who gets paid; that authority uploading a merkle root, with the most it pays out in SOL and to how many recipients; claims, showing who receives how much SOL from which account; and closing expired accounts, with where unclaimed tips and rent go.
- Sanctum Router stakes, swaps and withdrawals read as a sentence when you sign: who stakes how much wrapped SOL for which liquid staking token, redeems how much of an LST for wrapped SOL, burns how much of an LST to withdraw a stake account, deposits a stake account for an LST, or swaps how much of one LST for another by way of a stake account, from and to which accounts. Amounts are in each token's own units. The router sets no minimum received, so none is shown.
Lending and yield
- marginfi deposits, withdrawals and loans read as a sentence when you sign: who deposits into, withdraws from, borrows from or repays which bank of which marginfi account, from or to which token account, whether a withdrawal or repayment takes everything, flash loans, closing a balance or an account, moving an account to a new owner, and deposits and withdrawals that marginfi passes on to Kamino, Drift, Solend or Jupiter Lend, named as such. Amounts sent to those protocols are in the token's own units; amounts of ordinary marginfi deposits, withdrawals, loans and repayments are in the token's base units, as those instructions do not name the token. marginfi's IDL now ships with the app, so it is not fetched from the chain.
- Loopscale loans, lending strategies and vaults read as a sentence when you sign: who borrows how much of which token from which lender's strategy, repays it, deposits or withdraws collateral, opens or closes a loan, and how a loan is refinanced or liquidated; a lender's deposits into and withdrawals from a strategy; and vault deposits, withdrawals, staking and reward claims. Principal and collateral amounts are in the token's own units; the amounts of a vault deposit or withdrawal show in base units, and a loan's term shows as the slot of the lender's terms it uses rather than as days.
- Huma 2.0 deposits and redemptions read as a sentence when you sign: who deposits how much USDC into which mode (classic for PST, maxi for mPST) and where the tokens go, who asks to redeem how many PST or mPST to be paid out later and who claims the USDC once a request is processed, instant withdrawals with the most they may pay in fees, and switches between modes. The pool's own operations read too: deploying liquidity to and from lending protocols, losses, and settings. USDC and token amounts are in their own units (1.5, not 1,500,000), from the mints your node reads; a few settings stay in base units. Huma's IDL now ships with the app, so it is not fetched from the chain.
- Huma credit pool deposits, redemptions and loans read as a sentence when you sign: who deposits how much USDC into which tranche of which pool, who asks to redeem how many tranche tokens to be paid out after an epoch closes, cancels a request or claims the USDC, who borrows how much on a credit line or pays at most how much toward it, and yield withdrawals. An evaluation agent's credit approvals and changes, receivables and the pool's settings read too. USDC and tranche token amounts are in their own units (1.5, not 1,500,000), from the mints your node reads; credit limits and a few other settings stay in base units. Huma's IDL now ships with the app, so it is not fetched from the chain.
- Hylo mints, redemptions and conversions read as a sentence when you sign: who deposits how much of which liquid staking token, collateral or USDC to mint hyUSD, xSOL or a leveraged token, who redeems how much hyUSD, xSOL or leveraged token for which token, who converts hyUSD and xSOL or a leveraged token into each other, and who swaps one LST for another or for USDC, with the account each token is paid into. The price is set when the transaction runs, so no received amount is shown; the slippage check the transaction carries, if any, is listed as its expected amount and tolerance in Hylo's fixed-point form. Amounts are in each token's own units, from the mints your node reads. Hylo's keeper and admin actions read too: yield harvests, LST price updates, fee withdrawals, pausing and address changes. Hylo's IDL now ships with the app, so it is not fetched from the chain.
- Hylo trades through its router read as a sentence when you sign: how much of which token goes in and which token comes out, for every mint, redemption and conversion of hyUSD, xSOL and the other leveraged tokens and every Earn Pool deposit and withdrawal made from Hylo's app. The amount is in the token's smallest units, and the slippage check, if any, is listed as its expected amount and tolerance in Hylo's fixed-point form; the accounts passed on to Hylo are listed in order. Hylo's admin actions on the router read too.
- Hylo Earn Pool deposits and withdrawals read as a sentence when you sign: who deposits how much hyUSD from which account for eHYUSD paid into which account, and who burns how much eHYUSD to take back their share of the pool's hyUSD, less the withdrawal fee, into which account. Amounts are in each token's own units, from the mints your node reads; the number of eHYUSD or hyUSD received is set when the transaction runs, and the slippage check, if any, is listed in Hylo's fixed-point form. The pool's admin actions and loss absorption read too.
- Save (formerly Solend) deposits, withdrawals and loans read as a sentence when you sign: who deposits how much into which reserve, as collateral of which obligation or for collateral tokens sent where; who withdraws up to how many collateral tokens and redeems them into which account; who borrows or repays how much from or to which reserve; flash loans, liquidations, and the creation of an obligation. Collateral tokens you redeem are in their own units; other amounts are in the token's base units (1,500,000 for 1.5 of a token with six decimals), because those instructions do not name the token's mint. Where a withdrawal, borrow or repayment asks for everything, it shows the largest possible number, and the field says so.
- Upshift vault deposits and redemptions read as a sentence when you sign: who deposits how much of which token into which vault for at least how many shares, paid into which account, and who redeems how many shares for at least how much of the vault's token after the withdrawal fee, paid at once into which account, and where the fee goes. What the vault's operator and admin sign reads too: moving funds out of a vault and back, reported balances, fees, the operator and pausing.
- Perena USD deposits and withdrawals read as a sentence* when you sign: who deposits how much USDC into which vault, or its senior or junior tranche, for shares paid into which account; who redeems how many shares for the vault's USDC, paid at once into which account less any withdrawal fee; who converts USD* into tranche shares; and who asks to withdraw junior shares, to be paid out later after the lockup. Price reports, NAV updates and the vault managers' swaps and holdings read too. Withdrawal requests for regular shares, permissioned deposits and incentive claims, which the program added later, still read raw.
- OnRe purchases, sales and redemptions of ONyc read as a sentence when you sign: who pays how much of which stablecoin from which account to take which offer and where the ONyc goes, at the offer's current price less its fee; who sells how much ONyc through the Prop AMM for at least how much of which token; and who asks to redeem how much ONyc, to be fulfilled later at the price then, or cancels such a request. Any approval a purchase carries shows the approved wallet and when it expires. OnRe's admin actions read too: offers and their price vectors (price, APR and dates), fees in percent, vault deposits and withdrawals, minting, roles and the kill switch. Amounts are in each token's own units, from the mints your node reads. OnRe's IDL now ships with the app, so it is not fetched from the chain.
Perpetuals and order books
- Phoenix perpetuals trades read as a sentence when you sign: who places a market, limit or post-only order on which market for which trader account, with its side, price in ticks and size in base lots, and any additional fee the front end adds; who cancels orders, places or cancels a stop-loss, deposits or withdraws collateral and from or to which token account, moves collateral between trader accounts, creates a trader account or grants permissions. Collateral amounts are in base units of the collateral token (1,000,000 is 1 token), because the instruction does not name its mint; SOL collateral reads in SOL.
- Phoenix perpetuals beta trades read as a sentence when you sign: who places a market, limit or post-only order on which market for which trader account, with its side, price in ticks and size in base lots, and any additional fee the front end adds; who sets or cancels take-profit and stop-loss triggers, deposits collateral from which token account, moves collateral between trader accounts or grants permissions. Collateral amounts are in base units of the beta collateral token (1,000,000 is 1 token). Newer instructions of the beta program, such as withdrawals with a fee, still read raw.
- Phoenix Ember's USDC wrapping reads as a sentence when you sign: who deposits how much USDC from which account into the wrapper and receives Phoenix's collateral token in which account, or how much of that token is burned from whose account and where the USDC is paid, in each token's own units.
- Manifest order book trades read as a sentence when you sign: how much a swap pays in at most and the amount out it names (a minimum when the input is exact), with whether it pays in the market's base token; how much of which token you deposit to or withdraw from a market or a global account, in the token's own units; the orders a batch cancels and places, each with its size, price, side, type and expiry; and seat claims and new markets. Swap amounts and order sizes are in base units, and order prices are shown as the two numbers they are made of.
- GMX Solana requests read as a sentence when you sign: placing an order says its kind (market or limit, increase, decrease or swap), the market, whether it is long or short, the size change in USD and the most you pay a keeper to execute it later; deposits, withdrawals, shifts and GLV deposits and withdrawals say how many market or GLV tokens you put in or ask for at least, and where the tokens go; closing a request says where its tokens and rent go. Collateral and deposit amounts are in base units, and trigger and acceptable prices are shown raw.
- Velocity (formerly Drift) reads as a sentence when you sign: creating a subaccount, depositing and withdrawing collateral (in the token's base units, with the spot market's number) and whether a withdrawal may borrow, moving collateral or a position between subaccounts, placing, changing and cancelling perp orders (order type, long or short, size and prices in whole units), making someone the delegate of a subaccount (who may trade but not withdraw), staking in and unstaking from an insurance fund, and settling profit and loss.
Swaps and routers
- DFlow swaps read as a sentence when you sign: who swaps through DFlow for the quoted amount of which token, the slippage allowed, and the account the output is paid to, with the platform fee listed under it. The amount and token you pay are not shown, because DFlow keeps them inside the swap's route; for some swaps the quoted amount is in the token's smallest units, as the instruction does not say which token it is. Sending tokens to a DFlow sponsor, and wrapping and unwrapping SOL, read the same way.
- OKX swaps read as a sentence when you sign, as OKX Wallet and OKX DEX build them: who swaps how much of which token for a quoted amount of which other token, and the slippage allowed, with the commission recipient and the platform's share listed under it. The commission's rate shows as a single packed number. Creating the token accounts a swap needs reads the same way.
- PancakeSwap v3 swaps and positions read as a sentence when you sign: who swaps which token for which in which pool, from which token account to which; who opens, adds to, removes from or closes a position, paying at most or receiving at least how much of each token; and who creates a pool or starts its rewards. Position amounts are in the token's own units (1.5, not 1,500,000), from its mint as your node reads it. Swap amounts are in base units, because a flag in the swap decides whether the amount is what goes in or what comes out. PancakeSwap's IDL now ships with the app, so it is not fetched from the chain.
- Byreal swaps, positions and rewards read as a sentence when you sign: who swaps which token for which in which pool, from which token account to which; who opens, adds to, removes from or closes a position, paying at most or receiving at least how much of each token; and who claims how much of which reward token, into which account. Position and reward amounts are in the token's own units (1.5, not 1,500,000), from its mint as your node reads it. Swap amounts are in base units, because a flag in the swap decides whether the amount is what goes in or what comes out. Byreal's IDL now ships with the app, so it is not fetched from the chain.
- Hadron swaps, deposits and withdrawals read as a sentence when you sign: who swaps how much from which token account for at least how much into which, in which pool, and who deposits into or withdraws from a pool how much of each of its two tokens. Amounts are in base units. The operators' own price, spread and curve updates have a title and labelled fields.
- Riptide swaps and market deposits read as a sentence when you sign: who swaps how much in which market, between which token accounts, and whether the amount is token A or token B; and who deposits into or withdraws from a market how much of each token, in the token's own units. Swap amounts are in base units. The operator's quote updates and settings changes have a title and labelled fields.
Bridges and messaging
- Chainlink CCIP transfers read as a sentence when you sign: who sends a message to which receiver, in full, on which destination chain (by its chain selector), which tokens go with it and how much of each, and which token pays the fee. Token amounts are in base units, beside each token's address. Token administrators read too: registering a token, proposing, transferring and accepting its administrator role, and setting its pool, as do the router owner's changes and fee withdrawals.
- Chainlink CCIP pool locks and releases read as a sentence: how much of which token a send locks in its pool, by whom, for which receiver on which destination chain (by its chain selector), and which token a delivery releases to whom, from which source chain and sender. What a token's pool owner signs reads too: creating the pool, adding and editing remote chains and their rate limits (in base units), the sender allow list, the rebalancer and its liquidity, and handing over ownership.
- LayerZero messages read as a sentence when you sign: which application sends a message to which receiver, in full, on which destination endpoint (by its endpoint ID), with the most it may pay in fees in SOL, and who pays them. What an application's owner or delegate signs reads too: registering the application, setting its delegate, its send and receive libraries and their grace periods, and its configuration, as do the verification, delivery and alerts of incoming messages.
Payments and vesting
- Subscriptions and token delegations read as a sentence when you sign: who lets whom pull how much of a token, in total or in each period of how long, from when and until when (a date of 1970-01-01 is shown where the program means "never expires" or "no end"), who subscribes to which merchant's plan for how much how often, who pulls how much under such a permission and to where, and who cancels, resumes or revokes one. Enabling delegations for a token says plainly that it approves the program for an unlimited amount of that token. Pulls and plans show amounts in the token's own units; amounts in new delegations and subscriptions are in base units, because the token is not among their accounts. Devnet's build reads the same way.
- Streamflow vesting contracts read as a sentence when you sign: who locks how much of which token for which recipient, how much unlocks at the cliff and how much every period after it, plus Streamflow's fees, with the start and cliff dates, the period as a duration and each right the contract gives (who may cancel or transfer it, top-ups, pausing, rate changes, automatic withdrawals). Withdrawals, cancellations (unlocked tokens to the recipient, the rest back to the sender), transfers to a new recipient or sender, top-ups, pauses and setting changes read too, and say where Streamflow's and a partner's fees go. A new amount per period set on an existing contract is in the token's smallest units.
- Streamflow staking reads as a sentence when you sign: who stakes how much of which token in which pool, locked for how long, for whom, and where the pool's receipt tokens go; requests to unstake, unstaking (receipt tokens returned, the staked tokens back to your account), automatic unstaking when a lock ends and closing a stake entry. Creating a stake pool shows its shortest and longest lock as durations and how much more the longest lock weighs, with its cap, closing date and waiting period; handing over a pool's authority reads too.
- Coinflow credit checkouts read as a sentence when you sign: redeeming Coinflow credits shows how much of which token Coinflow's vault sends to your token account for the purchase, and that a token account created for it is paid for by Coinflow's fee payer and can be closed by it; SOL bought with credits for the transaction, and what is returned to Coinflow at the end, read too. Coinflow's own settlements to merchants show amounts in base units.
Others
- Magic Eden NFT pool trades read as a sentence when you sign: who sells an NFT to a pool for at least how much SOL, or buys one from a pool for at most how much, and who receives the maker and taker fees; creating, updating and closing a pool, setting the collections it trades, and depositing or withdrawing SOL and NFTs read plainly too.
- MetaDAO trades and proposals read as a sentence when you sign: who swaps how much for at least how much on a DAO's spot market, or on the pass or fail market of a proposal, and whether it is a buy or a sell; who adds or withdraws liquidity, stakes on or unstakes from a proposal, and who drafts, sponsors, launches or finalizes one, with the Squads transaction a drafted proposal would approve. Swap, liquidity and stake amounts are in base units; unstaking and new DAOs show whole tokens.
- Star Atlas cargo moves read as a sentence when you sign a SAGE transaction: who adds how much of which cargo type to which cargo pod and from which token account, removes it to which account, moves it between two pods, or burns fuel, food and ammo from a pod, with pods being created, handed over and closed. Amounts burned or minted are in the token's own units; amounts added, removed or moved are in base units, which for most Star Atlas resources are whole units.
- Star Atlas SAGE reads as a sentence when you sign: which key signs for which player profile, and which fleet warps or subwarps to which sector coordinates, docks or undocks at which starbase, starts or stops mining which resource at which planet, or scans a sector; how much of which resource moves between a starbase and a fleet's cargo pods or between your wallet and a starbase; ships deposited into or withdrawn from a starbase's escrow, fleets created, given ships and disbanded, crew moved, and crafting set up, started, stopped and claimed. Amounts are in the token's own units where the instruction names the token, otherwise in base units, which for most resources are whole units. Game admin instructions have titles and labelled fields.
- Market Tick updates read as a sentence when you sign: which key records a tick for which slot, at what time by its own clock and at what target interval, and who pays to create the tick account.
- Quarry staking and rewards read as a sentence when you sign: who stakes or withdraws how much of a quarry's token, from or to which account, and who claims the rewards their miner has earned, minted into which account less the rewarder's claim fee. Amounts are in the token's base units, since the instruction does not name its mint. Creating a miner, a quarry or a rewarder, and the rewarder authority's changes to rates, shares, famine dates, pausing and authority, read too.
Changed
Review and Sign
- Review and Sign says when an instruction carries more data than its IDL describes, and shows those bytes. An IDL describes an instruction up to its last argument; if the program has gained an argument since, the bytes after it mean something no sentence shows. Some apps pad their instructions with zeros, so the note is not an alarm, but a site's request that has one is signed from Review and Sign and not from the request window.
- An amount set to the largest possible number reads as "the maximum", in sentences and fields. Lending and vault apps send that number to withdraw or repay everything, and it read as a withdrawal of 18,446,744,073,709.551615 tokens.
- A program upgrade, or a change of who can upgrade a program, no longer gets a warning line of its own on Review and Sign, in the browser request modal or under Stored on chain: the instruction itself already says it in a sentence. It is still signed from Review and Sign, not from the modal, and the modal says so.
- A site's request keeps your work when something else takes Review and Sign. Sending from Wallets, Build, Stake or anywhere else while a site's request is open there sets the request aside with any signatures already added, and the page says so. Opening the request again from its card or bar brings it back as you left it. Before, it was dropped and prepared again from scratch. A site's request no longer replaces a transaction of your own that already carries a signature without asking first.
- A site's request on Review and Sign names the site under the title, after a globe ("Requested by https://jup.ag"), and the head's Clear reads Reject, which tells the site no. A transaction from Build, Wallets or Stake, or one pasted or scanned, says so in the same place. While that request is on screen, its reminder card no longer shows over the page. On a phone, a request you set aside is a bar at the top of the page instead of a card at the bottom, and no toast covers an open sheet or dialog.
- Review and Sign leads with the next step. Every transaction shows its steps, one signer or several. The action buttons are one row in one order and stay at the bottom of the pane while the transaction scrolls: once this device has signed and another device is next, Share with another device is the main button, and Submit appears when every signature is in. Add a signature and Load another transaction are two buttons. A signer whose key is elsewhere says where ("needed from its offline device") and has a Share button on its row.
- A token account is named by its owner, "Alice · USDC", wherever it is shown, so a token transfer says whose tokens move and to whom.
- The Summary says which instructions it leaves out ("Instructions 1 and 2 set the compute budget and are not shown") with a way to Inspect, and the fee line shows the fee and its priority part instead of the payer's whole balance change. A signer's row no longer carries a balance change, and neither does an address inside a sentence, which already says what moves. An account that changes and that no sentence names is still listed under the instructions with what it gains or loses ("Also changes"), and Inspect lists every account's change. Amounts and counts in a transaction are written with thousands separators: "1,250", "200,000 CUs".
- The simulation's program log names the programs Airlock knows, with Raw for the log as the node returned it. The share dialog says what its code carries ("1 of 2 signatures: Main has signed, Cold vault has not"). The sentence about missing signatures sits under the signers, and Share is offered once at a time: on the signer's row, or as the main button when it is the next step.
- Inspect is denser. The accounts and the programs are one list each, the programs with their IDL's checksum labelled, an instruction's raw bytes open from Data, and an instruction's account rows no longer repeat the balance change.
- The share dialog makes its code as large as the window allows, opens the text from Show as text with Copy text beside it, offers the code size as Standard or Larger, has a Close button, and says what the other device does next. A legacy or v0 transaction says in a notice above its signatures why it cannot be handed to another device.
- One filled button at a time in Review and Sign and Proposals. Rebuild the transaction and Rebuild on a fresh blockhash are amber when nothing else can move the transaction on, and plain buttons otherwise; a proposal's buttons are small.
- Creating a Streamflow stream says when it starts and who can cancel it, in the sentence Review and Sign shows: its start and cliff as dates (None: when created, and at the start), and whether the sender and the recipient can cancel it or hand it to another recipient. Before, these were only under Inspect. Create a vesting or payment stream refuses a start or cliff typed in milliseconds, which would be tens of thousands of years away, and its hint gives a time in seconds to compare with.
Build and templates
- Creating a Raydium constant-product pool fills in the pool address from the fee tier and the two mints, on mainnet and devnet. The program checks that address, so the field no longer has to be typed.
- Build takes amounts in the unit the program shows them in. A SOL transfer's amount reads amount · SOL and takes 1.5, not 1500000000; a token transfer's amount takes as many decimal places as its decimals field, and a transfer fee is typed in percent. A value with more decimal places than its unit has, or too large for its field, is refused with a message rather than rounded or cut. An amount the app cannot scale without reading an account says it is in base units. Opening a transaction on Build from Review and Sign shows its amounts the same way. The accounts the program fills in itself, and arguments left to their default, fold under Filled in for you, closed, at the end of each instruction.
- Build offers a choice where an instruction takes one of a fixed set of words. An authority type on setAuthority (Token and Token-2022), the state new token accounts start in on Token-2022's default account state, a stake authority, the format of program metadata and the like were a field Build could not fill, so those instructions could not be built at all. They are now a list to pick from, and opening such a transaction on Build shows the one it holds.
- Unstake mSOL in a few days and Stake SOL with Marinade no longer say a delayed unstake is free. Marinade keeps a delayed-unstake fee from the ticket (0.2 % today; Marinade sets it), and the templates now say so.
- The NFT and token-name templates say what they cost. Create a token with a name and symbol, Add a name and symbol to a token and Create an NFT say Token Metadata keeps a 0.01 SOL fee; Create a Core NFT names Core's 0.0015 SOL fee and Mint a compressed NFT Bubblegum's 0.00009 SOL fee; and each, with Create a Core collection and Create a compressed NFT tree, gives its rent in round figures. The fees are the ones in force when written, and Metaplex can change them.
Wallets
- Wallets is quieter. A wallet's card is its name, its address and its balance with a labelled Send button, and nothing else unless something needs attention. The Use button is gone: the wallet the app acts as is picked at the top of the window. So is the Default mark on an offline or hardware key's programmatic signer or durable nonce, which only chose what that button selected: the key and its signer are separate entries in that picker. A multisig's card keeps Proposals in sight, and a card's Export public key and Remove are in a More actions menu at the end of the card. Export public keys moved into the menu at the end of the Wallets header. An empty group of wallets is a short row with its icon and what will be listed there, and the hardware one has a Turn on in Settings button.
- A wallet's settings open from the wheel on its card, on every wallet that is not a hot key: who pays its fees, an offline or hardware key's programmatic signer and durable nonce, a multisig's acting member and who approves together with it. Nothing changes until you press Save, and a dialog with a change in it says "Not saved yet". Set up, Create nonce account and a Vector wallet's steps (Rotate key, Show next key, Show account state) are there too, and still act at once. A Vector wallet that is not initialized still says so on its card, with Initialize beside it. A multisig's Pays fees says who "The member's own setting" comes to, and its Approves together with list shows all its wallets without scrolling and says what a tick does.
- A smart contract wallet's details open from the "i" on its card: a multisig's vault, multisig account, program, threshold and members, a Vector wallet's scheme and key, a programmatic signer's authority key and nonce account, and the settings as they are saved. Nothing in it can be changed.
- Send on a wallet card is a small button with a border, like Proposals beside it, on a desktop as on a phone.
- Send is off on a Vector wallet that is not initialized yet, and says why.
- SOL amounts are written with thousands separators everywhere: "1,250 SOL".
Portfolio, History, Address Book and Programs
- Portfolio is easier to read. The priced holdings are one table with column labels (In, Amount, Price, 24h, Value), where In names the wallets that hold each asset, and each group carries the colour of its part of the bar above. Every row is the same height: a verified token carries a small check after its symbol, SOL carries one as the network's own asset, and only warnings are chips. A change that rounds to 0.00% is neutral, not red or green. Avatars take letters and colours that tell tokens apart, so USDC and USDT no longer look alike. A token nothing names goes by its short mint, with a copy button, and the line under the total says how many tokens the total leaves out. "stale data" reads "outdated price", and its tooltip says what is out of date. In a folded group, a warning every row would carry shows once on the group's line. An opened asset lists the wallets that hold it on the table's own columns: a wallet's name under the asset's, its address under In with a copy button, its amount under Amount, its value under Value and its send button under the asset's, with the asset's mint as the last line. A small arrow at the end of In says a row opens, and points up once it has. A part of the bar under the total opens into what it is made of when you press it, or its name under the bar: US Dollar into USDC and USDT, SOL into SOL and its staked forms. All goes back. Manage tokens and Watched addresses moved into the menu at the end of the Portfolio header.
- Send's list of assets groups digits: "USDC · 250,000".
- An opened History entry heads its instructions "Instructions", below the page's title "Transaction".
- History's rows draw the addresses in their titles as chips, with their kind icon, name and short address, amber for one nothing names, as the rest of the app does.
- A History row names a wallet with no name by its address chip, as its title does, rather than a bare short address. Send's Max is a small button with a border at the end of the amount field, on a phone too.
- The Address Book is a table. Each entry is one row on shared columns: name with its tags, address with its copy button, and balance. With All selected the entries are grouped by kind (wallets, programs, tokens, contacts), in name order, and each filter chip shows its count. A page holds 25. Edit and Remove are in a More actions menu at the end of each row, and no longer wait for a hover.
- A wallet's count of token accounts opens them under its row, each on one line with the token, the account and the amount, written with separators and the token's symbol ("12,480.52 USDC"). A token has a small avatar of its first letters, and one nothing names says "Unknown token".
- The Address Book's groups are a bar above the list, shown from the second group on. Export and Import moved into the menu at its end.
- Programs is easier to read. The list shows each program's whole name with its short address under it, in a card that stays in place while the detail scrolls, and a filter narrows it by name or address. The selected program's name and tabs stay at the top of the detail. Instructions are one list, with a filter of their own, and each row shows the first sentence of its description and how many accounts and arguments it takes. An opened instruction shows its accounts with their flags as pills ("signer optional" where it said "either") and its arguments with their types. An argument the IDL fixes, such as a discriminator, says "fixed" with its value.
- Programs that ship with Airlock go by a display name, "Compute Budget Program" where it said "computeBudget", wherever the app names an address. The three memo programs are told apart: "Memo Program v1", "Memo Program" and "Memo Program v4".
- On desktop too, an account or a type on Programs says what it holds ("5 fields · 82 bytes") and lists each field with its type, and where an IDL was taken from is a link to its repository ("solana-program/token"). Portfolio says once, under the total, how many prices are outdated, and what the Tokens API says of every token of a group is in the group's sentence ("It lists all four as unverified"). In the Address Book, a token account's flag buttons say what each flag does. The Settings section has the wheel that a wallet's Settings has; it had sliders.
- An IDL's check state is said in words ("not compared with chain", "same as on chain", "differs from chain") with Check online beside it, and a tooltip says what was compared. Import bundle and Export IDLs (it was Export) moved into the menu at the end of the Programs header.
The whole app
- Dialogs end the same way everywhere. The way out comes first (Cancel or Close), then Clear where there is one, then the main button last, at the right: Send, New stake, Add wallet, Add address, the remove confirmation and the rest, on a desktop and on a phone alike. A browser request keeps Block site at the left, apart from Reject and Approve. A dialog that saves or sends is left by Cancel, a wallet's Settings too (it said Close or Discard); Close is for one with nothing to keep. The lock screen's Skip and Unlock sit at the right, across the full width on a phone, and no dialog has a line above its buttons.
- A page's buttons come in one order: what filters the page, then Refresh, then the main button, then the menu. On Portfolio, Send follows All wallets and Refresh; History's Refresh sits beside its wallet filter instead of under it. Refresh is called that everywhere (the Address Book said Refresh from chain), and carries its circling-arrows icon before the word on a desktop, in a multisig's proposals and an account's details too; on a phone it is the icon alone. The icon turns while it runs.
- Settings has no main button. Beside the RPC URL of a custom RPC that is in use it shows "in use" as a label, on the label's own line, where it showed a dimmed button that could not be pressed; Use this RPC, Change password and Save key are plain buttons.
- Labels on chips are lower case, as "signed" already was: "succeeded", "failed", a stake's "active", "current". "current", the wallet the app acts as, and "in use", the RPC in Settings, are drawn the same way: outlined in the app's own colour with a check before the word, so they cannot be taken for a filled label that says what a thing is ("Squads v4") or for green, which means verified or done. Programs says "built-in", as Build does.
- Airlock Offline says why it does not do something in the same words everywhere: "this app never connects". A transaction it signs that no other device can take no longer ends on "Share to submit · next": that step reads "cannot be shared". On a phone in offline mode the tab bar reads Wallets, Build, Sign, in the sidebar's order.
- The padlock in the top bar is quiet while the vault is unlocked, and amber and closed while it is locked, with the word Locked, on a desktop and a phone. Before, the desktop's was amber while unlocked. On a phone the wallet picker now keeps the wallet's short address beside its name while locked too, where it dropped it; when the bar is short of room the address is shortened first, never the name or Locked.
- The buttons that take a transaction from Send and New stake say Review and Sign (they said Review in Sign), and hints call the section by that name too. On a phone, More lists Stake, Address Book, Programs, Build and Settings, in the sidebar's order.
- The token icon is drawn as a coin on every screen; it was a plus in a circle, which read as "add".
- An empty list looks the same everywhere: an icon at the left, then a sentence that says the list is empty and what will be listed there or how to add the first ("No stake accounts yet. New stake creates one, and delegates it to a validator."), with a button at the end where there is something to do. Stake, History, Portfolio, Programs, a multisig's proposals and the Wallets pane's groups use it. Build's empty tile is laid the same way, a row with its plus at the left and Add an instruction beside it, across the Instructions column on a desktop as on a phone.
- Every unlock card has a line under its title saying what unlocking is for, the lock screen's too, and Airlock Offline adds that it never connects to every one. The lock screen also says what Skip does: it opens the app with the vault locked, in the words the Wallets pane and Portfolio use while locked.
On a phone
- On a phone, Portfolio fits a screen. A holding is two lines: the token and its name, then its value over its amount, with send at the end. A price the Tokens API calls outdated has an alert mark at its value, which a screen reader reads as "outdated price", is counted once under the total and is explained when you open the token. On a desktop the same mark leads a row's "outdated price" label and the count under the total. Manage tokens and Watched addresses are in the menu after Send, which opens as a sheet.
- On a phone, Programs is a list, then the program you open, with a way back to the list. A program leads with its name, its address and its check state above Check online; where its IDL comes from is under About this IDL. An account or a type says what it holds ("5 fields · 82 bytes") and lists each field with its type, and a long description of an instruction opens with more.
- On a phone, an Address Book entry is three lines: its name and balance, its kind, and its address, which a tap copies, beside its token accounts and its menu. The kind reads as on a desktop ("Smart contract wallet · Squads v4 · 2 of 3"), on one line shortened at its end when it does not fit, and the link reads "2 token accounts", as on a desktop. A token account shows its token and amount over the account's address, and its flags are set from its three dots, each with what it does. The groups scroll on one line. Export and Import are in the menu, which opens as a sheet; Export and Import have icons of their own, on desktop too.
- On a phone, Wallets fits more on a screen. A wallet's card is its name, its address on one line, and its balance beside Send. The three dots at its corner open a sheet named for the wallet, with Details, Settings, Export public key and Remove, and the menu beside Add wallet opens a sheet of the same kind. Details and Settings read down the page, each label above its value or control, and Add wallet's kinds are a grid. A Vector wallet that is not initialized leads with Initialize.
- On a phone, the top bar is the wallet you are acting as. It opens Act as, a sheet that lists every wallet with its kind and address in place of Android's own list, and its end copies the current wallet's address. Notifications and More open as sheets of the same kind. A locked vault shows a Locked button. The app's mark is gone from the bar, and the network line above the tabs shows only while the node does not answer or a sync failed; Settings names the cluster.
- On a phone, every page's buttons sit in one place: the title on its own line, and under it one row, in the desktop's order. Refresh is an icon in that row on Portfolio, History, Stake and the Address Book, where it was a button on some and in the menu on others. Add address moved off the Address Book's title line.
Vector wallets and programmatic signers
- A Vector XMSS wallet restored from its recovery phrase gets four attempts at moving to its next key, where it had one. If something signed before the key was lost lands first and the rotation can no longer land, scan the account state again and press Rotate key again. Its row says how many attempts are left. A device that kept its key no longer signs with the last four leaves of a key, which are kept for this.
- The key device keeps a signed key rotation until it is shown that it landed, and shows it again from its row or from Sign without signing anything. The online device says on the wallet's row when a rotation it was given has not landed, and sends it again.
- Programmatic signers work with the signer programs devnet runs since 2026-11-09. The executor now signs each advance of the nonce, so an authorization signed ahead of another can only run once the one before it has, and the nonce's authority cannot skip it. Authorizations signed before that date no longer run: sign them again.
Fixed
Review and Sign, and what a transaction reads as
- After an update, a program Airlock now ships an IDL for reads with it. Before, if an earlier version had read that program's IDL from the chain, the kept copy stayed in place and its transactions went on reading without the new sentences. An IDL you imported yourself is still yours and stays.
- A failed simulation named a program's error only by its number, such as "error 6040 (0x1798)". It now gives the message the program's IDL holds for it, with the number after, for the program that returned it, and Send refuses more SOL than the wallet can send, saying how much it can.
- A transaction too large to be sent still offered Sign and showed only the node's raw error, and Inspect measured a legacy or v0 transaction against the 4,096 bytes of a v1 one. Review and Sign and the request modal now say it is too large, against the limit of its own format (1,232 bytes for legacy and v0), say what can be done, and do not offer Sign.
- An Associated Token "Create" sent with no data, as many clients still send it, read as an instruction the stored IDL does not recognise. It now reads as creating the associated token account.
- Review and Sign showed a sentence worded by an IDL read from the chain exactly like one from an IDL that ships with the app, and Inspect called such an IDL "imported". Each instruction so worded is now marked "IDL from the chain", with a note above the instructions that whoever controls the program wrote it, and Inspect and Programs label the IDL "read from the chain" and name the file that carries a program's IDL.
- A DFlow swap that leaves out the output token keeps its sentence when you sign: who swaps, the slippage allowed and the account the output is paid to. The quoted amount and the output token are listed under it, the amount in the token's smallest units when the swap does not name the token.
- Hylo mints, redemptions, conversions and Earn Pool withdrawals made through a router no longer carry a warning that the instruction has accounts its description does not cover: the three accounts the router adds are listed under it as Additional Account.
- Jupiter's aggregator, the upgradeable BPF loader and OtterSec's verify program are labelled by name (Jupiter Aggregator v6 Program, Upgradeable BPF Loader Program, OtterSec Verify Program) where an address is labelled, instead of by their IDLs' identifiers (jupiter, loaderV3, otterVerify).
- Mint tokens and Burn now read as a sentence with the amount in whole tokens ("Mint 123456 t2 to …") in History, the Sign screen and the browser request. The online app reads the mint's decimals from your node. Before, it showed the raw amount and the accounts.
- A token whose mint claims more than 19 decimals now shows its amount correctly. Before, the amount was wrong, and a mint with 64 or more decimals could stop the app.
- Adding liquidity on PancakeSwap is no longer flagged as carrying data its IDL does not describe. Apps that lay out the base flag as two fixed bytes send an unused byte when the flag is not set; the program never reads it, so the row reads as before and a site's request can be signed from the request window.
- Launching a Token-2022 token on Raydium LaunchLab is no longer flagged as carrying data its IDL does not describe. Raydium's own SDK sends ten unused zero bytes when the token has no transfer fee; the program never reads them, so the launch reads as before and a site's request can be signed from the request window.
- The "Create an NFT" template's own mint instruction showed on Review and Sign as fourteen raw account rows, and its metadata sentence left out the collection chosen. Both now read as sentences, naming the collection when one is given.
Build and templates
- An instruction with an optional signer left out could not be signed. Build put the program's own address in its place as a signer, which nobody can sign for; it is now read only and signs nothing.
- Build no longer writes one optional value in another's place. Some instructions end in several optional values that the program reads in order, such as Pump's
buyandcreateV2and Raydium AMM v4'swithdraw. Filling a later one and leaving an earlier one blank built a transaction that the program read as the earlier one set, a holder reward as cashback or a floor for one token as a floor for the other. Build now refuses it and marks the blank field to fill first. - A template answer that cannot be used is named on its field. A royalty with more decimal places than a hundredth of a percent, a stream amount with more decimal places than the token has, a canopy that is not a whole number or text that is not an address now marks that field at once with what is wrong ("
2.555has more than 2 decimal places."), and Review and Sign and Show as blocks wait until it changes. Before, Review and Sign said only "Instruction 3 · Enter a number.", and in a template of your own whose value fed an optional field, the field was left out of the transaction. - A chain fact typed by hand on a template stays editable. When the node would not answer a rent or a mint's decimals, the field offered to type it went away after the first keystroke, keeping a one-digit value that could only be undone by closing the template. The field now stays while you type.
- A field Build cannot fill says so plainly. Its placeholder read "definedTypeLinkNode" and building it said "This field (definedTypeLinkNode) has to be filled by hand in a later slice."; it now reads "Build cannot fill this field yet", and building names the field and says to write the instruction as Raw or build it with another tool. Create a token and Add a name and symbol to a token now say that changing the name, symbol or link later takes another tool, since Build cannot write Token Metadata's update yet.
- A template that cannot be used on the network in use said why in its own variable names ("No IDL for
$token_metadata"). It now says which networks it works on and which program it needs that Airlock has no description of here.
Wallets, Address Book, Programs and Settings
- A removed wallet stayed in the Address Book as a hot wallet and was still offered to sites on Connect and Sign in. Its address now stays as a plain address, and the removal dialog says so.
- An offline wallet is called that everywhere. The Address Book and an address's card said "Cold wallet · offline key"; they say "Offline wallet · key on another device", as the Wallets pane's group does.
- A wallet's menu offered "Export key" and the Wallets menu "Export keys", though both export only public keys. They are now named Export public key and Export public keys.
- An offline wallet whose durable nonce was made on one network could not send on another ("Nonce account … does not exist"), and its Settings offered no way out. A wallet now records the network its nonce was made on and uses it there only; elsewhere its Settings and Send say so, and Create nonce account makes one for the network in use.
- Choosing Custom RPC in Settings showed the saved URL but kept reading the network in use, with nothing to say so. It now switches to the saved URL at once, Settings always says which node is in use, and a URL not yet applied says so until Use this RPC is pressed.
- Importing an IDL file or bundle replaced an IDL that ships with Airlock without saying so. Programs now asks first, naming each program it would replace, and the message after the import says what was replaced.
- The desktop app no longer closes when something comes up while a Programs file dialog is open, such as a site's request through the browser bridge. Import IDL, Import bundle and Export IDLs now open their dialog without freezing the window, and are greyed out until it closes, so a second one cannot open beside it.
- While the vault was locked, Portfolio said only watched addresses were counted, although this device's wallets were counted too.
The whole app
- Notices other than Confirmed stayed on screen until dismissed, over dialogs, and three covered half of a narrow window. A notice that only informs now leaves by itself, errors stay until dismissed, a narrow window shows only the newest with how many more, notices go under an open dialog, and every one stays in the notifications list.
- The notifications offer the same on a desktop as on a phone: Mark all read shows only with something unread, Clear only with something to clear, and the filters only once there is something to filter.
- Auto-lock now counts the time the computer was asleep. Before, a laptop closed partway through the timeout woke still unlocked on Linux and macOS, with the rest of the timeout to go. A shorter timeout chosen in Settings now applies at once instead of at the next lock cycle.
- The browser bridge keeps serving sites after a connection fails to open. Before, one failed connection stopped it until Airlock restarted.
- In an address chip, the name, the short address and a balance change sit on one line of text, the line of the sentence the chip is in. Before, the short address sat almost two pixels higher than the name and the amount beside it.
Airlock Offline and the phone's offline mode
- Airlock Offline and the phone's offline mode read mainnet transactions. They read only devnet's programs, with no way to change it, so a mainnet Kamino or Velocity transaction said "No IDL for this program". Settings now has Read transactions for (mainnet, devnet or testnet), mainnet until you choose, and Review and Sign says which network's programs it read the transaction with. A vault that was on devnet only because that was the default moves to mainnet once.
- Airlock Offline and the phone's offline mode say they are offline: "Offline · never connects" at the foot of the sidebar, a short Offline chip in the phone's top bar, and a line on the lock screen.
- Airlock Offline, and the phone's offline mode, no longer offer what needs a network. A fully signed transaction has no Submit button: Share with another device is the main button when it can be handed over, and the line under the buttons no longer says to go online. Programs has no Check online, and its tooltip says an online Airlock can compare the IDL. The Address Book has no Balance column, and its note no longer names an RPC method.
- Airlock Offline's WebView opened a connection to a Microsoft server about a minute after start on Windows, while the app said it never connects. Its WebView now starts with its background traffic turned off and nothing but loopback allowed out.
On Android
- On Android, a larger font size no longer pushes the tab bar off the screen. From one step above the default, Wallets and Build grew wider than the screen, the tab bar sat below it, and there was no way out of the pane. A tapped ? now shows its explanation across the screen, under its heading.
- On Android, changing the font size or display size no longer closes Airlock. It closed the moment the setting changed and opened cold on the lock screen; it now stays open and lays itself out again, with its text at the new size.
- On Android, Back closes what is open before it leaves. It closed the whole app, even inside a dialog, and a half-filled Build form was lost. Back now closes the open dialog, sheet or list of suggestions, then goes back from a program or a transaction to its list, and only then leaves, to the background, so the app is as you left it when you come back.
- On Android, the keyboard no longer hides the field you type in. The tab bar now steps aside while the keyboard is up, so the field the keyboard's Next key moves to is never under it, and an address field moves to the top of the screen so its suggestions show above the keyboard.
- On a phone, Build's number fields open the number keyboard: digits for a whole number, digits and a decimal point for an amount with decimals. They opened the letter keyboard.
- The keyboard no longer learns a seed phrase or private key. The fields for a seed phrase, a private key, keys from another device and a Vector recovery phrase told the phone's keyboard it could correct, capitalize and learn what was typed, and the desktop's spellchecker could read them. They now turn all of that off, and a seed's passphrase is no longer offered to a password manager.
- The Android app's window is named Airlock, which is what TalkBack reads. It was "Dioxus app".
- On Android the app now follows the phone's dark mode when its theme is System. Before, the lock screen and the app's frame stayed light.
- On Android, a site in Chrome that asks Airlock to connect through Mobile Wallet Adapter now gets the Connect request on screen. Before, on some phones Airlock came to the front and showed nothing, and the request expired: Android closed the connection as soon as Airlock opened.
- On Android, Airlock has its own icon on the home screen, in the app drawer, in recent apps and in the phone's settings: the vault door of the desktop app, in the launcher's shape, and its padlock with themed icons on. Before, it showed a placeholder.
Security
- An IDL read from the chain can only describe its own program. A Codama IDL can carry other programs beside its own, and Airlock took them from any file. A site could publish an IDL for its own program that also described another one, such as the Vote program, and a later transaction of that program read in the site's words, with the site's program nowhere in it. It could take the associated-token program's wording from the Token IDL that ships, too. An IDL read from the chain now words its own program and nothing else, and a program a shipped file carries stays with that file.
- Handing over a vote account is warned of, like handing over a stake account: authorizing a new voter or withdrawer never gets Sign in a site's request window, and Review and Sign says what it does above the instructions. A program upgrade, or a change of who can upgrade a program, gets the same warning whenever the loader's shipped IDL is not what puts it in words.
- A small Anchor IDL can no longer make Airlock use gigabytes of memory while reading it. One generic type with many fields, used many times, is refused past a limit, and that program's instructions read raw.
- An Anchor IDL whose generic type hands its own parameter to another is now read, as GMX's does with its prices. Before, reading one closed the app, and since a program's IDL is read from the chain as soon as a transaction names the program, a transaction of such a program could not be reviewed at all. An IDL whose generic types hold themselves, or expand into more than a type may hold, is refused, and its instructions read raw.
- On Linux and macOS, Airlock's data folder is now only readable by you: the folder is created
0700, so other accounts on the computer cannot read the vault, settings, site grants or logs, and the files Airlock saves are0600. It has also moved to where the platform keeps app data:~/.local/share/airlockon Linux (or$XDG_DATA_HOME/airlock),~/Library/Application Support/airlockon macOS. A folder at~/airlockfrom an earlier build is moved there on first start. - In a browser, Airlock opens in one tab at a time. A second tab says Airlock is open elsewhere instead of loading, since two tabs would undo each other's saves, including the record of used signing leaves.
- Release builds ignore
WEBVIEW2_*environment variables (andWEBKIT_INSPECTOR_SERVERon Linux), which could open a debugging port into the wallet's window or swap the browser it runs on. - The desktop app refuses a site's request whose origin is not a well-formed web address, so the request window always names the site the browser reported.
- Restoring a Vector XMSS wallet from its recovery phrase a second time now signs the same rotation with the same signature. Before, each restore made a new signature with the key's last leaf, and two of those could give the key away.
- An account state that claims more leaves than a key has is refused. Before, scanning one made the key unable to sign on that device.