Intents
Understanding how intents drive state transitions in Grid
Grid uses an intent-based architecture for operations that originate from the smart account, such as payments and policy changes. This design ensures security and control over all outgoing operations. Operations that don’t originate from the smart account, like KYC verification, virtual account creation, and onramping, follow a simpler direct process.
How Intents Work
An intent represents a desired state change that originates from the smart account. Each intent follows a consistent lifecycle:
- Creation: The intent is created with the desired state change
- Authorization: Required authorities must approve the intent
- Confirmation: The intent is confirmed with necessary signatures
- Execution: The state change is executed on the blockchain
Operations That Require Intents
Intents are required for operations that originate from the smart account:
Payment Intents
- Outgoing transfers to external accounts
- Recurring payments initiated by the smart account
- Direct debits authorized by the smart account
Policy Intents
- Updating authority permissions
- Modifying threshold requirements
- Changing time locks
Direct Operations
The following operations don’t require intents as they don’t originate from the smart account:
Account Setup
- Smart account creation
- KYC verification
- Virtual account creation
Incoming Operations
- Onramping funds
- Incoming transfers
- Direct debit collections
Intent Authorization
Each intent requires authorization from the appropriate authorities based on the smart account’s policies. The authorization process ensures that:
- Only authorized parties can initiate state changes
- Multiple authorities can be required for sensitive operations
- Time locks can be enforced for additional security
- All operations are auditable and traceable
For detailed information about the authorization process, see the Authorization Guide.