Account abstraction model
How DALP uses smart accounts, UserOperations, EntryPoint routing, bundlers, paymasters, and validators without replacing identity or compliance controls.
Account abstraction lets a DALP participant execute transactions through a smart account instead of sending every transaction directly from an externally owned account. The model changes the execution path. It does not replace participant identity, asset policy, custody approval, or transaction outcome checks.
How the layers fit together
Account abstraction has several layers. Each layer answers a different question in the transaction path.
| Layer | Question it answers | DALP behaviour |
|---|---|---|
| Participant | Who is acting in the platform? | DALP keeps the participant, organisation scope, roles, and identity model separate from the executor wallet. |
| Smart account | Which on-chain account executes the call? | A smart account is an account contract deployed through the account factory and used as the transaction executor. |
| UserOperation | What does the account abstraction transaction request contain? | DALP builds the operation that the smart account validates and the EntryPoint executes. |
| Validator module | Who is allowed to approve this operation? | Installed validators enforce the smart account's signing rules. Multisig thresholds use signer weights, not a simple signer count. |
| Bundler | Who submits valid operations to the chain? | The bundler accepts and simulates UserOperations, then submits valid operations to the configured EntryPoint. |
| EntryPoint | Which contract coordinates validation and execution? | The EntryPoint receives UserOperations, calls the smart account validation path, and executes the requested call when validation succeeds. |
| Paymaster | Who can sponsor gas? | A funded and enabled system paymaster can sponsor eligible account abstraction transactions. Otherwise the smart account needs enough native token balance. |
What changes for transaction execution
With account abstraction, the smart account becomes the on-chain executor. DALP still applies platform checks before submission, then the smart account and EntryPoint handle the account abstraction validation path.
A typical flow is:
- The caller selects a participant and an executor route.
- DALP builds a UserOperation when the route uses a smart account.
- The validator module checks the configured signer or multisig authorisation.
- The bundler simulates the UserOperation and submits it to the EntryPoint.
- The EntryPoint calls validation and executes the requested operation when validation succeeds.
- DALP transaction tracking, indexing, and webhooks report the resulting chain outcome.
What account abstraction does not replace
Account abstraction is an execution model, not a compliance or custody shortcut.
| Control | Relationship to account abstraction |
|---|---|
| Identity and claims | The participant identity remains the compliance subject. A smart account can execute a transaction without becoming the participant identity model. |
| Asset policy | Transfer, mint, and eligibility rules still come from the configured asset contracts and compliance modules. |
| Platform roles and API access | DALP still checks organisation scope, API permissions, and role requirements before submitting platform-managed work. |
| Custody policy | Custody provider and HSM approval rules stay separate from the smart account validator model unless the deployment connects them deliberately. |
| Transaction status | Integrations still need transaction tracking, indexed state, or subscribed webhooks after submission. |
Production checks
Before relying on account abstraction in a regulated workflow, verify the operational surfaces that control execution.
| Check | Where to verify it |
|---|---|
| Supported EntryPoint | Call the Bundler JSON-RPC reference with eth_supportedEntryPoints. |
| Smart wallet signers and threshold | Use the Smart wallets API guide. |
| Paymaster funding and enablement | Use System paymasters or the Account Abstraction Control Center. |
| Transaction completion | Use Transaction tracking after the operation is submitted. |
Related pages
- UserOperations for the smart-account request model
- Bundlers for the submission layer
- Paymasters and gas sponsorship for sponsored gas checks
- Account abstraction architecture for the infrastructure component view
- Smart wallets for signer, threshold, validator, and wallet endpoints
- Bundler JSON-RPC for supported EntryPoint discovery behaviour
- Signing flow for custody and approval sequencing