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
  3. Signet

Draft Signet Whitepaper

PreviousSignetNextExtra Life

Last updated 1 year ago

Signet works by allowing account abstraction logic to be applied gaslessly and immediately at the signing step of the transaction flow, rather than at the target chain transaction step. Account abstraction rules are checked by the smart account without adding additional target chain execution cost or additional latency. If an active account abstraction rule is matched, including but not limited to these examples:

  • the actor is the account owner, using multi-factor authentication

  • the actor is an active session key (Sessions)

  • the actor has an active budget (Party Members)

  • the actor is an inheritor, and inheritance is active (Extra Life)

then the transaction signature is finalized and can broadcasted to the destination chain (e.g. Ethereum or Cosmos Hub).

From the user’s perspective, they simply submit an Ethereum (or Cosmos Hub) transaction in a dapp, using a normal address and normal Ethereum/Cosmos Hub assets. The smart account layer’s participation as account abstraction rule enforcer does not need to be visible to the user.

From Ethereum’s (or Cosmos Hub's) perspective in this example, an private key signed a simple transaction. However, account abstraction rules were applied on a different layer, saving gas and enabling functionality which is not yet natively available on Ethereum.

Read more in the draft :

πŸ”΅
πŸ”
Signet Whitepaper
EOA