Contract safety measurements on Ethereum, fetched live and rendered server-side. Each row names the endpoint it came from so you can check it yourself.
0x678658399199a736b1b74ce7aa799247a9391f9a · view on Ethereum explorer
| Check | Value | Source |
|---|---|---|
| honeypot.is | unreachable: HTTP 404 | api.honeypot.is/v2/IsHoneypot (chainID=1) |
| Source code verified | yes | api.gopluslabs.io/api/v1/token_security/1 |
| Mintable | no | api.gopluslabs.io/api/v1/token_security/1 |
| Owner can take back ownership | no | api.gopluslabs.io/api/v1/token_security/1 |
| Hidden owner | no | api.gopluslabs.io/api/v1/token_security/1 |
| Transfers pausable | no | api.gopluslabs.io/api/v1/token_security/1 |
| Blacklist function | no | api.gopluslabs.io/api/v1/token_security/1 |
| Proxy contract | no | api.gopluslabs.io/api/v1/token_security/1 |
| Creator holds | 0.00% | api.gopluslabs.io/api/v1/token_security/1 |
| Owner address | 0x0000000000000000000000000000000000000000 | api.gopluslabs.io/api/v1/token_security/1 |
| Share | Classification | Source |
|---|---|---|
| LP holder 97.36% | unknown holder | api.gopluslabs.io/api/v1/token_security/1 · 0xeea6c6ca4ede9d677f8d42837a386ec84ca88f1b |
| LP holder 2.64% | unknown holder | api.gopluslabs.io/api/v1/token_security/1 · 0x7a2069ae091a83e6d85306813c7b8325e4ce5ba7 |
"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.