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.
0xaa8319bff7898f24780b6f80839b1ea13f02a4b8 · 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 | yes | api.gopluslabs.io/api/v1/token_security/8453 |
| Owner can take back ownership | unknown | api.gopluslabs.io/api/v1/token_security/8453 |
| Hidden owner | unknown | api.gopluslabs.io/api/v1/token_security/8453 |
| Transfers pausable | unknown | api.gopluslabs.io/api/v1/token_security/8453 |
| Blacklist function | unknown | api.gopluslabs.io/api/v1/token_security/8453 |
| Proxy contract | yes | api.gopluslabs.io/api/v1/token_security/8453 |
| Creator holds | 0.00% | api.gopluslabs.io/api/v1/token_security/8453 |
| Share | Classification | Source |
|---|---|---|
| LP holder 100.00% | unknown holder | api.gopluslabs.io/api/v1/token_security/8453 · 0x27869cfa0dd5dae258aeb14e26c1e1df23b9cccb |
| LP holder 0.00% | unknown holder | api.gopluslabs.io/api/v1/token_security/8453 · 0xc2f71f4865cbfde605d5a99ca287b1d74e2f58ea |
"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.