ArchitectureConcepts
UserOperations
How UserOperations carry smart-account transaction requests through DALP's account abstraction execution path.
A UserOperation is the ERC-4337 transaction request that a smart account validates before the configured EntryPoint executes it. In DALP, UserOperations belong to the account abstraction execution path. They do not replace participant identity, asset policy, custody approvals, or transaction outcome tracking.
Where UserOperations sit
UserOperations connect the API or operator action to the smart account execution path:
- DALP selects the participant and executor route for the request.
- When the route uses a smart account, DALP builds a UserOperation for the requested chain action.
- The smart account validator checks whether the configured signer or multisig policy authorises the operation.
- The bundler simulates and submits the valid UserOperation to the EntryPoint.
- DALP reports the resulting transaction through transaction tracking, indexing, and webhook events.
What to verify
| Question | Where to verify it |
|---|---|
| Which smart wallet can execute the operation? | Smart wallet API overview |
| Which signers or thresholds authorise the operation? | Smart wallet approvals and Smart wallet thresholds |
| Which EntryPoint receives supported operations? | Bundler JSON-RPC |
| How do integrations confirm completion? | Transaction tracking |
Related pages
- Account abstraction model for the full execution model
- Bundlers for the submission layer
- Paymasters and gas sponsorship for sponsored gas checks