Permissions & operations
Connect application operations to signers, contract permissions, implementation versions and incident handling.
Separate operation permissions
Issuance, configuration and pausing depend on each contract’s roles or ownership conditions. Map application access to the actual on-chain execution permissions.
Record administrator, routine operator and incident-response addresses and permissions. Consult each source for role identifiers, administration and revocation.
Align implementation, initialization and version
Track the network, implementation address, deployed address and initial configuration together. Factory deployment selects an implementation owner, type, version and initialization data.
Registering a new implementation does not update existing contracts. Check update capabilities and authority against the actual clone or proxy architecture.
Scope signatures and delegated actions
For signed offers and vouchers, align contract, network, nonce and expiry. SmartAccount session keys can constrain target contracts and allowed operations.
Track approval, submission and confirmation separately to handle expiry and retries. Use operation IDs to prevent duplicate completion of the same business action.
Plan pausing, recovery and reconciliation
EmergencyPauseManager coordinates pause and resume calls for registered targets. Because individual calls can fail, reconcile target states and events rather than relying solely on submission success.
Define operations available while paused, who authorizes resumption and how records are reconciled with balances. Pausing does not reverse confirmed transactions.