Account Abstraction Control Center
Review and manage Account Abstraction infrastructure from Platform settings, including the bundler wallet, paymaster status, funding controls, signer key, and recent on-chain activity.
Open the Account Abstraction Control Center from Platform settings > Infrastructure > Account Abstraction or directly at /platform-settings/account-abstraction.
The control center shows whether Account Abstraction is enabled, which infrastructure wallets are configured, whether balances need funding, and which recent on-chain events came from the bundler or paymaster. Use the page to check whether sponsored and bundled transactions have the required infrastructure: an enabled setting, a configured bundler wallet, an installed paymaster, funded balances, and a current signer key.
The page answers three operational questions:
- Is Account Abstraction enabled for this platform?
- Do the bundler and paymaster have the addresses and gas balances needed to relay and sponsor user operations?
- Which recent on-chain events came from the configured bundler or paymaster addresses?
Account Abstraction changes the transaction infrastructure, not the asset custody model. The bundler relays eligible UserOperations, and the paymaster can fund their gas through its EntryPoint deposit when sponsorship is enabled and funded. Gas costs vary by network and operation, so confirm balances against the active chain and the operation you plan to submit.
If sponsorship is unavailable, disabled, unfunded, or not applicable, the smart account needs native token balance for execution. A chain that reports zero gas still needs operational monitoring and does not change custody or policy requirements. Direct externally owned account calls and direct contract calls outside the Account Abstraction flow are outside the paymaster sponsorship path.
Treat the bundler and paymaster as shared gas and relay infrastructure. Decide separately whether investors, operators, or custody providers hold the wallets that own the assets.
Before you start
Check three things before changing Account Abstraction settings:
- Confirm your role allows the change you plan to make.
- Confirm the bundler wallet is configured before enabling Account Abstraction.
- Confirm the paymaster is installed and funded before relying on sponsored transactions.
Use the control center for infrastructure readiness. Use Operator Wallets when you need a wider view of configured operator wallet gas balances across the deployment.
Access
The page appears when Account Abstraction is available for the platform. If the feature is unavailable, DALP redirects users back to Platform settings.
| Role | What the role can do |
|---|---|
| Admin | View the page, change the Account Abstraction setting, manage paymaster enablement and funding, and rotate the paymaster signer key. |
| System manager | View the page, change the Account Abstraction setting, install the paymaster add-on, manage paymaster enablement and funding, and rotate the paymaster signer key. |
| Gas manager | View the page and manage gas operations, including paymaster enablement and funding. Signer key rotation is not available. |
| Auditor | View the page for review. Setting changes, funding, paymaster installation, and key rotation are not available. |
If the page is hidden, either Account Abstraction is unavailable for the platform or your role is outside the access list above.
Before enabling Account Abstraction in production, confirm that:
- The bundler wallet is configured.
- The bundler wallet has enough native token balance for relay operations.
- A paymaster is installed if the platform will sponsor user-operation gas.
- The paymaster has enough EntryPoint deposit balance and, where visible to your role, enough native token balance.
- The signer key shown on the paymaster card matches the operational key you expect.
- Monitoring and incident procedures cover low-balance warnings, failed balance reads, and unexpected activity.
Account Abstraction setting
The control is disabled until the bundler wallet is configured. When the bundler wallet is missing, DALP keeps the setting visible but prevents the update.
- Open Platform settings > Infrastructure > Account Abstraction.
- Review the top Account Abstraction setting.
- If you are an Admin or System manager and the bundler wallet is configured, switch the setting on or off.
- Confirm the update in the dialog.
- Wait for the page to refresh the setting and show the success message.
The setting control is disabled when your role cannot manage Account Abstraction or when the bundler wallet is not configured. If the control is disabled, hover the disabled switch to see the reason.
Bundler
The bundler card is the first operational check for Account Abstraction. It shows the wallet DALP uses for bundler infrastructure on the active network. Review these fields before you change the setting or route production traffic:
| Field | How to use it |
|---|---|
| Bundler wallet address | Copy the address when you need to fund it or reconcile it with your operator records. |
| Native token balance | Check that the wallet has enough gas for relay operations. |
| Last balance update | Confirm the balance reading is fresh enough for the decision you are making. |
| Low-balance warning | Top up the wallet before enabling Account Abstraction or continuing production traffic. |
Use Fund bundler to open a dialog with the bundler wallet address. Use View on explorer to inspect the same address in the configured block explorer.
The card warns when the bundler balance is below the configured low-balance threshold. Send native gas token to the bundler wallet, then use the last updated time to confirm the balance has refreshed.
When no bundler wallet is configured, the card shows a not-configured state and the Account Abstraction setting cannot be changed.
Paymaster
The paymaster card appears when a paymaster is installed for the platform. The card shows sponsorship infrastructure that can fund Account Abstraction transactions through the EntryPoint deposit.
Review these fields:
| Field | How to use it |
|---|---|
| Paymaster contract | Copy the address when reconciling the contract with external records. |
| EntryPoint deposit | Check the balance available for sponsored user operations. |
| Native token balance | Review the contract's native balance when your role is allowed to see it. |
| Signer key | Confirm the signer address used for sponsorship tickets. |
| Key set on | Check when the signer key was created or last rotated. |
The EntryPoint deposit is the funding source for sponsored execution. Sending native tokens to the paymaster contract deposits those tokens into EntryPoint for the paymaster.
The native token balance is a diagnostic field when it is available to your role. It is separate from the EntryPoint deposit and can stay low after a plain transfer because the paymaster deposits received tokens into EntryPoint.
When the EntryPoint deposit is below its operational threshold, use the fund button to copy the paymaster address before sending native tokens. The deposit warning clears after the next balance refresh shows enough EntryPoint funds.
Use the card controls as follows:
| Control | Who can use it | What it does |
|---|---|---|
| Enable or disable paymaster | Admin, System manager, Gas manager | Opens a confirmation dialog, then updates the paymaster enablement setting. |
| Fund paymaster | Admin, System manager, Gas manager | Opens a dialog with the paymaster address to fund. |
| Rotate key | Admin, System manager | Starts signer-key rotation. DALP may require wallet verification before applying the change. |
| View on explorer | All roles that can view the page | Opens the paymaster contract in the configured block explorer. |
Signer key rotation may require wallet verification before DALP applies the change. Gas manager users can manage paymaster funding and enablement. Only Admin and System manager users can rotate the signer key.
If the EntryPoint deposit balance or native balance shows a low-balance warning, fund the paymaster before relying on sponsored transactions. If a balance is unavailable, treat the page as inconclusive and verify the address in the block explorer or your operational monitoring before making a production decision.
Install a missing paymaster
When no paymaster is installed, the control center shows an install prompt instead of the paymaster card.
- Open the install prompt from the paymaster card.
- Go to the platform add-ons page.
- Install the paymaster add-on when your network supports it and your role has permission to install add-ons.
- Return to the Account Abstraction page and confirm that the paymaster card now shows an address, balances, signer key, and explorer link.
Users who cannot manage Account Abstraction see the install control disabled with a role requirement tooltip.
Completing the installation requires the add-on creation permission described in Install addons.
During organization setup, DALP installs the paymaster when the active network supports the paymaster add-on. If setup resumes after a partial installation and an existing paymaster is already registered, DALP reuses that paymaster and reconciles its signer key instead of creating another paymaster.
Activity
The activity log appears when a bundler or paymaster address is configured. It combines recent events from the configured bundler and paymaster addresses. Each row identifies whether the event came from the bundler or the paymaster. The newest events appear first and the log shows up to the latest 20 events across both addresses.
Use the activity log after funding, enablement, signer rotation, or configuration changes to confirm which infrastructure address produced recent on-chain activity. If you need the full transaction context, open the bundler or paymaster address in the configured block explorer from the relevant card.
If no events are listed, confirm that the relevant infrastructure address is configured and inspect the address in the configured block explorer.
The log is an operational view for infrastructure addresses, not a complete investor, token, or transaction audit export.
Operating checklist
Before using Account Abstraction in a production workflow, verify that:
- The Account Abstraction setting reflects the intended platform behavior.
- The bundler wallet is configured and funded.
- The paymaster is installed when sponsored transactions are required.
- The paymaster is enabled when sponsorship is required and funded through the EntryPoint deposit.
- The signer key is set and rotation ownership is clear between Admin and System manager users.
- Gas managers understand that they can manage paymaster gas operations but cannot rotate the signer key.
- Auditors know where to review infrastructure addresses and recent activity.
- Operational monitoring checks the same bundler and paymaster addresses shown on this page.
Use these related guides next:
- Operator Wallets for configured operator wallet gas balances across the deployment.
- Account abstraction model for the smart-account execution route that uses this infrastructure.
- Paymasters and gas sponsorship for the conceptual model behind sponsored gas.
Change admin roles
Update platform administrator roles from Platform Settings when operating responsibilities, least-privilege reviews, or wallet assignments change.
Operator wallets
Check configured operator wallet balances from the Admin area before low native token balances interrupt gas-funded platform operations.