> For the complete documentation index, see [llms.txt](https://docs.onyx.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onyx.org/developer-guide/bridge/smart-account-integration.md).

# Smart Account Integration

Native-XCN withdrawal intents accept signatures from deployed ERC-1271 smart accounts.

## Requirements

1. `senderAddress` is the deployed smart-account contract on Onyx, not its owner EOA.
2. The contract must validate `isValidSignature(bytes32,bytes)` with the ERC-1271 magic value.
3. Register the intent before transferring XCN.
4. Read the transfer destination from the intent response every time.
5. Transfer the exact `amountAtomic` from the smart account to that destination.
6. For ERC-4337, resolve the user operation to its final execution transaction and bind that transaction hash. A `userOpHash` is not an Onyx transaction hash.

Counterfactual or undeployed accounts and ERC-6492 wrapping are not documented as supported. Test the exact account implementation before enabling a production withdrawal path.


---

# 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://docs.onyx.org/developer-guide/bridge/smart-account-integration.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.