> For the complete documentation index, see [llms.txt](https://a3sprotocolcontact.gitbook.io/a3s-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://a3sprotocolcontact.gitbook.io/a3s-protocol/a3s-v1.0/how-a3s-v1.0-works.md).

# How A3S v1.0 works?

A3S Protocol creates an Address Factory Smart Contract that follows the ERC-721 or ERC-1155 standard, thereby establishing a standard for contract paradigms and address transfer methods.&#x20;

![how A3S works ](/files/GUA0qloDIMI9FjfrJs3g)

The user mints a Commander NFT from the Address Factory Smart Contract, which automatically deploys a corresponding Address Smart Contract. The owner of the Address Smart Contract points to the corresponding NFT holder. The contract can receive any type of on-chain assets and only allows the owner to send assets, that is, the Address Smart Contract will serve as the carrier for users to interact with any Blockchain dApps.&#x20;

As a result, the user who holds the NFT is holding a remote control to the Address Smart Contract. All subsequent interactions with other addresses and contracts will be completed by the NFT holder to control the Address Smart Contract. &#x20;

Meanwhile, users can transfer their NFTs through the NFT exchange market that supports the ERC-721 or ERC-1155 standard. Since the control of the Address Smart Contract is directed to the NFT, after transferring the NFT, the control of the Address Smart Contract will also be transferred.
