EGMO Token Airdrops are coming

Solana Blockchain

EdgeMob leverages the Solana blockchain as its on‑chain coordination, incentive, and governance layer—while keeping AI inference at the edge on mobile devices. It also outlines Web3 integrations, cross‑chain connectivity, and how Solana Layer‑1 security/validation underpins the ecosystem.

1) Design Goals

  • Separation of Concerns: Heavy AI compute stays off‑chain (mobile). Solana handles payments, staking, reputation, discovery, and governance.

  • Low‑Latency Coordination: Use Solana’s high throughput/finality for rapid settlement and state updates while a WebSocket control plane coordinates real‑time routing off‑chain.

  • Composable Web3 Primitives: Wallet auth (SIWS), tokenized incentives (EGMO/SPL), programmatic access via Solana Programs (smart contracts).

2) On‑Chain Programs (Solana)

  1. Staking Program

    • Accounts: Operator, Delegator, StakeVault (PDA).

    • Functions: stake(), unstake(), slash(), claimRewards().

    • Logic: Operators lock EGMO to join the decentralized gateway set; uptime/reliability affect reward weights.

  2. Rewards & Settlement Program

    • Accounts: RewardPool (PDA), Operator, JobReceipt.

    • Off‑chain oracle (EdgeMob controller) posts metered usage summaries; program mints/distributes EGMO from RewardPool according to weights.

  3. Operator Registry & Reputation Program

    • Accounts: OperatorProfile (PDA) with device class, region, caps, reliability score.

    • Functions: register(), updateProfile(), reportUptime().

    • Source-of-truth for discovery and policy‑based routing.

  4. Gateway Policy & Routing Program

    • Stores allowlists/denylists, minimum stake, regional policies, QoS tiers.

    • Off‑chain control plane queries registry + policies to route requests to eligible mobiles; receipts settle on‑chain.

  5. Governance & Treasury Program

    • SPL‑governance compatible proposal/vote/execute.

    • Treasury (PDA) funds grants, bounties, marketplace incentives; inflows from fees, slashing, marketplace rev‑share.

3) Off‑Chain Control Plane (Web2/Web3 Hybrid)

  • Session Layer (WebSockets): Binds clients ↔ gateway ↔ mobile nodes; multiplexed channels for prompt/response and streaming tokens.

  • Attestation & Signing: Nodes sign per‑job receipts; controller batches and anchors usage proofs on Solana.

  • Anti‑Fraud: Random spot‑checks, quorum verification for distributed LLM jobs; slashing evidence submitted on‑chain.

4) Payment & Metering Flow

  1. Client funds a prepay escrow (EGMO) to a Job Escrow PDA.

  2. Mobile node processes inference; emits a signed job receipt (gasless off‑chain).

  3. Controller posts usage batch → Rewards & Settlement Program.

  4. Program releases EGMO to Operator; fee split to Treasury; any overage refunded to client.

5) Web3 Integration Patterns

  • Wallet‑Gated APIs: Clients sign requests; gateway verifies ownership and policy (token balance, NFT pass, stake threshold).

  • AI Oracles: EdgeMob posts model outputs (scores, signals) on‑chain for DeFi/DeSci protocols.

  • Tokenized Model Access: Model creators set SPL‑token gates or per‑call pricing; operators opt‑in to host.

6) Cross‑Chain Connectivity

  • Bridged Access: Use Wormhole/Hyperlane (or similar) to expose EGMO payments and oracle messages to other chains.

  • Multi‑Chain dApps: Requests originate on any chain; settlement routed to Solana programs; receipts bridged back as events.

  • Data Integrity: Hash commitments of job receipts anchored on Solana; proofs referenced on destination chains.

7) Solana Layer‑1 Validation & Security

  • Economic Finality: All stake, rewards, slashing, and governance state live on Solana—secured by L1 validators.

  • Deterministic Programs: PDAs enforce state ownership; instruction constraints minimize attack surface.

  • Slashing Discipline: On‑chain evidence (quorum mismatch, failed audits, duplicate claims) triggers slash() and reputation downgrade.

  • Future ZK/TEE Hooks: Optional ZK proofs of execution or TEE attestations (e.g., Android/ARM TrustZone) can be referenced by programs to raise trust in off‑chain compute.

8) Data & Account Model (Example)

  • OperatorProfile PDA: {pubkey, stake_amt, region, hw_caps, reliability, last_heartbeat}

  • JobReceipt PDA: {job_id, client_pubkey, operator_pubkey, usage_metrics, result_hash, sig}

  • RewardPool PDA: {epoch, emission_rate, undistributed, policy}

  • Policy PDA: {min_stake, qos_tiers, allow_regions, model_allowlist}

9) Compliance Hooks

  • Optional KYC flags on OperatorProfile for regulated workloads.

  • Treasury reporting events emitted by Governance program for off‑chain analytics.

10) Developer Experience

  • TypeScript/Rust clients for all programs (IDLs), with helpers for PDAs and transactions.

  • CLI: edgemob stake, edgemob operator register, edgemob job settle.

  • Server Kits: Middleware for validating wallet signatures, deriving PDAs, posting usage batches.


Summary: Solana secures the money/state layer (stake, rewards, governance), while EdgeMob keeps AI compute at the mobile edge. Off‑chain routing + on‑chain settlement yields low‑latency UX with L1‑grade security and clear paths to cross‑chain expansion.

Last updated