On-chain Bitcoin addresses show up in a sanctions screen the moment they're generated; Lightning Network payments mostly never touch an address a screen can check at all.
On October 16, 2023, Bitcoin developer Antoine Riard disclosed a routing flaw serious enough to earn four CVE numbers at once: CVE-2023-40231 in LDK, -40232 in Eclair, -40233 in LND, -40234 in Core Lightning. Every major Lightning implementation needed a patch for the same underlying bug. If the engineers who built the protocol needed months to describe how one payment actually moves through it, a sanctions screen watching from outside has no real chance. That gap between Bitcoin's base chain and its Lightning Network is bigger than most people deciding where to accept a BTC payment realize. A block explorer like mempool.space or Blockstream.info will show you every input, output, and address tied to an on-chain Bitcoin transaction, back to the first confirmation it ever got. Screen the address with Plastron and that same address gets checked against the OFAC SDN list and the labeled threat corpus in one pass, instead of you reading the raw ledger yourself. Lightning gives you none of that. It wasn't built to.
What Changes When a Bitcoin Payment Moves Off-Chain Through Lightning?
A Lightning payment starts with an on-chain transaction and ends with one. In between, it does nothing a block explorer can see. Opening a channel means locking bitcoin into a 2-of-2 multisig output, and that output is as visible as any other UTXO, address, balance, all of it. Once the channel is open, payments move as signed balance updates the two sides hold privately. Nothing about an individual payment touches the Bitcoin blockchain again until someone closes the channel. A node can route a hundred payments through one channel in an afternoon, and the chain records exactly zero of them.
FinCEN's 2019 guidance on convertible virtual currencies says a business that accepts and transmits customer funds over Lightning is probably a money transmitter, the same test applied to a custodial exchange. The guidance names the business model. It doesn't hand that business a way to screen a single routed payment the way it would screen an on-chain deposit, because the payment was never built to be individually addressable in the first place. The rule applies. The tool to check it mostly doesn't exist.
Compliance teams that touch Lightning at all tend to work around the blind spot rather than through it. The common approach is to verify identity and screen a payment only at the two points where Lightning touches the outside world: when funds first enter a hosted wallet or exchange, and when they leave one. Everything the payment does while it's actually routing between those two points keeps happening off the record. That's a workable posture for a custodian. It's also an admission that Lightning itself can't be screened, only its edges can.
On-chain Bitcoin leaves a visible address at every step. Lightning only surfaces the channel's funding and closing transactions; everything routed in between stays off-chain.
On-Chain Bitcoin: 513 OFAC Hits and a Permanent Address Record
Bitcoin carries more direct OFAC SDN designations than any other chain in Plastron's corpus: 513 of the 780 OFAC SDN crypto addresses in Plastron's July 2026 baseline, out of more than 100,000 labeled addresses tracked altogether. Every one of those 513 is exactly that, an address, and every transaction it ever sends or receives sits on a ledger anyone can read for free.
Running a Bitcoin wallet check means matching the address against that sanctions list and against a wider threat corpus of scam, fraud, and hack-linked addresses, then pulling its live balance and activity straight from the chain. Plastron does this for Bitcoin the same way it does for Tron and Solana, a direct label and balance check, with no multi-hop graph behind it. There's no need for one. The address, and everything that ever touched it, is already sitting in public.
You don't need a warrant to read a Bitcoin address. You need a URL.
Bitcoin's base chain carries 513 directly screenable OFAC SDN addresses in Plastron's corpus. Lightning carries none, because a routed payment never resolves to a single address a designation could name.
Lightning Network: Fast, Private, and Built to Disappear
Lightning was built to solve a real problem. Bitcoin's base chain settles maybe seven transactions a second, and a $4 coffee payment shouldn't compete with a $4 million settlement for block space. Routing that coffee payment through a channel instead of the chain fixes the throughput problem, and it does it by onion-routing the payment so each hop only knows its immediate neighbors, never the sender or the final recipient. No single node, and no outside observer, sees the whole path.
For ordinary users that's a genuine feature. But it leaves almost nothing for a sanctions screen to check at the payment level. The channel-opening and channel-closing transactions are visible. The payments that move through that channel in between are not, and a liquidity rebalance between two routing nodes can look, from outside, like the kind of layering pattern that gets an on-chain wallet flagged, even when nothing about it is illicit. Rebalancing moves liquidity from one side of a channel to the other so it can keep routing in both directions, and it produces the same repeated, split-up transfer shape that trips a monitoring model built for a single wallet moving funds in and out. Nothing is being hidden on purpose. A system built to flag structuring can't always tell the difference. Good privacy design and screenable design are not the same thing. Lightning picked privacy.
Head-to-head
Line up the two on criteria that actually matter if you're deciding whether to accept a Bitcoin payment on-chain or over Lightning, and the gap holds across every row.
Criterion
On-chain Bitcoin
Lightning Network
OFAC sanctions check possible on the payment itself
Yes, direct address match
No, payments don't resolve to a checkable address
Direct OFAC SDN hits in Plastron's corpus
513
Not applicable, no address format to designate
Transaction history on a public explorer
Every input and output, indefinitely
Only channel-funding and channel-closing transactions
Governing US guidance
FinCEN 2019 CVC guidance
Same guidance, applied to the node operator, not the payment
Known protocol-level risk
None comparable at the payment layer
Replacement cycling (CVE-2023-40231 to -40234), disclosed Oct. 16, 2023
Plastron screening depth
Direct label and balance check, no multi-hop graph
Not covered, no Lightning invoice format to screen
A Clean Lightning Wallet Proves Nothing
A Lightning node with no sanctions hits hasn't passed a screen. It's mostly never been subject to one. The opening and closing transactions a channel does post on-chain are the only payment data a screen can reach, and those two data points describe a channel's entire lifetime, not any single payment inside it.
FATF's guidance for virtual-asset service providers flags exactly this gap, warning that structuring and layering typologies written for on-chain monitoring don't transfer cleanly to a network where the individual payment is invisible by construction. A node that routes a hundred payments a day and shows a clean channel balance at close could have handled one sanctioned counterparty, or none. From outside, the two look identical. A clean channel balance means nothing was visible, not that nothing happened.
Most regulated venues that advertise Lightning support don't actually expose raw peer-to-peer routing to a retail user. They run the node themselves, hold the channel, and screen the deposit as it lands on their side, then let Lightning handle only the plumbing underneath. The check still happens. It just happens at the wallet's boundary, before the funds ever touch a channel, not anywhere inside the network itself.
Verdict
Pick on-chain Bitcoin when you need to prove you checked who you're dealing with. The address is public, the OFAC list covers it, and a scan today works the same way it would have five years ago. Pick Lightning when the payment is small enough that the realistic laundering value rounds to zero, a few dollars for coffee or a tip isn't what Treasury built a sanctions program to catch, and waiting for an on-chain confirmation to screen it costs more than the risk you're managing. That's the one case where Lightning is clearly the right call: the screening overhead would exceed the actual exposure. For anything bigger than that, on-chain is the only one of the two you can actually check before you hit accept. If a counterparty insists on Lightning for a payment that actually matters, route it through a custodial wallet or exchange that screens deposits at the edge instead of accepting a raw peer-to-peer channel open. You lose a little of Lightning's privacy. You get back the one thing it can't give you: a record someone else can check.
Disclaimer: This article is for educational and informational purposes only and is not legal, financial, tax, or compliance advice. Crypto carries risk; you act on this information at your own risk. Always do your own research and consult a qualified professional before making decisions. Views are the author's own and do not constitute financial, legal, or investment advice.
About Plastron
Plastron is a free, non-custodial wallet screening tool. It checks Ethereum and six EVM chains for AML and KYT risk — sanctions exposure, mixer contact, and stolen-funds proximity — and returns a risk report in seconds. It reads public on-chain data only: it never takes custody of funds and never asks for private keys.