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. The Obi Smart Account Suite

Sessions

One-click sign-in with advanced security protections.

PreviousAutomatonsNextThreshold Escalation

Last updated 1 year ago

Session keys are temporarily authorized to act. Session keys can be limited by other rules, as well, such as allow/block lists and spend limits, and are not able to take admin actions such as updating owners, extending their own lifetime, or creating other permissions. They can, however, destroy themselves.

Example Use Cases

  • β€œSave password for 30 minutes” functionality on a device. After signing once with their Multikey, users can transact without needing to sign again until the session key expires, or until they lock their device.

  • Gaming sessions. Users can sign once at the beginning of a play session, rather than upon taking any action.

  • Setting a Session Key in the User Interface (Transaction Screen)

    • Coming to Early Access very soon

    • Perform any transaction

    • Select β€œAuto sign transactions on this device for the next 30 minutes”

    • Your device now securely contains an active session key

  • Setting a Session Key in CLI/Code: Session keys are no longer their own explicit concept in the code and no longer have their own gatekeeper. Instead, simply set an expiration on any other kind of rule or rules.

πŸ”΅
⏳
obi.money