Obi Public Docs
  • FOR USERS
    • Quickstart: Using Obi
  • FOR BUILDERS
    • Obi: Cross-Chain Account and User Management
    • Dev Quickstart: Connecting Your App
    • Dev Quickstart: Building Multi-Chain Apps
    • πŸ”΅The Obi Smart Account Suite
      • πŸ”’Multikey
        • 🎣Preventing Phishing
        • πŸ“²SMS and Other Web2 Providers
        • πŸ’•Final Recovery
      • πŸ”Signet
        • Draft Signet Whitepaper
      • πŸ’•Extra Life
      • πŸ€–Automatons
      • ⏳Sessions
        • Threshold Escalation
      • πŸ§™β€β™‚οΈParty Members
        • Allowances: Hot Wallets, Budgets, and Subscriptions
        • Allow/Block/Delay Lists
      • 🧩Obi Stack Overview
      • β›½Gasless UX
      • πŸ”General Obi Features
      • πŸ“œSmart Account Design Philosophy
      • πŸ—οΈSmart Contract Architecture & Flow
    • πŸ›£οΈRoadmap: Upcoming Features
      • πŸ”§Duress Mode
      • πŸ“³Security Notifications and Lockdowns
      • βœ‹Global Transaction Limit (Sanity Limit)
      • 🌐Obi Service Providers
        • Incentivizing Service Providers
    • πŸ₯‡Obi's Unique Advantages
    • πŸ”’Multikey Attack & Loss Vectors
      • Passkey
      • Cloud Key
      • SMS Key
      • Telegram Key
      • WhatsApp Key
      • Social Recovery Key
      • Email Recovery Key
      • Ledger Hardware Key
      • Map Points Key
      • NFC Key
      • Major 2 Key Loss Vectors and Mitigations
      • Major 2 Key Attack Vectors and Mitigations
      • β€œUnlocked Obi Theft” Attack
  • Glossary
Powered by GitBook
On this page
  1. FOR BUILDERS
  2. Roadmap: Upcoming Features

Obi Service Providers

Some Obi Multikey keys currently rely on services or accounts operated or held by Obi:

  • SMS providers (Twilio)

  • Telegram bot

  • WhatsApp business license

  • CloudFlare/AWS/Netlify/Heroku services which aid recovery or boost entropy

    • Note that services are spread across providers to avoid single points of failure

These represent points where a compromised Obi Technologies could potentially be better positioned to execute an attack on a user, or where a shut down Obi Technologies could reduce users’ available paths to recovery and make certain key types impossible to use.

To correct this, a network of service providing nodes on a network will be incentivized to offer the above services, and potentially more. These can include other key types, such as fuzzy biometric authorization, but could also provide other services to smart contracts generally. Examples include:

  • IPFS pinning

  • Oracles (web and blockchain)

  • Transaction batching or scheduling

  • Off-chain compute

Fees from Obi Accounts will go to these service providers, or, more directly, a marketplace of services can be provided to contracts and bought directly when used or as a regular quota.

The fees will be distributed to service providers, and potentially to other participants or structures in future economic designs.

Entities who wish to ensure uptime for their users without relying on a third-party network of service providers can add their own in-house providers.

Incentivizing Service Providers

PreviousGlobal Transaction Limit (Sanity Limit)NextIncentivizing Service Providers

Last updated 1 year ago

πŸ›£οΈ
🌐