jepeta.
evidence

How should I use a permanent Base token risk evidence page?

Use a permanent evidence page as a timestamped record of what Jepeta publicly observed for an exact Base token at a specific time. It is designed for verification, citations, comparisons, and audit trails. For a current trade, use the page's fresh-scan link because token and market conditions can change.

Concept illustration of a lens inspecting transparent evidence layers and an obscured boundary.
Jepeta · Original AI concept illustration; not a product photo or evidence

Key takeaways

  • Use canonical URL for citations
  • Check lastCheckedAt
  • Use JSON for software
Dated observations · Base

Radar evidence

These reviewed observations are examples tied to their original measurement times. They describe screening outputs, not a current token assessment.

The canonical screening output changed. This describes Jepeta policy output, not proof of fraud or a safety guarantee.

Source scope: First-party engine output; two timestamps are not two independent providers.

Open Radar

What the permanent page contains

Each eligible page exposes the exact contract, Base chain ID, PASS/WARN/BLOCK decision, score and level, explicit honeypot and mintability signals, taxes when available, exact matching liquidity, observed concentration, observed LP-lock coverage, warnings, source status, methodology, and timestamps.

The same snapshot is available as HTML for users and search engines and as JSON for software. Both use one canonical URL family under /risk/base/0xTOKEN/.

Why not every scan becomes a page

Jepeta only promotes tokens that already passed its public publication gate, have HIGH or MEDIUM public data quality, explicit required security booleans, and at least two non-null public evidence dimensions.

This gate avoids turning ordinary scans or incomplete data into a mass of thin, indexable pages.

Historical snapshot versus current report

Permanent pages preserve the public snapshot selected for publication. The free full report can provide additional available evidence for an exact token, but neither surface guarantees that an upstream provider supplied every field.

Keep the two purposes separate: a citation identifies a recorded observation, while a new report asks what the service can observe now. A free report does not make an old snapshot current.

Make a citation reproducible

A useful citation records the canonical snapshot URL, exact contract, chain, observation time and the field being discussed. If a later scan differs, cite it as a separate observation. Do not overwrite the earlier value or describe the page-build time as a new provider check. Before comparing two records, check whether their methodology and evidence scope are comparable; a changed output can reflect a changed method rather than a changed token.

AI-assisted review of linked documentation; no independent product benchmark. Screening observations and policy labels do not guarantee token safety.

Practical checklist

  • Use canonical URL for citations
  • Check lastCheckedAt
  • Use JSON for software
  • Run fresh scan for current decisions
  • Distinguish the snapshot from a current free report

Limitations

This is educational risk-screening content, not investment advice. Token and market conditions can change after any snapshot. A PASS result or negative honeypot signal is not a safety guarantee.

Public evidence snapshot example

0x4f81f6ae802dec6c8e1846ad853019a5458186d1

DecisionWARN
Risk score65/100
HoneypotNo
MintableNo
Liquidity$0.04
CheckedOct 16, 2026

Timestamped public evidence only. Run a fresh scan for current execution.

Field-specific interpretation: Observed Oct 16, 2026. This is a historical public snapshot; always request a fresh exact-contract scan for a current decision.

Open evidence

Sources & methodology

Sources reviewed Nov 4, 2026.

Continue reading

Browse all articles