Contract safety measurements on Base, fetched live and rendered server-side. Each row names the endpoint it came from so you can check it yourself.
0xa4a92aa22cb174fbb48fd1a0d34f345217fc7b07 · view on Base explorer
| Check | Value | Source |
|---|---|---|
| honeypot.is | unreachable: HTTP 404 | api.honeypot.is/v2/IsHoneypot (chainID=8453) |
| Source code verified | yes | api.gopluslabs.io/api/v1/token_security/8453 |
| Mintable | no | api.gopluslabs.io/api/v1/token_security/8453 |
| Owner can take back ownership | no | api.gopluslabs.io/api/v1/token_security/8453 |
| Hidden owner | no | api.gopluslabs.io/api/v1/token_security/8453 |
| Transfers pausable | no | api.gopluslabs.io/api/v1/token_security/8453 |
| Blacklist function | no | api.gopluslabs.io/api/v1/token_security/8453 |
| Proxy contract | no | api.gopluslabs.io/api/v1/token_security/8453 |
| Creator holds | 0.00% | api.gopluslabs.io/api/v1/token_security/8453 |
| Owner address | 0x0000000000000000000000000000000000000000 | api.gopluslabs.io/api/v1/token_security/8453 |
| Share | Classification | Source |
|---|---|---|
| LP holder 69.87% | unknown holder | api.gopluslabs.io/api/v1/token_security/8453 · 0xb4b8fbf8bdd1872e065795ecdeebc49e6b9d5af6 |
| LP holder 30.13% | unknown holder | api.gopluslabs.io/api/v1/token_security/8453 · 0x1abee27c06b12965478380d62d97472908b400e2 |
"Unknown holder" means unknown, not unlocked. Our verified locker registry is deliberately empty: the first draft contained five locker addresses written from memory, and on-chain checks showed one was an empty wallet with no contract code and two could not be verified at all. A safety page that calls an empty wallet a locker is worse than one that admits the gap. The registry and its admission criteria.
This page states measurements, not a verdict. There is no score here on purpose: a number with its source beside it is something you can verify, and a score is something you have to trust. Checking many tokens at once? The same checks run as an API at Base Token Risk Scanner.