Account Abstraction ERC-4337

Covers userOperation submission, bundling lifecycle, confirmation, and fallback handling patterns.

• Smart-account support and signer policies are implemented.
• Gas and sponsorship assumptions are defined for target environment.
• Monitoring exists for mempool acceptance and execution confirmations.

• Submission requests return userOperation hash and acceptance context.
• Status polling returns queued, bundled, executed, reverted, or dropped progression.
• Terminal failures include executable context for corrective action.

1. Construct userOperation with validated nonce, gas, and call data.
2. Submit operation and persist operation hash for tracking.
3. Monitor inclusion lifecycle through bundler acceptance and on-chain execution.
4. Apply fallback handling when operation is dropped or non-executable.

• Validation failure before bundling due to nonce, signature, or policy checks.
• Bundling delay or drop due to market conditions or capacity limits.
• Execution revert due to contract-level logic or state conditions.

Retain one logical operation identity and apply nonce-safe retry logic to avoid duplicate execution intent.

• Track time from submission to inclusion and final execution status.
• Alert on stuck queued operations beyond defined SLA windows.
• Log userOperation hash, account identifier, and failure class for every terminal failure.