Technical DeepDive

1. User & Identity Layer

  • Social (Login/Signup): creates frictionless in-app wallets, boots the paymaster config, triggers SBT mint flow.

  • In-App Wallet: abstracted wallet UX; users do not need external wallets.

  • SBT Identity Contract: mints a non-transferable SBT as on-chain identity/DID. Used as an attestable credential for provisioning and entitlement checks.

  • Label: minimum-KYC* (asterisk → see compliance footnote).

2. Frontend (Vercel, TypeScript)

  • Handles signup/login, plan browsing, purchase flow, activation QR, device pairing, and status UI.

  • Propagates intent_id with each operation for correlation.

  • Interacts with Paymaster for gasless meta-transactions (frontend triggers payment or relayed calls).

3. Paymaster & social login Facilities

  • Paymaster: gas sponsorship for meta-txs, used for UX (user doesn’t need gas).

  • Top-up semantics: paymaster can be topped-up by user (optional) or by GeSIM (promotional). Paymaster operations are instrumented and fees (gas margin) flow to protocol revenue.

  • Feature Set (in-app wallet + top-up + key extraction option): users may optionally extract their private keys/seed phrase (explicit UX flow).

4. Backend / Orchestration (Node.js on Render + Supabase)

  • Core microservices: Intent Manager, Provisioner, Metering Engine, Smart Switch Engine, Billing Engine, Relayer Controller.

  • Supabase DB: stores only non-PII metadata (plans, intent states, profile hashes, session hashes). No PII stored (No-KYC).

  • Relayer / Indexer connector: watches on-chain events, pushes proofs to contracts, and ingests signed provisioning receipts.

5. AI Layer — Optimization & Insights (new)

  • Inputs: network telemetry (signal/QoS), active users per region, usage patterns, historical profile success, pricing data, carrier SLAs.

  • Functions: run Smart Network Switch decisions (choose best carrier + timing), price optimization (spot vs fixed), anomaly detection (fraud), predictive provisioning (pre-warm profiles).

  • Outputs: recommended carrier, switch intent, preferred pricing, real-time feed to Backend and Observability.

  • Privacy: uses hashed/aggregated signals (no PII), and can use secure enclaves/DP techniques for privacy.

6. Telecom Integration Layer

  • EsimAccess (SM-DP+): Profile creation and profile delivery.

  • SM-DP+, SM-DS, RSP: clearly represented as separate subcomponents in Telecom box:

  • SM-DP+ — Data Preparation and storage; generates encrypted eSIM profile packages.

  • SM-DS — Subscription Manager – Data Storage / Security functions (if applicable for secure descriptor storage).

  • RSP — Remote SIM Provisioning protocol used by device to fetch profiles.

  • Flows: Backend triggers SM-DP+ to prepare profiles; SM-DP+ signs provisioning receipts. RSP used by device to download. SM-DP+/SM-DS connect to carriers (MNO/MVNO).

7. Blockchain & Payments Layer

  • SBT Contract (identity) and Escrow / Intent Contract (createIntent, fundIntent, releaseToCarrier, refund).

  • Settlement Contract: merkle roots, usage commits, periodic settle.

  • Pay-on-Usage Contract: accepts usage proofs and releases payments pro-rata.

  • Safe.global: multisig treasury for protocol fees, batched payouts, and fiat conversion orchestration.

  • Stable staking (e.g., USDC pools) for liquidity providers.

  • Option: FHE / INCO (experimental): privacy-preserving payment channel to MNOs - provide as advanced feature where MNO supports FHE/INCO-style protocol for encrypted settlement (note: advanced R&D item).

8. Settlement & Billing Layer

  • Pay-as-You-Go Billing Engine: back-end microservice that aggregates usage, creates merkle roots, posts usageCommitment to chain.

  • Payout flow: Settlement contract triggers transfer to MNO address (stablecoin) → Safe.global for fiat conversion.

  • Paymaster interactions: Paymaster covers gas for users in purchase UX; fees and paymaster margin are recorded and a % flows to protocol treasury.

9. Observability / OSS-BSS / Dashboards

  • Dashboards: User, Carrier, Finance (payouts), Developer.

  • Logs: immutable signed provisioning receipts and merkle roots; store cryptographic proofs off-chain (hashed) and on-chain anchors.

  • AI telemetry feeds into dashboards for analytical views, SLAs, and enforcement.

10. External Verifiability (EigenLayer, Oracles, Relayers)

  • EigenLayer (or similar) for staking/verifiable compute to back off-chain attestations (prove relayer honesty or indexer proofs).

  • Oracles: exchange rates, sanctions lists, external compliance signals.

  • Relayers: meta-tx relayers (funded via Paymaster) to submit proofs & sign transactions.

PreviousUnique Selling Prop.NextRole of AI in GeSIM

Last updated