# Advanced accounts control center

Source: https://docs.settlemint.com/docs/operators/platform-setup/advanced-accounts-control-center
Review and fund the gas reserves behind advanced accounts from Organisation settings, including the submission reserve, sponsorship reserve, signer key, and recent on-chain activity.



Open the advanced accounts control center from **Organisation settings > Operations > Advanced accounts** or directly at `/platform-settings/transaction-funding`.

**Requires:** advanced accounts enabled for the deployment.

This page is where you monitor and fund the two gas reserves that keep advanced accounts working. The submission reserve covers getting transactions on-chain (backed by the bundler wallet), and the sponsorship reserve funds gasless transactions (backed by the paymaster's EntryPoint deposit). For what each reserve does and why they are separate, read [Gas reserves](/docs/operators/platform-setup/gas-reserves). For the operational tasks, read [Gas reserves operations](/docs/operators/runbooks/gas-reserves-operations).

The control center shows whether Advanced accounts 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 address, an installed paymaster, funded balances, and a current signer key.

If the page reports that the bundler wallet address is not configured, treat that as an incomplete Advanced accounts provisioning state. Complete the platform or system deployment step that provisions the organization bundler wallet before relying on the balance and funding controls. The bundler wallet address is organization scoped; do not substitute a paymaster, investor, or custody wallet for it.

The page answers three operational questions:

1. Is Advanced accounts enabled for this platform?
2. Do the bundler and paymaster have the addresses and gas balances needed to relay and sponsor user operations?
3. Which recent on-chain events came from the configured bundler or paymaster addresses?

Advanced accounts 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 Advanced accounts 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 [#before-you-start]

Check three things before changing Advanced accounts settings:

1. Confirm your role allows the change you plan to make.
2. Confirm the bundler wallet is configured before enabling Advanced accounts.
3. Confirm the paymaster is installed and funded before relying on sponsored transactions.

Use the control center for infrastructure readiness. Use [Operator Wallets](/docs/operators/platform-setup/operator-wallets) when you need a wider view of configured operator wallet gas balances across the deployment.

## Access [#access]

The page appears when Advanced accounts is available for the platform. If the feature is unavailable, DALP redirects users back to Organisation settings.

| Role           | What the role can do                                                                                                                                             |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Admin          | View the page, change the Advanced accounts setting, manage paymaster enablement and funding, and rotate the paymaster signer key.                               |
| System manager | View the page, change the Advanced accounts 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 Advanced accounts is unavailable for the platform or your role is outside the access list above.

Before enabling Advanced accounts 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.

## Advanced accounts setting [#advanced-accounts-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.

1. Open **Organisation settings > Operations > Advanced accounts**.
2. Review the top **Advanced accounts** setting.
3. If Advanced accounts is not enabled yet, confirm that an Admin or System manager has configured the bundler wallet.
4. Switch the setting on and confirm the update in the dialog.
5. Wait for the page to refresh the setting and show the success message.

Advanced accounts is a one-way platform setting. After DALP stores it as enabled for the organisation, the platform rejects attempts to turn it off.

New organisation deployment also preserves an enabled value on retry. Operators should treat enablement as a production infrastructure decision rather than a temporary toggle.

The setting control is disabled when your role cannot manage Advanced accounts or when the bundler wallet is not configured. If the control is disabled, hover the disabled switch to see the reason.

## Bundler [#bundler]

The bundler card is the first operational check for Advanced accounts. 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 Advanced accounts 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 Advanced accounts setting cannot be changed.

## Paymaster [#paymaster]

The paymaster card appears when a paymaster is installed for the platform. The card shows sponsorship infrastructure that can fund Advanced accounts 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.

Read the signer-key fields as an operational status check:

| Status shown                                 | How to read it                                                                                                                                                                                                              |
| -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Signer key address is visible                | DALP resolved the current paymaster signer wallet and shows the address that should match your operator records.                                                                                                            |
| Signer key is empty                          | DALP could not resolve a current signer address from the configured signing backend. Treat the paymaster as not ready for sponsored production traffic until an Admin or System manager rotates or rechecks the signer key. |
| Key set on shows the paymaster creation date | The paymaster is installed, but no later signer-key rotation timestamp is recorded. Use the date as the initial key-age reference.                                                                                          |
| Key set on updates after rotation            | The signer-key rotation has completed and DALP has recorded the new active key timestamp.                                                                                                                                   |

Signer-key rotation may be queued while the on-chain signer update confirms. If DALP reports that rotation is still pending, wait for confirmation and retry the action or refresh the control center before rotating again.

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 [#install-a-missing-paymaster]

When no paymaster is installed, the control center shows an install prompt instead of the paymaster card.

1. Open the install prompt from the paymaster card.
2. Go to the platform add-ons page.
3. Install the paymaster add-on when your network supports it and your role has permission to install add-ons.
4. Return to the Advanced accounts page and confirm that the paymaster card now shows an address, balances, signer key, and explorer link.

Users who cannot manage Advanced accounts see the install control disabled with a role requirement tooltip.

Completing the installation requires the add-on creation permission described in [Install addons](/docs/operators/system-addons/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 [#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 [#operating-checklist]

Before using Advanced accounts in a production workflow, verify that:

1. The Advanced accounts setting reflects the intended platform behavior.
2. The bundler wallet is configured and funded.
3. The paymaster is installed when sponsored transactions are required.
4. The paymaster is enabled when sponsorship is required and funded through the EntryPoint deposit.
5. The signer key is set and rotation ownership is clear between Admin and System manager users.
6. Gas managers understand that they can manage paymaster gas operations but cannot rotate the signer key.
7. Auditors know where to review infrastructure addresses and recent activity.
8. Operational monitoring checks the same bundler and paymaster addresses shown on this page.

Use these related guides next:

* [Gas reserves](/docs/operators/platform-setup/gas-reserves) for what the submission and sponsorship reserves do and why they are separate.
* [Gas reserves operations](/docs/operators/runbooks/gas-reserves-operations) for funding, thresholds, and troubleshooting steps.
* [Operator Wallets](/docs/operators/platform-setup/operator-wallets) for configured operator wallet gas balances across the deployment.
* [Account abstraction model](/docs/architecture/concepts/account-abstraction) for the smart-account execution route that uses this infrastructure.
* [Paymasters and gas sponsorship](/docs/architects/components/infrastructure/account-abstraction/paymasters-and-gas-sponsorship) for the conceptual model behind sponsored gas.