OFFLINE-FIRST SIGNING CONCEPT

Your Keys.
Offline.
Your Control.

AirGap Link bridges connected and isolated devices to help you sign blockchain transactions without exposing your private keys to an internet-connected environment.

Explore the protocol How it works
PRIVATE-KEY ISOLATION SIMULATION-READY
ONLINE ENVIRONMENT
ISOLATED ENVIRONMENT
KEY BOUNDARYAIR-GAPPED CORE
UNSIGNED TX
UNSIGNED TX
SIGNED TX
KEY VAULT
ISOLATED
PRIVATE KEY
NEVER TRANSMITTED

THE PROTOCOL

Move data.
Never move the key.

A deliberate four-step flow keeps transaction preparation and private-key operations in separate environments.

01

Prepare

Create a transaction on your connected device without exposing your private key.

02

Transfer

Transfer the unsigned transaction to the isolated signing device using a supported method.

03

Sign Offline

Review transaction details and sign it on the isolated signing device.

04

Broadcast

Return the signed transaction to the connected device for network submission.

Actual signing, supported transfer methods, and blockchain compatibility depend on implementation.

BUILT AROUND SEPARATION

Security is not a feature.
It is the architecture.

Offline Transaction Signing

Keep private-key operations on an isolated signing device.

Controlled Device Communication

Design a clear communication flow between online and offline environments.

Transaction Review

Display transaction details for review before signing.

Private-Key Isolation

Design the system so private keys never need to leave the signing device.

Flexible Transfer Architecture

Explore QR codes and other supported methods for moving transaction data.

Security-First Design

Prioritize explicit confirmation, clear warnings, and separation of concerns.

INTERACTIVE PROTOCOL DEMO

See the separation
in motion.

A guided simulation of transaction data moving between environments. Nothing is signed. Nothing is broadcast.

SIMULATION ONLY — NO REAL TRANSACTIONS
DEMO / TRANSACTION_FLOW_001 LIVE SIMULATION
CONNECTED
DEVICE
NETWORK<br />READY
NETWORKDemo Network
TRANSACTIONSample Transfer
SIGNING STATUSNot Signed
BROADCAST STATUSNot Submitted
ISOLATE
& VERIFY

SECURITY PHILOSOPHY

Isolation is a
design principle.

AirGap Link is built around a simple principle: transaction preparation and private-key operations should be separated. By keeping signing on an isolated device, the architecture aims to reduce exposure to threats targeting connected environments.

01Minimize ExposureKeep sensitive key operations away from internet-connected devices.
02Verify Before SigningMake transaction details visible before the user approves an action.
03Make Security TransparentExplain the flow, assumptions, and limitations clearly.

AIRGAP LINK ARCHITECTURE

Data has a path.
Keys have a home.

Every payload is visible. The key never joins the journey.

Transaction data Private key boundary
CONNECTED DEVICEPrepare
UNSIGNED TRANSACTION PAYLOAD
CONTROLLED TRANSFER CHANNEL
OFFLINE SIGNING DEVICEPrivate key stays here
SIGNED TRANSACTION PAYLOAD
BLOCKCHAIN NETWORKBroadcast

ROADMAP

A considered path
forward.

Each phase is planned, not promised. The work starts with clear assumptions and observable behavior.

01
PLANNED

Architecture

Define device separation, transaction flow, and security assumptions.

02
PLANNED

Prototype

Build a simulated transfer interface and offline-signing workflow.

03
PLANNED

Security Testing

Test transaction validation, device communication, and signing isolation.

04
PLANNED

Compatibility

Investigate supported blockchains, formats, and device integrations.

FAQ

Clear answers.
No absolutes.

An offline-signing and device-communication concept designed to separate transaction preparation from private-key operations.

The intended architecture keeps private keys on the isolated signing device. Actual security depends on the implemented system.

Blockchain support depends on the transaction formats, signing standards, and integrations implemented.

The initial website demo is a simulation and does not perform real signing or broadcast transactions.

No. Isolation can reduce certain risks, but device compromise, malicious transaction data, implementation flaws, and other threats remain possible.