{
  "object": "jepeta_content_article",
  "schemaVersion": "1.0.0",
  "id": "article.base-risk-alerts-pool-comparability-2026",
  "contentType": "original_research",
  "title": "Five of 13 Base Token Risk Alerts Compared Different Liquidity Pools",
  "slug": "base-risk-alerts-pool-comparability-2026",
  "category": "research",
  "intent": "Investigate whether token risk-score changes measure the same DEX pool, using a reproducible audit of Jepeta's own published Base Intelligence records.",
  "directAnswer": "A review of 13 Jepeta Base risk-score events published on October 7–8, 2026 found that five before/after comparisons changed the selected liquidity pool (38.5% of the event cohort). The observation describes stored first-party metadata, not independent market behavior. A score movement across different pools must not be presented as a like-for-like liquidity change.",
  "sections": [
    {
      "heading": "The finding: five comparisons changed the selected pool",
      "paragraphs": [
        "In a read-only review of Jepeta's 13 published Base token risk-score events dated October 7–8, 2026, **5 events used a different selected DEX pool before and after the score change**. The other 8 retained the same selected pool. That is 38.5% of this publication cohort—not 38.5% of Base tokens, trades, alerts elsewhere, or incidents.",
        "Pool identity matters because a comparison between two different markets is not a measurement of how liquidity changed *inside one market*. A score can move when the scoring system selects a different pool. The stored score is a valid historical output of the stated policy, but it cannot by itself explain a token's actual market behavior. This audit has not independently reconstructed the historical third-party API responses."
      ]
    },
    {
      "heading": "The five affected records",
      "paragraphs": [
        "| Published event | Stored score before → after | Selected pool identity |\n| --- | ---: | --- |\n| [KRAV](https://jepeta.dev/intelligence/2026-10-07-be3111856e-risk-score-fa7332ed74fc/) | 65 → 30 | Changed |\n| [ZED — first alert](https://jepeta.dev/intelligence/2026-10-08-a7921e4c3d-risk-score-7ca74964dd36/) | 70 → 80 | Changed |\n| [flETH](https://jepeta.dev/intelligence/2026-10-08-000000000d-risk-score-61faa3a8b6d6/) | 45 → 55 | Changed |\n| [ZED — later alert](https://jepeta.dev/intelligence/2026-10-08-a7921e4c3d-risk-score-2ddfeb9d78b5/) | 80 → 70 | Changed |\n| [YUNAI](https://jepeta.dev/intelligence/2026-10-08-ea2e0887dc-risk-score-a8825d5fb9f6/) | 65 → 40 | Changed |\n\nThe two ZED entries are separate published events for the same token, not two distinct tokens. The cohort denominator is **events**, and includes repeated observations of tokens. This is not a claim that any of these tokens are unsafe."
      ]
    },
    {
      "heading": "Why a token can have more than one pool",
      "paragraphs": [
        "[DEX Screener's API reference](https://docs.dexscreener.com/api/reference) exposes both pair-address lookups and a token-pairs endpoint, because a token may trade across multiple liquidity pools. [CoinGecko's onchain documentation](https://docs.coingecko.com/reference/top-pools-contract-address) likewise retrieves and ranks multiple pools for a token. These official API contracts support the basic distinction between a token and the specific market selected to describe it.",
        "Consider a reader seeing an apparent improvement in a risk score while the selected market changes. Without a stable pair identifier, a statement such as 'the original pool recovered' would exceed the evidence. The responsible next step is to compare the exact chain, token contract, DEX pool address, observation time and source coverage, then examine whether the scoring policy itself changed."
      ]
    },
    {
      "heading": "What did pass the narrower reviewed-feed test?",
      "paragraphs": [
        "Two other October 7 cases—[SM](https://jepeta.dev/intelligence/2026-10-07-4f81f6ae80-risk-score-c3434b27af96/) and [TKN247](https://jepeta.dev/intelligence/2026-10-07-474c853a5c-risk-score-765ac21c5744/)—kept the same selected pool in their stored before/after records and passed a separately documented **AI-assisted retrospective editorial review** for Jepeta's narrowly defined first-party observations. That approval covers what Jepeta's system recorded; it is not independent verification of raw historical provider measurements or a judgment about either token.",
        "The distinction is operationally important: a working news feed should not treat an automated signal, a reviewed internal calculation and independent market corroboration as equivalent. Jepeta's external publisher feed only includes its specifically reviewed records, and still requires third-party editors to decide whether any are newsworthy."
      ]
    },
    {
      "heading": "Reproduction: a small, bounded cohort",
      "paragraphs": [
        "**Population:** every row with a non-null publication timestamp in Jepeta's `jepeta.live_intelligence_events` table at the audit time. **Count:** 13 published events; unpublished or withdrawn events were excluded. **Calculation:** compare the two exact stored fields `payload.context.previous_pool` and `payload.context.pool` per event. Five differ and eight match. The numerator is divided by thirteen and rounded to one decimal place. Scores are read from the original event payload, never recomputed under a new version.",
        "Jepeta retained the per-event identifiers and selected-pool fields for this audit. The [public Intelligence catalog](https://jepeta.dev/intelligence/) exposes the corresponding dated reports, and the [methodology](https://jepeta.dev/methodology.html) describes the limitations of a screening result. Historical raw third-party provider bodies were not independently reproduced, so the audit proves an internal metadata classification, not that the underlying external markets changed in a particular way."
      ]
    },
    {
      "heading": "What analysts and readers can do with this",
      "paragraphs": [
        "Before citing a token risk-score movement, ask five questions: Was the token contract identical? Did the selected DEX pool stay the same? Were the observation timestamps and methodology versions comparable? Which provider fields were missing or uncertain? Did an independent reviewer check the inference being made, rather than only the arithmetic? If any answer is unknown, describe the output as a dated screening observation and preserve the uncertainty.",
        "**Bottom line:** this small first-party audit identifies a specific failure mode for interpreting automated risk headlines. It does not establish error rates for other projects, estimate market-wide prevalence or recommend trading any named token. The useful lesson is to keep market identity attached to every before/after claim. Jepeta's screening products and commercial relationships did not determine this classification."
      ]
    }
  ],
  "sources": [
    {
      "id": "jepeta_events",
      "label": "Jepeta published Live Intelligence event catalog — Oct 7–8, 2026",
      "url": "https://jepeta.dev/intelligence/",
      "sourceType": "primary",
      "publishedAt": null,
      "verifiedAt": "2026-10-09T20:19:14.667Z"
    },
    {
      "id": "jepeta_method",
      "label": "Jepeta risk-screening methodology and evidence limitations",
      "url": "https://jepeta.dev/methodology.html",
      "sourceType": "primary",
      "publishedAt": null,
      "verifiedAt": "2026-10-09T20:19:14.667Z"
    },
    {
      "id": "dexdocs",
      "label": "DEX Screener official API reference — pairs and token-pairs endpoints",
      "url": "https://docs.dexscreener.com/api/reference",
      "sourceType": "primary",
      "publishedAt": null,
      "verifiedAt": "2026-10-09T20:19:14.667Z"
    },
    {
      "id": "geckodocs",
      "label": "CoinGecko official onchain API — top pools by token address",
      "url": "https://docs.coingecko.com/reference/top-pools-contract-address",
      "sourceType": "primary",
      "publishedAt": null,
      "verifiedAt": "2026-10-09T20:19:14.667Z"
    },
    {
      "id": "publisher",
      "label": "Jepeta editorially reviewed publisher feed and publication decisions",
      "url": "https://jepeta.dev/publisher/source.json",
      "sourceType": "jepeta",
      "publishedAt": null,
      "verifiedAt": "2026-10-09T20:19:14.667Z"
    }
  ],
  "sourceDates": [
    {
      "sourceId": "jepeta_events",
      "publishedAt": null,
      "verifiedAt": "2026-10-09T20:19:14.667Z"
    },
    {
      "sourceId": "jepeta_method",
      "publishedAt": null,
      "verifiedAt": "2026-10-09T20:19:14.667Z"
    },
    {
      "sourceId": "dexdocs",
      "publishedAt": null,
      "verifiedAt": "2026-10-09T20:19:14.667Z"
    },
    {
      "sourceId": "geckodocs",
      "publishedAt": null,
      "verifiedAt": "2026-10-09T20:19:14.667Z"
    },
    {
      "sourceId": "publisher",
      "publishedAt": null,
      "verifiedAt": "2026-10-09T20:19:14.667Z"
    }
  ],
  "originalEvidence": [
    {
      "type": "jepeta_data",
      "description": "Read-only cohort extraction of 13 published first-party Base Intelligence payloads, retaining exact before/after selected pool identifiers, score outputs and 13 canonical event URLs.",
      "url": "https://jepeta.dev/intelligence/",
      "observedAt": "2026-10-09T20:19:14.667Z"
    },
    {
      "type": "calculation",
      "description": "Recomputed event-level pool identity comparison: 5 changed, 8 unchanged out of 13 published events; 5/13 rounds to 38.5%. Two ZED event rows are counted separately.",
      "url": "https://jepeta.dev/intelligence/",
      "observedAt": "2026-10-09T20:19:14.667Z"
    }
  ],
  "datePublished": "2026-10-09T20:19:14.667Z",
  "dateModified": "2026-10-09T20:19:14.667Z",
  "reviewedAt": "2026-10-09T20:19:14.667Z",
  "affiliate": {
    "enabled": false,
    "partnerId": null,
    "linkId": null,
    "disclosureRequired": false,
    "rel": null
  },
  "disclosure": "This analysis is based on Jepeta's own published data, prepared with AI-assisted editorial methods. No commercial relationship affects the findings, and no third-party historical raw provider response was independently reconstructed.",
  "internalLinks": [
    "/news/",
    "/intelligence/",
    "/research/",
    "/methodology.html",
    "/articles/token-risk-evidence-limits/",
    "/#scanner"
  ],
  "telegramCohort": {
    "surface": "article",
    "cohortId": "article"
  },
  "format": "markdown",
  "seoTitle": "Base Token Risk Alerts: 5 of 13 Changed the Liquidity Pool",
  "metaDescription": "Jepeta reviewed 13 published Base token risk alerts and found 5 before/after comparisons used different DEX pools. See the records, method and limits.",
  "quality": {
    "decision": "publish",
    "citabilityScore": 100,
    "reviewedAt": "2026-10-09T20:19:14.667Z",
    "policyVersion": "1.0.0"
  },
  "canonicalUrl": "https://jepeta.dev/articles/base-risk-alerts-pool-comparability-2026/",
  "jsonUrl": "https://jepeta.dev/articles/base-risk-alerts-pool-comparability-2026/index.json"
}