> For the complete documentation index, see [llms.txt](https://litepaper.mopn.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://litepaper.mopn.xyz/erc-6551-account.md).

# ERC-6551 Account

## What's ERC-6551

The ERC-6551 standard originates from [eip-6551](https://eips.ethereum.org/EIPS/eip-6551), aims to give every NFT the same rights as an Ethereum user. The Token Bound Accounts (ERC-6551) is a new primitive that will give every NFT its own account/wallet address.

The standard does not require any changes to existing ERC-721 NFT smart contracts. The accounts are compatible with every existing on-chain asset standard, and can be extended to support new asset standards created in the future.

By giving every NFT the full capabilities of an Ethereum account, this account enables many novel use cases for existing and future NFTs.

## MOPN ERC-6551

In MOPN, when an NFT is used for the first time, an ERC-6551 account is automatically created. This operation does not necessarily have to be initiated by the NFT holder.

The MOPN ERC-6551 account offers a mechanism that allows owners to transfer and reclaim it at any time, unlocking greater composability and imaginative potential for NFT use cases.

With this composability and permissionless, developers can use MOPN ERC-6551 accounts in any dapps.


---

# 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://litepaper.mopn.xyz/erc-6551-account.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.