Contract source code is not verified
- What it means
- The source code behind the deployed contract has not been published.
- Why a contract might have it
- Sometimes nothing more than an unfinished housekeeping step.
- When it matters
- It means nobody outside the team has read what the contract does. Not a finding on its own — an absence of one, which is different.
52 of the 6,030 contracts we have read carry this — about 0.9% of the catalogue. Worth knowing about, and common enough that it is not on its own a reason to conclude anything.
Tokens whose contract permits this
Most recently checked first. 25 further contracts carry it and are not listed: they belong to assets with an established market position, where these heuristics are unreliable enough that naming them would be wrong.
- ethereum
- ethereum
- ethereum
- ethereum
- Nest Apollo ACRDX VaultNACRDXethereum
- ethereum
- ethereum
- ethereum
- ethereum
- Aquabank bCircleBUSDCavalanche
- ethereum
- ethereum
- ethereum
- Aquabank bTetherBUSDTavalanche
- ethereum
- ethereum
- ethereum
- ethereum
- Molecules of Korolchuk IP-NFTVITA-FASTethereum
- arbitrum-one
- ethereum
- ethereum
- ethereum
- ethereum
- Tradable LatAm Residential SSTLPC0000089zksync
- ethereum
- Tradable Singapore Fintech SSLPC0000023zksync
Being listed here means the contract permits something, not that the project has done it or intends to. Contract data from GoPlus Security; each token's own page carries the full report and the date it was read.