Address block-list
Configure the DALP address block-list module so an asset rejects specific wallet addresses regardless of registered identity status.
The address block-list compliance module rejects regulated operations when any involved wallet address is on the asset's block-list. Use the address block-list for wallet-level sanctions enforcement where the block must apply even to wallets without a registered identity, or to specific wallets owned by an otherwise-allowed identity.
The address block-list differs from the identity block-list: identity blocks operate on OnchainID and cover every wallet under that identity, while address blocks operate on raw EVM addresses.
For the architecture reference, see Address block-list.
Prerequisites
- The asset already exists (configure during creation) or you have the Asset administrator role on the deployed asset.
- The wallet addresses to block are known and validated as valid EVM addresses.
- Operating-team approval to block the addresses, with documented justification.
Configure during asset creation
In the Asset Designer compliance step, pick the address block-list module. Add the wallet addresses to block. Most assets start with an empty list; entries land later as compliance events occur.
Configure on an existing asset
From the asset detail workspace, open the compliance tab and add or remove address entries on the block-list. The platform queues an on-chain transaction per change.
Operating considerations
- The address block-list operates on raw addresses. A blocked wallet that belongs to an otherwise-allowed OnchainID still cannot transact under this asset; the holder must use a different wallet under the same OnchainID if they need to continue.
- The block-list does not move existing balances out of a blocked wallet. Coordinate forced transfer or escheatment through the operating runbook when the block must take effect on existing balances.
- The address block-list applies to the asset only. Adding an address to one asset's list has no effect on other assets.
What stays external
Sanctions screening, address-attribution evidence, regulatory disclosures, and the periodic review of the block-list stay with your compliance team.
Troubleshooting
| What you see | What to check |
|---|---|
| Transfer still passes for a blocked address | Confirm the on-chain transaction that added the entry has confirmed. The list edit is asynchronous. |
| Need to block every wallet under an identity | Use the identity block-list instead; identity-level blocks cover all wallets under that OnchainID. |
| Need to unblock without losing audit evidence | Remove the entry; the compliance event remains in the audit trail. Document the reversal in your compliance log. |
Read next
- Compliance overview
- Identity block-list for identity-level blocking.
- Address block-list architecture