Account.tech is an open-source framework on the Sui blockchain that introduces Smart Accounts highly fl exible, secure, and customizable account objects that can execute on-chain actions through a modular, intent-based architecture.

Think of it like programmable wallets with native support for multisig, DAO logic, scheduled execution, dynamic access control, and more.

Why Smart Accounts?

Traditional accounts are just passive containers. They hold assets and sign transactions. Smart Accounts are active, programmable entities that can define ownership logic, automate workflows, and manage assets based on rules.

With Account.tech, these rules live on-chain, are customizable through Move modules, and are enforced via Intents.

Key Concepts

Smart Account Struct

public struct Account<Config> has key, store {
    id: UID,
    metadata: Metadata,
    deps: Deps,
    intents: Intents,
    config: Config,
}

A Smart Account is a shared object containing:

• Metadata: descriptive info
• Deps – dependency packages used
• Intents – pending or active requests to perform actions
• Config – the custom ruleset (e.g., multisig, role-based, DAO logic)

Each account has a unique Config module that determines how intents are resolved.

Intent-Based Execution

An Intent is a structured request to perform one or more on-chain actions. It progresses through 3 stages:

• Request the user creates the intent with actions
• Resolution – the config module checks if conditions are met
• Execution – anyone can execute the intent when it’s valid

Example: a multisig intent to transfer funds will only execute once enough members have approved it.

⸻

3. Actions = Modular Execution Units

Each action is a standalone Move struct, like:

struct WithdrawAction { object_id: ID }
struct TransferAction { recipient: address }

You can compose multiple actions in one intent. For example:

Withdraw → Transfer → Withdraw → Transfer

This enables advanced workflows — like atomic swaps, batch transfers, time-based vault releases, etc.

Config: Customizable Ownership Logic

The Config type defines how intents are resolved. You can plug in logic such as:

1. ✅ Multisig with weighted votes
2. 🔐 Role-based access control
3. 🗳 DAO voting logic
4. ⏳ Time delays or recurring tasks
5. 💾 Recovery flows

Each intent tracks an Outcome, which represents resolution status (e.g., votes collected, approvals granted, etc.).

Learn More

1. 🔗 Docs: https://account-tech.gitbook.io/docs
2. 🧑‍💻 GitHub: https://github.com/account-tech