Contract and execution checks
Start with the exact Base contract address. Verify that the scanner is evaluating chain 8453 and not a same-name asset elsewhere.
Require explicit honeypot and mintability results. If a required security source is unavailable, treat that as no usable verdict rather than assuming the token passed.
Market and distribution checks
Review buy/sell taxes, exact matching Base liquidity, observed top-holder concentration, and observed LP-lock coverage. Each one answers a different question: exit cost, market depth, ownership concentration, and liquidity persistence.
Pay attention to null fields and source-status warnings. Data quality is part of the decision, not an implementation detail.
Decision discipline
BLOCK means stop under the configured Jepeta policy. WARN means review the flagged conditions. PASS means only that no configured WARN/BLOCK condition was observed in available evidence.
Run the scan close to execution, and use permanent evidence pages for traceability rather than as a substitute for a current scan.
Practical checklist
- Exact contract + Base 8453
- Honeypot
- Mintability
- Buy/sell tax
- Holder concentration
- Liquidity
- Observed LP lock
- Data quality/source status
- Fresh timestamp