Practical overview
When it fits
Use it when private-key generation and signing need to take place on a dedicated smartphone that remains disconnected from networks, with a separate connected phone handling transaction preparation.
Who it is for
- Crypto users seeking offline private-key storage.
- Users adopting a two-device self-custody workflow.
- Developers examining an MIT-licensed TypeScript mobile wallet project.
Documented uses
- Generate private keys with device random data and additional sensor-based entropy.
- Store secrets in the device secure enclave behind biometric authentication.
- Create accounts for supported crypto protocols.
- Sign transactions offline and exchange transaction data with AirGap Wallet through QR codes.
Requirements & limits
The repository documents Android and iOS applications and links to Google Play and the App Store. It identifies the project as public, active and MIT-licensed.
- A second smartphone is central to the documented architecture: Vault runs on the offline device and AirGap Wallet runs on the connected device.
- The private key is intended to remain on the Vault device during the QR-based transaction flow.
- The project uses TypeScript and Capacitor for a shared Android and iOS codebase.
- The README names support for Bitcoin, Ethereum, Tezos, Cosmos, Kusama, Polkadot, Groestlcoin and Aeternity, while noting that the complete workflow may vary by protocol.
- The repository describes secure-enclave storage and biometric access as part of its design.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up the documented two-device wallet architecture
Create the offline Vault and connected Wallet arrangement described by the project.
Before you start
- A dedicated Android or iOS smartphone for AirGap Vault
- A separate everyday smartphone for AirGap Wallet
- The Vault device must have no connection to any network
Steps
Install AirGap Vault on the dedicated offline smartphone.
Install the separate AirGap Wallet application on the everyday smartphone.
Use AirGap Wallet to prepare a transaction and transfer it to Vault by QR code.
Sign the transaction on the offline device and return it to AirGap Wallet through another QR code.
Expected outcome
A two-device arrangement in which Vault handles offline key storage and signing while Wallet handles connected transaction preparation.
Guide limitations
- The supplied README describes the architecture but does not establish a complete workflow for every listed asset or transaction type.
- This is source-based guidance, not a security audit or execution test.
Build the documented local development project
Install dependencies and open the native Android or iOS project from the TypeScript codebase.
Before you start
- Node/npm environment
- Capacitor CLI
- Xcode for iOS or Android Studio for Android
Steps
Install the Capacitor CLI with npm.
Install the project dependencies with npm.
Run the documented build command and synchronize the Capacitor project.
Open the iOS or Android project in the corresponding native development environment.
Expected outcome
A locally prepared native project that can be opened in Xcode or Android Studio.
Guide limitations
- The documented steps cover setup and project opening, not a verified build result or deployment.
- The source does not specify operating-system versions or hardware requirements.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 2 October 2026
- Original website title
- airgap-it/airgap-vault · Official homepage title · retained in its source language