Back to AirPay

Who we are

An open protocol effort for resilient local value exchange.

AirPay is built around a narrow promise: keep local crypto settlement workflows usable during connectivity failure without pretending offline promises are final money.

Community surface

1Solana builders
2Wallet developers
3Local operators
4Field and event teams

Operating principles

01

Non-custodial by default

Users control wallet keys and signatures. AirPay should not be framed as a custody account or stored-value product.

02

Protocol before app

The wallet UI is the front door, but the defensible product is reserve capacity, policy, journals, claims, and settlement evidence.

03

Community-readable

The repository, demos, and docs should help builders reproduce, audit, and extend the protocol.

Who AirPay serves

Local operators

Events, markets, campuses, rural commerce, and field teams need continuity when mobile networks fail.

  • Operate through unstable connectivity
  • Sync when a device reconnects
  • Keep risk visible before handoff

Protocol contributors

Builders can improve wallet UX, transport, trust policy, journals, backend recovery, and Solana contracts.

  • Public monorepo
  • Devnet MVP evidence
  • Contribution areas mapped by module

AirPay is a devnet MVP and protocol project. Public copy should stay precise, conservative, and inspectable.