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.
0x3221baeb0c2745e39a1dba73cd413361b7f5fe13 · view on Base explorer
| Check | Value | Source |
|---|---|---|
| Honeypot simulation ran | yes | api.honeypot.is/v2/IsHoneypot (chainID=8453) |
| Flagged as honeypot | no | api.honeypot.is/v2/IsHoneypot (chainID=8453) |
| Buy tax | 0% | api.honeypot.is/v2/IsHoneypot (chainID=8453) |
| Sell tax | 0% | api.honeypot.is/v2/IsHoneypot (chainID=8453) |
| Transfer tax | 0% | api.honeypot.is/v2/IsHoneypot (chainID=8453) |
| Holders | 49 | 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 89.79% | unknown holder | api.gopluslabs.io/api/v1/token_security/8453 · 0x231278edd38b00b07fbd52120cef685b9baebcc1 |
| LP holder 4.29% | unknown holder | api.gopluslabs.io/api/v1/token_security/8453 · 0x8e4c015fb1558e5f5e86d3d91836b2a8cb967bb2 |
| LP holder 3.60% | unknown holder | api.gopluslabs.io/api/v1/token_security/8453 · 0xdb03585d268368a99b8704c55187d00693a9127e |
| LP holder 2.32% | unknown holder | api.gopluslabs.io/api/v1/token_security/8453 · 0x5f2f3a193592d20a4b0a24a7254c6b5d30d98841 |
"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.