> For the complete documentation index, see [llms.txt](https://docs.qorechain.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qorechain.io/developer-guide/account-abstraction.md). # Account Abstraction QoreChain provides **protocol-level account abstraction** through the `x/abstractaccount` module. This enables programmable accounts with flexible authentication rules, session keys, spending limits, and social recovery -- all without requiring external smart contract infrastructure. ## Overview Traditional blockchain accounts are controlled by a single private key. Account abstraction decouples the concept of "who can authorize a transaction" from a single cryptographic key, enabling: * **Multisig accounts** with configurable threshold signing * **Social recovery accounts** with guardian-based key recovery * **Session-based accounts** with granular, time-limited permissions for dApps The `x/abstractaccount` module implements these capabilities at the protocol layer, meaning they work across all three VMs (EVM, CosmWasm, SVM) and benefit from native gas efficiency. ## Account Types | Type | Description | Use Case | | ----------------- | --------------------------------------- | ------------------------------ | | `multisig` | M-of-N threshold signing | DAO treasuries, shared wallets | | `social_recovery` | Guardian-assisted key recovery | Consumer wallets, onboarding | | `session_based` | Delegated session keys with constraints | dApp sessions, mobile wallets | ## Creating an Abstract Account ### Session-Based Account ```bash qorechaind tx abstractaccount create \ --account-type session_based \ --from mykey \ --gas auto \ -y ``` ### Multisig Account ```bash qorechaind tx abstractaccount create \ --account-type multisig \ --signers qor1alice...,qor1bob...,qor1carol... \ --threshold 2 \ --from mykey \ --gas auto \ -y ``` ### Social Recovery Account ```bash qorechaind tx abstractaccount create \ --account-type social_recovery \ --guardians qor1guardian1...,qor1guardian2...,qor1guardian3... \ --recovery-threshold 2 \ --from mykey \ --gas auto \ -y ``` ## Session Keys Session keys are the cornerstone of the `session_based` account type. They allow you to grant **temporary, scoped permissions** to a secondary key -- perfect for dApp interactions where you do not want to expose your primary key. ### Key Properties | Property | Description | | --------------------- | ---------------------------------------------------- | | **Permissions** | Which message types the session key can sign | | **Expiry** | Automatic expiration after a configurable duration | | **Spending limits** | Maximum amounts the session key can spend | | **Allowed contracts** | Restrict interactions to specific contract addresses | ### Grant a Session Key ```bash qorechaind tx abstractaccount grant-session \ --session-key qor1sessionkey... \ --permissions "bank/MsgSend,wasm/MsgExecuteContract" \ --expiry "2026-03-01T00:00:00Z" \ --allowed-contracts qor1contract1...,0x1234...abcd \ --from mykey \ -y ``` ### Revoke a Session Key ```bash qorechaind tx abstractaccount revoke-session \ --session-key qor1sessionkey... \ --from mykey \ -y ``` ### List Active Sessions ```bash qorechaind query abstractaccount sessions ``` ## Spending Rules Spending rules add financial guardrails to abstract accounts, regardless of account type: | Rule | Description | | ---------------- | ----------------------------------------------- | | `daily_limit` | Maximum total spend per 24-hour rolling window | | `per_tx_limit` | Maximum spend per individual transaction | | `allowed_denoms` | Restrict which token denominations can be spent | ### Set Spending Rules ```bash qorechaind tx abstractaccount update-spending-rules \ --daily-limit 1000000000uqor \ --per-tx-limit 100000000uqor \ --allowed-denoms uqor \ --from mykey \ -y ``` ### Query Current Rules ```bash qorechaind query abstractaccount spending-rules ``` ### Example Response ```json { "daily_limit": { "denom": "uqor", "amount": "1000000000" }, "per_tx_limit": { "denom": "uqor", "amount": "100000000" }, "allowed_denoms": ["uqor"], "daily_spent": { "denom": "uqor", "amount": "250000000" }, "window_reset": "2026-02-27T00:00:00Z" } ``` ## Querying Abstract Accounts ### CLI ```bash # Get full account configuration qorechaind query abstractaccount account
# List all abstract accounts (paginated) qorechaind query abstractaccount list --limit 10 ``` ### JSON-RPC ```bash curl -X POST http://localhost:8545 \ -H "Content-Type: application/json" \ -d '{ "jsonrpc": "2.0", "method": "qor_getAbstractAccount", "params": ["0xYourAddress"], "id": 1 }' ``` ### Example Account Response ```json { "address": "qor1myaccount...", "account_type": "session_based", "owner": "qor1owner...", "active_sessions": 2, "spending_rules": { "daily_limit": "1000000000uqor", "per_tx_limit": "100000000uqor", "allowed_denoms": ["uqor"] }, "created_at_height": 54321 } ``` ## Social Recovery Flow If the account owner loses access to their primary key, guardians can authorize a key rotation. {% stepper %} {% step %} ### Owner reports lost key (or a guardian initiates) ```bash qorechaind tx abstractaccount initiate-recovery \ --account \ --new-owner qor1newkey... \ --from guardian1 \ -y ``` {% endstep %} {% step %} ### Additional guardians approve (must meet `recovery_threshold`) ```bash qorechaind tx abstractaccount approve-recovery \ --account \ --recovery-id \ --from guardian2 \ -y ``` {% endstep %} {% step %} ### Recovery executes automatically once the threshold is met A **time-lock period** (default: 48 hours) gives the original owner a chance to cancel a fraudulent recovery attempt. {% endstep %} {% endstepper %} ## Integration with dApps Session keys enable seamless dApp experiences: 1. **User connects wallet** and creates a session key scoped to the dApp's contract 2. **dApp uses session key** to submit transactions on behalf of the user 3. **No repeated signing** -- the session key handles authorization within its permissions 4. **Session expires** automatically, or the user revokes it at any time This pattern is especially useful for: * Mobile wallets where repeated biometric prompts are disruptive * Gaming dApps that need rapid transaction signing * DeFi protocols that execute multiple sequential operations ## Next Steps * [Running a Validator](broken://pages/4da6ac9ceb6ef4008955f97b79504a480510f5a3) -- Set up and operate a validator node * [EVM Development](broken://pages/77165eb8a7fa0ade0820d31a8f8919bf39b28c9f) -- Integrate abstract accounts with Solidity dApps * [Cross-VM Interoperability](broken://pages/f230af5f198d32323f97e29863d5cc9146006931) -- Cross-VM messaging with abstract accounts --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.qorechain.io/developer-guide/account-abstraction.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.