Zypp SDK

Zypp SDK is offline-first intent infrastructure for Web3 applications. It captures user intent locally, queues it securely, transfers it across nearby devices when needed, and settles it on-chain or via a developer backend once connectivity returns.

The Problem

Most Web3 products fail in practical conditions. A user on a train, in a stadium, or in a rural area with weak coverage cannot complete a transaction because the network path is unavailable. The product fails at the point of interaction rather than at the point of intent.

Traditional SDKs begin at transaction creation. Zypp SDK begins before transactions exist. It doesn't optimize blockchain execution — it optimizes everything that happens before blockchain execution becomes possible.

The Solution

Zypp SDK introduces an intent-based workflow: the system preserves the action, protects its integrity, and later settles it safely once connectivity is restored. Intents are created offline, queued locally with optional encryption, and synced when the device comes online.

The SDK is built around a Rust core with bindings for multiple platforms. The core is domain-agnostic: intent creation, queue management, synchronization, and settlement routing share no assumptions about what the intent represents.

Intent Types

Zypp SDK works with three intent types in a closed enum:

Type	Schema	Exit Target	Adjudication
Payment	SDK-fixed (amount, asset, recipient, nonce)	Solana mainnet via settlement RPC	Chain consensus
Ticket	Dev-owned free-form	Developer backend	Dev-defined validation
Action	Dev-owned free-form	Developer backend or dev-owned Solana program	Dev-defined validation

Payment is the only type with an SDK-hardcoded destination and schema. Tickets and actions are domain-varied — the SDK enforces that a validation checkpoint exists, not what the rules are.

Architecture

Application
   │
   ▼
┌─────────────────────┐
│     Zypp SDK        │
├─────────────────────┤
│ Intent Engine       │  Capture intent as structured payload
│ Transfer Layer      │  Serialize for BLE / NFC / QR
│ Local State Engine  │  Queue with content-hash dedup
│ Sync Engine         │  Connectivity-aware coordinator
│ Settlement Engine   │  Route to exit target, record outcome
└─────────────────────┘
   │
   ▼
Relayer / RPC → Solana

Zypp SDK owns the pipes and contracts. It never owns databases or domain logic — those live in the consuming application or starter templates.

Platforms

Zypp SDK is available on three platforms with identical API surfaces:

Expo (React Native) — @zypp-labs/expo-sdk for mobile applications
Unity (C#) — zypp-labs/unity-sdk for game engines
Rust Core — zypp_labs_core for desktop, server, or native apps

Security Principle

The SDK verifies integrity. It does not establish validity.

Integrity: "This data has not been tampered with since it was signed." Verified by signatures, content hashes, and MACs.
Validity: "This data represents a legitimate, authorized action." Established by the issuer backend, settlement layer, and application policy.

No intent type exits the pipeline without passing through both an integrity check and a validity checkpoint.

Next Steps

Continue to the Quickstart to create your first intent in under five minutes.