Insights on Crypto Payments, Infrastructure, and Operations

Address Blacklist

Pronunciation: AD-res BLAK-list

Also known as: Blocked Address List

Definition

Address Blacklist is a controlled list of blockchain addresses that a system is configured to reject, block, restrict, or escalate. It is used to prevent transactions involving destinations or sources that are prohibited, confirmed malicious, compromised, or unacceptable under policy. It differs from address screening, which evaluates current risk signals and context rather than relying only on a static list decision. In practice, a blacklist can stop payouts to known scam addresses, compromised wallets, sanctioned addresses, or addresses linked to prior incidents.

Overview

Address Blacklist is a controlled list of blockchain addresses that a system is configured to reject, block, restrict, or escalate. Its operational purpose is to prevent transactions involving destinations or sources that are prohibited, confirmed malicious, compromised, or unacceptable under policy. It should be considered alongside Address Screening. The relevant distinction is address screening, which evaluates current risk signals and context rather than relying only on a static list decision.

A typical workflow is as follows: An authorized process adds an address with its chain, reason, evidence, scope, effective date, owner, and review date. Transaction systems check exact chain-aware matches and apply the specified action.

Core controls include governed additions and removals, chain identification, reason codes, expiry or review dates, dual approval, source validation, change logs, and exception handling.

In payment and crypto operations, A blacklist can stop payouts to known scam addresses, compromised wallets, sanctioned addresses, or addresses linked to prior incidents. It should not treat similar-looking addresses as exact matches.

Evidence should include address, network, source, attribution confidence, reason, legal or policy basis, approvers, dates, affected transactions, exceptions, and removal rationale. Stale, overbroad, or incorrectly keyed entries can block legitimate users or fail to stop the intended destination.

It is used to prevent transactions involving destinations or sources that are prohibited, confirmed malicious, compromised, or unacceptable under policy.

A production treatment of Address Blacklist should test a controlled list of blockchain addresses that a system is configured to reject, block, restrict, or escalate within the relevant asset, decision, or service state. The Address Blacklist context record for block, restrict, and escalate should preserve source data, configuration or policy version, responsible actor, exception, and outcome. Review of Address Blacklist should determine whether safeguards addressing block, restrict, and escalate changed exposure in practice, not merely whether a document or setting existed.

Key Takeaway

An Address Blacklist needs exact chain-aware identifiers, documented reasons, controlled changes, review dates, and evidence for every restriction.

Sources

  1. Address Book and Crypto Withdrawal Address Whitelisting — Coinbase (2026-08-03)
  2. Sanctions List Service — U.S. Treasury OFAC (2026-08-03)
  3. Guidance for a Risk-Based Approach to Virtual Assets and VASPs — FATF (2026-08-03)