What to verify before acting
Start with the exact contract address on Base chain 8453. Names and tickers are not unique, so checking the wrong contract can produce a technically correct answer for the wrong asset.
Treat the result as a screening snapshot. Contract controls and market conditions can change, and a token that passes one check can still fail a different due-diligence question.
How Jepeta answers the question
Jepeta requires explicit honeypot and mintability evidence from GoPlus for a successful public verdict. It also records buy and sell taxes when available, observed top-10 holder concentration, observed LP-lock coverage, exact matching Base liquidity from DEX Screener, source status, and data quality.
BLOCK means a configured hard blocker was observed. WARN means at least one material risk or evidence-quality condition needs review. PASS only means no configured WARN/BLOCK condition was observed in the available evidence at that time.
Use evidence, not a label
Read the normalized evidence fields behind the decision. If liquidity is missing, concentration is high, mintability is enabled, or upstream data is degraded, those facts matter more than a single score.
For a current decision, run a fresh scan. Permanent evidence pages are historical, timestamped snapshots for tokens that already passed Jepeta's publication gate; they are useful for verification and citation, not as an eternal verdict.
Turn the safety question into an evidence question
A hypothetical screening result with a missing optional liquidity observation does not answer whether your intended order can exit at an acceptable price. State what the screening established and what remains unknown, then obtain separate route and execution evidence if needed. If required evidence is missing, first recognize NO_VERDICT rather than treating the situation as a weaker PASS. This distinction avoids making a stronger conclusion than the available record supports.
AI-assisted review of linked documentation; no independent product benchmark. Screening observations and policy labels do not guarantee token safety.
Practical checklist
- Confirm the exact Base contract
- Check honeypot and mintability
- Review taxes and liquidity
- Review holder concentration and LP-lock observations
- Read data-quality and source-status fields
- Use a fresh scan before execution
Limitations
Sources & methodology
Sources reviewed Nov 4, 2026.


