Skip to content

Commit

Permalink
fix: add recommended hook execution order
Browse files Browse the repository at this point in the history
  • Loading branch information
fangting-alchemy committed Aug 30, 2024
1 parent b348dec commit 5e85f87
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions standard/ERCs/erc-6900.md
Original file line number Diff line number Diff line change
Expand Up @@ -528,6 +528,10 @@ During execution uninstallation, the account MUST correctly clear flags and othe
- the account SHOULD call `onUnInstall` on the execution module to initialize the states and track call success if required by user.
- the account MUST emit `ExecutionUninstalled` as defined in the interface for all uninstalled executions.

#### Hook execution order

It is RECOMMENDED that an account implementer runs hooks in first installed first executed order. However, an account MAY implement a different execution order.

### Validation Call Flow

Modular accounts support three different calls flows for validation: user op validation, runtime validation, and signature validation. User op validation happens within the account's implementation of the function `validateUserOp`, defined in the ERC-4337 interface `IAccount`. Runtime validation happens through the dispatcher function `executeWithAuthorization`, or when using direct call validation. Signature validation happens within the account's implementation of the function `isValidSignature`, defined in ERC-1271.
Expand Down

0 comments on commit 5e85f87

Please sign in to comment.