What a honeypot check tells you
A honeypot detector tries to identify whether buying is possible while selling is blocked or materially impaired. Honeypot.is documents an IsHoneypot endpoint with simulation results and buy/sell tax fields.
That answers a narrow but critical execution question. It does not by itself prove that contract permissions, liquidity depth, ownership concentration, or later contract changes are acceptable.
How Jepeta handles unknowns
Jepeta uses GoPlus as the required security source for its strict public honeypot signal. If the required honeypot value is unknown, Jepeta does not silently convert it to false; the public scan fails closed instead of manufacturing reassurance.
A successful Jepeta preview therefore exposes is_honeypot as an explicit boolean alongside is_mintable, tax fields, market context, data quality, and source status.
What to do after the honeypot result
If the result is positive, stop. If it is negative, continue with mintability, taxes, holder concentration, liquidity, and source quality. A negative honeypot result is one passed check, not a safety certificate.
For permanent verification, use a Jepeta evidence page only when one exists for that exact token. Evidence pages are timestamped and disclose their last-checked time.
Practical checklist
- Use the exact Base contract
- Require an explicit honeypot result
- Do not treat unknown as false
- Continue with permission and market checks
- Re-scan close to execution