> For the complete documentation index, see [llms.txt](https://docs.veilnyx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veilnyx.com/technical-implementation/account-abstraction.md).

# Account Abstraction

Shielded Account as Smart Contract Account

Your shielded account is agnostic to any EOA from which the transaction originated. This is because transactions are not verified by a signature by EOA signature. Rather, it is verified by a ZK proof. As long as the proof is valid, the transaction is let through by the contract. The transactions sent via your Shielded Account can be relayed on-chain using a bundler and are [EIP-4337](https://eips.ethereum.org/EIPS/eip-4337) (Account Abstraction) compatible. This allows it to reap UX benefits like the user not having to sign every transaction, sponsoring gas for the user, etc, but more importantly, enhancing privacy.

Privacy is enhanced as transactions via Veilnyx default to A, avoiding paying gas fees with their EOA, which results in the appearance of their address on-chain, hampering privacy.

This setup also enables shielded accounts to pay the transaction fee in any of the supported ERC-20 tokens and integrating protocols into Veilnyx, may sponsor gas fees for their users who use Shielded Account to anonymously interact with their protocol.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.veilnyx.com/technical-implementation/account-abstraction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
