AirLiftLab

Use case — files, access & USDC settlement

Illustrative workflow (Pay & Store–style)

This page walks through encrypted storage, shared access, and USDC settlement on Arbitrum—the same stack described in the overview. It is a story device (Elena & David), not a literal feature checklist.

We are not describing a live SNFT barter marketplace, IDO, or Celo / NEAR / Oasis dependency. For what ships now, open Pay & Store and StablePay.

Elena (sender / creator) and David (recipient / payer)

Stage 1: Creation & Securitization

The lifecycle begins when a standard file is transformed into a secure, sovereign digital asset with flexible storage options.

📄
🔒

Action: Elena uploads draft blueprints to Pay & Store storage, choosing a standard tier. For the final signed contract she selects a longer-lived or permanent archive tier.

Behind the Scenes: Files are encrypted and addressed with content identifiers (IPFS-style CIDs). The Free tier uses time-bounded IPFS pinning; Standard and hot legs of Pro use 0G Storage; Pro archival and Enterprise use Arweave for permanence or immutability as described in the storage tiers. Keys and access policy are enforced by AirLiftLab’s security model (including on-chain components where deployed).

Stage 2: Management & Access Control

The asset's owner now needs to share it securely without losing control.

👤
⏱️

Action: Elena grants David (david@email.com) “View Only” access to the blueprints for 7 days with a single approval.

Behind the Scenes: Permissions are recorded in AirLiftLab’s access-control layer. David can view without repeated signatures from Elena, but download rules follow policy—signature-minimized sharing where the product allows it.

Stage 3: Agreement & payment link

The parties align on scope; settlement is prepared as a dollar-quoted stablecoin payment, not a bespoke NFT swap marketplace.

🔄
🤝

Action: David confirms the deliverable. Elena issues a payment request (StablePay-style) or in-app charge for 5,000 USDC equivalent—no "SNFT barter exchange" step.

Behind the Scenes: Ownership or entitlement to the secured asset is represented and transferred through AirLiftLab’s application and smart-contract layer on Arbitrum, with Ethereum providing settlement assurances—not NEAR or unrelated chain hubs.

Stage 4: Financial Settlement

The lifecycle concludes with a seamless, cross-border financial transaction.

💰

Action: David accepts the swap and authorizes payment of 5,000 USDC (shown in dollars in the app).

Behind the Scenes: Stablecoin settlement executes on Arbitrum; batches are tied to Ethereum for final settlement policy. The app updates access rights when the trade completes—without routing through Celo, Oasis, or NEAR.

Sharing & permissions

Signature-minimized sharing and approvals are implemented in the product layer—with cryptography and policy enforcement appropriate to Pay & Store and StablePay—not via separate “AI agent hubs” on other chains.

1

User states intent

Elena chooses a high-level action in Pay & Store (for example, grant time-limited, view-only access).

2

Policy verification

AirLiftLab verifies accounts, roles, and constraints using the product security model (application logic plus on-chain checks where used).

3

Grant access

Encrypted access is updated; only the intended recipient receives decryption material after verification—without naming Oasis or NEAR as required infrastructure.

The Integrated Technology Stack

🏛️

Ethereum

The Trust Anchor for ultimate security, settlement, and liquidity.

Arbitrum L2

Fast, low-cost execution for USDC transfers and product-backed workflows.

📱

Pay & Store

Consumer and SMB surface for stable send and secure storage.

🌐

StablePay

Global payouts and invoicing runs in one click.

🛡️

USDC

Stable unit of account for user-facing dollar quotes and settlement flows.

🔗

IPFS

Trial-tier temporary pinning and content addressing so integrity stays verifiable.

📦

0G Storage

Decentralized network for Standard and Pro “hot” data—fast upload and download until you remove it.

🗄️

Arweave

Permanent and Enterprise-grade archiving—immutable retention on the permaweb.