When To Use This
Use Loyal Smart Accounts when you need one or more of these:- Multiple signers with an approval threshold
- A controlled separation between configuration and funds
- Proposal-based execution with an optional delay
- Rules around what can be spent or executed
- A TS SDK today, with a narrower Rust parity surface for create flows
If you only need a single signer wallet with no policy logic, Smart Accounts are probably unnecessary overhead.
Mental Model
Think about the system in five pieces:| Piece | What it does |
|---|---|
Settings | The configuration root for a smart account |
| Sub-accounts / vaults | The addresses that actually hold assets and execute |
| Signers + permissions | Who can initiate, vote, and execute |
| Transactions + proposals | The async governance path |
| Policies | Scoped rules for what can happen and under what limits |
1. Settings
TheSettings account is the control plane. It stores signer configuration, threshold, time lock, and other governance state.
2. Sub-accounts
Assets live in derived smart-account addresses, sometimes easiest to think of as vaults.account_index = 0 is usually the primary one.
3. Signers
Each signer has a permission mask. The important permissions are:- Initiate
- Vote
- Execute
4. Transactions and proposals
If you want review and approval before execution, you create transactions and proposals, collect votes, then execute once the threshold and time-lock rules are satisfied.5. Policies
Policies let you express narrower execution rules without giving the whole settings authority away. That is useful for spend controls, constrained program calls, and delegated operational flows.Start Here
- Read Concepts if you are new to the model
- Read Policies and Execution if you need the lifecycle and rule system
- Read TypeScript SDK if you are integrating from an app today
- Read Rust SDK if you need the current parity-first Rust surface