Overview#
The Address Whitelist centrally manages addresses your Team has verified, and controls how they can be used through groups, tags, and transfer restrictions.A whitelist accumulates address identity information — who an address belongs to and what business it serves. The outcome is owned by the Policy Engine: a whitelist can serve as a destination condition in a policy, for example requiring approval for transfers to addresses outside it. Separately, whitelists work with transfer restrictions to constrain which destination addresses can be selected at all.Adding an address to the whitelist is not a guarantee by DeepSafe that the address is genuine or safe. Verify the address, its network, and its owner through an independent, trusted channel before submitting.This page uses the app as its example. Fields and approval rules are the same in the Web Console, reached from Address Whitelist in the left navigation.Before you begin#
You have joined the intended Team and switched to it;
You hold the permissions to view, add, edit, delete, or approve whitelist entries;
If you need to change transfer restrictions, you hold the corresponding view and toggle permissions;
You have verified the address, its network, and its owner through a trusted channel.
Opening the whitelist#
In the app, tap Workbench in the bottom navigation, then Address Whitelist.The list shows each entry's name, network type, address, status, group, and tags. Transfer restrictions are reachable from the top of the screen, and new entries are created from the top right.Searching and filtering#
Search — enter a whitelist name or address at the top of the list and matching results appear as you type.Filter — tap the filter button to the right of the search box to combine the following conditions.| Condition | Options |
|---|
| Network type | EVM, Bitcoin, Bitcoin Testnet3, Tron, Solana |
| Status | Active, Pending approval |
| Group | Customer, Internal Wallet, Supplier |
| Tags | Tags defined by your Team |
Tap Confirm to apply, or Reset to clear. The groups and tags actually available depend on your Team's current configuration.Creating an entry#
Tap the add button at the top right of the list, complete the following, and submit for approval.| Field | Required | Notes |
|---|
| Name | Yes | Up to 30 characters. Use a recognizable business name rather than only a platform name |
| Network type | Yes | Select the network the address actually belongs to. Choosing EVM covers the mainnets and testnets of all EVM-compatible chains |
| Address | Yes | Enter manually or scan a QR code |
| Group | No | Classify by business counterparty — Customer, Internal Wallet, or Supplier |
| Tags | No | Up to 3. Choose from existing tags or create new ones |
| Note | No | Up to 100 characters. Describe what the address is for, who owns it, and how it was verified |
Check the network type and the full address again before submitting. Once submitted, the entry shows as Pending approval — add. After approval it becomes Active, and only then is it formally part of the whitelist.The system validates that the address format matches the selected network type, and prevents adding an address that already exists.Example#
| Field | Example | Guidance |
|---|
| Name | Exchange deposit account | Use a name your Team recognizes at a glance |
| Network type | EVM | Must match the address's actual network |
| Address | 0x28C6…1d60 | Verify the full address before submitting, not just the first and last characters |
| Group | Customer | Used by policy references and list filtering |
| Tags | High-frequency | Adds business context, up to 3 |
| Note | Deposits and liquidity movements | Describes the purpose and scenario |
Groups do more than classify. A policy's destination condition can reference a whitelist group, and addresses added to that group afterward are covered by the policy automatically. Planning your groups well substantially reduces policy maintenance.Viewing details#
Tap an Active entry to open its details, which contain three parts.Basic information — name, network type, address, status, group, tags, note, creation time, update time, and source. Source indicates whether the entry was created in the app or the Web Console.Transactions — sends and receives involving this address.Change history — approved creations and edits, with the before-and-after difference for each field.Entries with the status Pending approval — add are not yet active and cannot be opened.Editing an entry#
Swipe left on an entry in the list and tap edit. You can change the name, group, tags, and note. Submit for approval and confirm in the dialog.The entry then shows as Pending approval — edit. After approval the new content takes effect; if the request is rejected, the original content is retained.Network type and address cannot be changed after creation. Together they identify the on-chain destination, and locking them prevents an address being reused across networks by mistake. If either is wrong, delete the entry and create a new one.Entries that are pending approval cannot be edited again.Deleting an entry#
Swipe left on an entry in the list, tap delete, read the notice, and submit for approval.The entry then shows as Pending approval — delete. Once approved, the address is removed from the whitelist and removed at the same time from the whitelist scope referenced by transfer policies. If the request is rejected, the address remains.Before deleting, confirm no transaction in progress or about to be submitted depends on that address. Deleting a whitelist entry does not delete the address's existing transaction history.Approving whitelist changes#
Adding, editing, and deleting whitelist entries all require approval under your Team's Decision Mode.In the app, tap Approvals in the bottom navigation, open Pending, select Other approvals, and open the request.What to check depends on the request type:Add — verify the name, network type, full address, group, tags, and note.Edit — focus on the difference between the previous and new values.Delete — consider the effect on transfers and transfer policies.Approve or reject once you have verified the details.Submitters can track progress under Approvals > Submitted by me. An add request that is still pending can also be cancelled by swiping left on the entry in the list; the entry then never enters the whitelist.Transfer restrictions#
Transfer restrictions come in two forms — Manual Transfer Restriction and API Transfer Restriction — set independently of each other.Manual Transfer Restriction, when enabled, means transfers created manually in the app or Web Console can only use whitelist addresses that are Active and match the network.API Transfer Restriction, when enabled, means transfers initiated through the API can only go to whitelist addresses that are Active and match the network.Enabling and disabling are not symmetrical#
Enabling — switch the toggle on in the transfer restrictions screen and confirm. It takes effect immediately.Disabling — switch the toggle off and submit for approval; the screen then shows Pending approval — disable. The existing restriction remains in force until approval completes, after which transfers to non-whitelist addresses of that type become possible.This design lets you tighten controls at any time, while relaxing them requires the Team's agreement. While one restriction is pending approval, that toggle cannot be changed again.Using whitelist addresses in transfers#
With the Manual Transfer Restriction enabled, selecting a destination address while creating a transfer opens the whitelist address list. You can search by name, address, group, or tag, select an address that is Active and matches the network of the current transfer, then return and verify the address, network, and amount before submitting.Entries showing Pending approval — add, edit, or delete should not be relied on as valid destination addresses.If a destination address is deleted, its group changes, or the transfer restriction changes after a transaction is submitted, the approval detail flags the difference between the current state and the state at submission. Approvers should re-verify before deciding whether to proceed.Status reference#
| Status | Meaning | Already in effect as requested |
|---|
| Active | The address has been approved and is in the whitelist | Yes |
| Pending approval — add | A new address is awaiting approval | No |
| Pending approval — edit | An edit is awaiting approval | No; applies once approved |
| Pending approval — delete | A deletion is awaiting approval | No; removed once approved |
| Pending approval — disable | A request to disable a transfer restriction is awaiting approval | No; the restriction stays on until approved |
Things to note#
Always verify the full address through an independent, trusted channel; never rely on the first and last characters alone;
Network type and address must match. Addresses for the same asset on different networks are not interchangeable;
A whitelist means only that your Team permits the address; it does not mean the address is free of fraud, sanctions, or other on-chain risk;
Groups are referenced by transfer policies. Confirm the effect on existing policies before changing a group or deleting an address;
Because the Policy Engine denies by default, narrowing whitelist coverage can block transactions that were previously released;
Only entries with the status Active are a reliable basis for use;
The Manual and API Transfer Restrictions are independent — check both;
Before enabling a transfer restriction, confirm that every destination address your routine business uses is already in the whitelist and approved.
Modified at 2026-08-26 02:51:05
