Repository navigation
Airlock 0.3.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.3.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.3.0-windows-x64-setup-full.exe: the same, with WebView2 inside (about 190 MB more) |
| Windows, Airlock, without installing | airlock-0.3.0-windows-x64-portable.zip: unzip and run airlock.exe |
| Windows, Airlock Offline | airlock-offline-0.3.0-windows-x64-setup.exe needs WebView2 already, as Windows 11 has it. airlock-offline-0.3.0-windows-x64-setup-full.exe has it inside, for a machine that has never been online. airlock-offline-0.3.0-windows-x64-portable.zip runs without installing |
| Mac with Apple Silicon | airlock-0.3.0-macos-arm64.dmg, airlock-offline-0.3.0-macos-arm64.dmg. Intel Macs are not built |
| Debian, Ubuntu and their kin, x86-64 | airlock-0.3.0-linux-amd64.deb, airlock-offline-0.3.0-linux-amd64.deb |
| Other x86-64 Linux | airlock-0.3.0-linux-x86_64.AppImage, airlock-offline-0.3.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.3.0-android-arm64.apk: online or offline, chosen in the app |
| Signing for websites in Chrome, Edge or Brave | airlock-extension-0.3.0.zip, with Airlock on the same computer. See the browser extension |
| The browser bridge on its own | bridge-host-0.3.0-windows-x64.exe, bridge-host-0.3.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.3.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.3.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.3.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.3.0-linux-amd64.deb # Linux
shasum -a 256 airlock-0.3.0-macos-arm64.dmg # macOS
Get-FileHash airlock-0.3.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.3.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.3.0
Before you update
- Vector wallets made before this release no longer work. The devnet Vector program was upgraded to Vector 2.0 on 2026-11-14, and their accounts were left behind by the upgrade: anything still in one cannot be moved out. Add the wallet again and initialize its new account.
Changed
- Vector wallets use Vector 2.0. An Ethereum wallet's
personal_signfor a Vector wallet now signs 39 bytes,vector:and the digest, as the Sign screen shows.
Fixed
- On Android, Airlock no longer stops drawing after you come back to it. Returning to Airlock from another app could leave it taking taps and changing nothing on screen, for seconds or longer. It was not waiting on the node or on prices. On a phone that cuts the network of an app in the background, as a Galaxy does, what Airlock sent its own page meanwhile was lost, and sent again only after a wait, during which the page stayed as it was: Airlock now sends its page nothing while it is in the background. And on any phone, a request to draw that arrived together with Android's notice that the app was in front again could be left waiting.
- On Android, answering a site's request takes you back to the site. After you approved or rejected a connection or a signature a page in the browser asked for, Airlock stayed on screen with nothing to say it had worked, and the page waited behind it. On some phones, a Galaxy among them, a page in a browser that is not in front hears nothing, so it never got the answer and the site stayed unconnected. Airlock now steps back as soon as the request is answered, as it already did for a request from another app.
Security
- A Vector wallet's authorization expires about an hour after Airlock makes it, so a relay can no longer hold it back to land it later, and one that failed on chain cannot be landed again much later by anyone. The Sign screen says until which slot it holds. One a Winternitz or XMSS wallet signs never expires, since replacing it would take a second signature from the same key.
- A Vector key signs
vector:and then the digest, never a bare 32-byte digest, so a signature it made for anything else can never authorize a Vector account. Sites can no longer have a message that starts withvector:signed, and a 32-byte message may be signed again. - A Vector wallet cannot be made for a key that cannot sign: an Ed25519 key of small order or written in a second encoding, which anyone could sign for, or a secp256k1 key that is not on the curve. The program refuses them too.