GeSIM ID - Wallet & Identity

One eSIM for the world

GeSIM ID is a wallet-first, non-transferable SBT that ties your eSIM entitlement to your wallet — enabling instant carrier provisioning, purchase authentication, and privacy-preserving billing without re-sharing PII (GDPR-compliant).

How the eSIM map works (quick reference)

• eSIM ID (top-level) — one global identifier stored on device and referenced by the SBT, maps to multiple profiles.

• Profile (1..N) — each profile holds carrier bindings: ICCID, masked MSISDN, IMSI (hashed or vaulted), carrier_id, region, plan metadata, and QoS tag (e.g., chat-optimized, Video streaming).

• Active profile — only one active at a time; device + orchestration mark which profile is pushed to the eUICC.

• Switching logic — combines wallet QoS preference + runtime metrics (latency, throughput, cost) to pick the most relevant local carrier — not just the strongest signal.

• Off-chain vaulting — full IMSI/MSISDN stay encrypted off-chain; the SBT carries hashes/pointers and provisioning tokens — not raw PII.

User flow (what happens, step-by-step)

1. Buy / Entitle — user purchases a plan; GeSIM issues the SBT (GeSIM ID) to the wallet.

2. Authenticate — wallet signature proves ownership no PII exchange.

3. Provision — orchestration issues a provisioning token to MVNE/MNO chosen profile is written to the eUICC.

4. Activate — device activates the profile; traffic routes through the carrier.

5. Bill & Settle — usage is recorded with privacy-preserving meters, settlement happens off-chain (stablecoin or fiat rails) without repeatedly exposing PII.

Developer mapping — suggested SBT metadata (example)

{
  "esim_id": "89234567890123456789012345678145",
  "owner_wallet": "0xAB...123",
  "entitlement_id": "GES-ENT-0001",
  "profiles": [
    {
      "sim_id": 2,
      "iccid": "ICCID_2",
      "msisdn_masked": "+***-***-*123",(optional)
      "imsi_hash": "sha256:...",
      "qr_url": "carrier_2",
      "region": "PT",
      "status": "active"
    }
  ],
  "issued_at": "2025-09-27T00:00:00Z",
}

Privacy & compliance (straight to the point)

• Non-transferable SBT reduces resale/fraud.

• No PII on-chain — only metadata, hashes, and secure pointers.

• GDPR posture — access/erase handled via off-chain controller; on-chain token only proves entitlement.

• Least privilege — carriers get provisioning tokens, not raw user identities.