# Implementation

In the following sections, we detail how to implement your own smart account type as well as your own intents and actions using our macros.

Smart accounts can power virtually any kind of application. We have implemented Multisig and DAO versions, but the possibilities are endless! Consider AI agents, shops, gaming accounts—account.tech provides predefined building primitives that you can leverage in your own Move packages.

In addition to making our new `Account` standard modular (use the Config you want), we have also made it easily extensible (add any functionality). We demonstrate how this is accomplished in the following sections.

If you want to use or fork one of the existing implementations, you can find them in our [move-registry](https://github.com/account-tech/move-registry).

<figure><img src="https://342306357-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAIwXAmPWcA9c8KMBB0xA%2Fuploads%2FwM30FqZiNEuZY4h8npDc%2Fintent_flow.excalidraw.png?alt=media&#x26;token=1496bead-0804-4e95-970c-1b571fd48a51" alt=""><figcaption></figcaption></figure>

**Intent Flow**

1. User must authenticate by getting an `Auth` instance in the account config module.
2. Then an empty `Outcome` can be initialized for the intent.
3. A new `Params` struct must be instantiated with the common intent arguments.
4. An intent can then be created via `request_intentname()` functions within intent modules.
5. The intent must be resolved by validating the `Outcome` as defined in the account config module. (e.g. approving the intent to reach a threshold for a multisig)
6. Once the conditions are met, the intent is executed by calling the `execute_intent()` function defined in the config module. An `Executable` hot potato ensuring proper execution is returned.
7. Actions are executed sequentially by passing the `Executable` hot potato to `execute_intentname()`.
8. The `Executable` hot potato must be destroyed via `account::confirm_execution()`.
9. Optionally, if there is no "execution\_times" left, the intent can be removed with `account::destroy_empty_intent()` that returns an `Expired` hot potato.
10. This hot potato must be passed to all the delete functions of the matching actions in order to empty the action bag.
11. Finally, `intents::destroy_empty_expired()` can be called.

{% hint style="info" %}
These 10+ Move calls are all executed within a single Programmable Transaction Block (PTB), showcasing the strengths of Sui. Our composable design coupled with the power of PTBs makes this framework extremely generic and efficient.
{% endhint %}