# Your account wallet

Source: https://docs.settlemint.com/docs/operators/user-management/account-wallet
Read the Wallet card on your DALP account page. Understand the wallet address that holds your assets, the on-chain status badge, and the managed signing key behind the Show control.



The Wallet card on your account page shows the addresses that act for you on-chain. It leads with the address that holds your assets, keeps the technical signing address tucked behind a control, and, on administrator views, tells you whether the wallet is live on-chain.

Open it from **Account** > **Profile**. The same card appears to administrators on a participant's detail page.

## The wallet address that holds your assets [#the-wallet-address-that-holds-your-assets]

The address shown first, under the **Wallet** heading, is your smart wallet. This is the account that holds balances and executes your transactions. When you mint, transfer, or service an asset, this is the address the action runs from and the address compliance checks evaluate. It is the address to share when someone needs to send you an asset.

The card shows the raw address rather than your display name, so you can copy and verify the exact value.

## The status badge [#the-status-badge]

On administrator views of a participant, the card can show a status badge beneath the wallet address:

| Badge                          | Meaning                                                                                                                   |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------- |
| Active on-chain                | The smart wallet is deployed on-chain and ready to execute transactions.                                                  |
| Activates on first transaction | The smart wallet address is assigned and reserved, and it deploys automatically the first time it executes a transaction. |

A pending wallet is not an error. The address is already yours; deployment happens on first use, so you can receive and prepare work before the wallet executes anything.

Your own profile page omits this badge. It reports the address that is yours without asserting a deploy state that a self-view cannot always confirm.

## The signing key behind the Show control [#the-signing-key-behind-the-show-control]

Below the wallet address, a collapsed **Signing key** row sits behind a **Show** control. Selecting it reveals a second address with the note that it is the key that authorizes the wallet's transactions and is managed for you. Selecting **Hide** collapses it again.

The signing key is intentionally tucked away. It is the key that signs on behalf of your smart wallet, and DALP manages it for you. You do not need it for routine work: balances, transfers, and compliance all attach to the wallet address above, not to this key. The disclosure exists so the address is available when you want to verify it, without putting account-abstraction detail in front of every routine action.

The wallet and its signing key resolve to a single identity before any compliance check or registry operation runs, so an action lands in the audit trail attributed to you regardless of which address signed it.

## When the card shows a single address [#when-the-card-shows-a-single-address]

The card collapses to a single address under **Wallet**, with no separate signing-key disclosure, in two situations:

* **Account abstraction is disabled.** There is one address acting for you, and the card presents it plainly.
* **Your wallet address and signing key are the same address.** A separate disclosure would only repeat the same value, so the card omits it.

A pending smart wallet does not collapse to a single address. Even when the wallet is assigned but not yet deployed on-chain, it still has its own wallet address, separate from the managed signing key. The card keeps the full layout: the wallet address, the **Activates on first transaction** badge on administrator views, and the collapsed **Signing key** row.

## Related guides [#related-guides]

* [Account security](/docs/operators/user-management/account-security)
* [Account abstraction security](/docs/compliance-security/security/account-abstraction-security)
* [Why account abstraction](/docs/architecture/concepts/account-abstraction)