Machine-readable at /lockers.json. Free, no key, copy it.
| Label | Address | Why it counts as burned |
|---|---|---|
| Null address | 0x0000000000000000000000000000000000000000 | No private key can exist for it. Tokens sent here are unrecoverable by anyone, including the deployer. The strongest form of "burned". |
| Dead address (0x…dEaD) | 0x000000000000000000000000000000000000dead | A convention rather than a protocol feature, but no known private key exists for it, so it behaves as a burn in practice. |
The locker registry is empty, and that is a deliberate choice rather than an oversight.
Every guide on checking liquidity says "see whether the LP sits in a known locker" and then never lists the addresses, so a complete registry is the genuinely missing public good here. The first draft of this file had five, written from recall. Checked on chain before publishing: one — labelled a Team Finance locker — returned no contract code at all, an empty externally-owned account. Two others could not be verified. Three of five were wrong or unprovable.
A safety page that tells someone their liquidity is locked in an empty wallet is worse than no page. So nothing goes in without meeting all four criteria: bytecode present on that chain, the operator's own documentation naming that exact address, recorded lowercase and never retyped from a screenshot, and a date when both were last confirmed together. "It is a contract" proves it is not an empty wallet and proves nothing about whose contract it is — that criterion is what blocked every candidate.
Entries appear here as they clear that bar. Until then this answers unknown, which is true.