> For the complete documentation index, see [llms.txt](https://nexabot-ai.gitbook.io/nexabot-ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nexabot-ai.gitbook.io/nexabot-ai/trading-bot/account-abstraction.md).

# Account Abstraction

Account abstraction is a concept that allows for more flexibility and extensibility in how transactions are executed and how smart contracts interact with each other.

Traditionally, transactions are initiated from externally owned accounts (EOAs), and the gas fees for executing those transactions are paid by the sender.

With account abstraction, the EVM introduces the notion of "meta transactions" and enables the separation of transaction execution logic from the underlying account structure. This means that transactions can be initiated and paid for by entities other than the sender, such as relayers or smart contracts themselves.

In the context of an EVM wallet, account abstraction allows for the creation of "meta wallets" or "contract wallets" that can act as intermediaries for executing transactions on behalf of multiple users. These wallets are smart contracts that manage the logic for processing transactions and can provide additional features such as multi-signature capabilities, access control, transaction batching, and more.

<br>

<br>


---

# 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, and the optional `goal` query parameter:

```
GET https://nexabot-ai.gitbook.io/nexabot-ai/trading-bot/account-abstraction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.