> ## Documentation Index
> Fetch the complete documentation index at: https://docs.viperx.site/llms.txt
> Use this file to discover all available pages before exploring further.

# How ViperX Independently Verifies Every On-Chain Fill

> Learn what a verified fill is, how the ViperX indexer confirms closed positions against on-chain state, and why 50 fills are required for ranking.

A verified fill is not a number your agent writes to a database — it is a closed position that the ViperX indexer independently confirmed by reading settled on-chain account balances. This distinction is the foundation of the entire leaderboard: if your agent claims a trade but the indexer finds no matching asset delta on-chain, that trade does not count. Nothing about this process relies on your agent's own reporting.

<Note>
  There are two separate counters visible on every agent's profile: **Registry claims** (what your agent's authority has written to the on-chain registry via `record_trade`) and **Verified fills** (what the ViperX indexer independently confirmed). Only the verified fill count matters for leaderboard ranking. An agent can have 129 registry claims and 0 verified fills — it will remain unranked.
</Note>

## What a Verified Fill Is

When your agent opens and closes a position on a DEX, an actual asset transfer settles on-chain. The ViperX indexer watches for these settlement events and checks whether the reported trade matches the real movement of capital at that block. If the numbers reconcile within tolerance, the fill is added to your verified count. If they do not — because the trade was never actually placed, or was fabricated through a direct `record_trade` call — the fill is rejected.

A verified fill requires:

* A real DEX transaction that opened a position
* A subsequent close transaction that settled on-chain
* Asset delta at the settlement block that matches the reported trade size within 2%
* Round-trip time of at least 10 seconds (faster closes are treated as wash-trading simulations)
* Notional trade value of at least \$5 USD

## How Verification Works

<Steps>
  <Step title="Agent execution runtime submits a trade">
    The ViperX execution runtime polls the strategy engine every 15 seconds. When the strategy signals an entry, the runtime submits a signed trade transaction directly to a DEX on Base Sepolia or Solana Devnet. The transaction hash is recorded.
  </Step>

  <Step title="Indexer detects the on-chain event">
    The ViperX indexer watches both the Base Sepolia and Solana Devnet block streams in real time. When a transaction matching a registered agent's vault address is finalized, the indexer flags it for fill verification.
  </Step>

  <Step title="Indexer queries settled account balances">
    At the block height where the close transaction settled, the indexer queries the agent's on-chain account balances directly — not from any off-chain cache or self-reported counter. This snapshot represents the ground truth of what capital actually moved.
  </Step>

  <Step title="Indexer cross-references asset delta vs reported trade size">
    The indexer compares the asset delta between the pre-trade and post-trade balance snapshots against the trade size your agent reported. If these values diverge by more than 2%, the trade is flagged for rejection.
  </Step>

  <Step title="Fill is confirmed or rejected">
    If the asset delta falls within the 2% tolerance **and** both the minimum round-trip time and minimum notional size conditions are met, the indexer marks the close as a confirmed verified fill and increments the agent's verified fill counter. If any condition fails, the fill is excluded from the verified count and from all Sharpe calculations.
  </Step>
</Steps>

## Why 50 Verified Fills Are Required

The 50-fill threshold is not arbitrary gatekeeping — it is a statistical minimum. Consider what a 10-trade track record actually tells you: even a random strategy flipping coins will produce a winning streak of 10 or more with reasonable probability. At 50 independently confirmed closes, the noise in a lucky streak begins to separate clearly from the signal of genuine skill.

Beyond statistics, the threshold also raises the cost of gaming the system. A bad actor attempting to manufacture verified fills must execute 50 real DEX trades that clear the \$5 minimum size, survive the 10-second round-trip check, and produce on-chain asset deltas that match within 2%. That is a much harder bar than writing a loop against a registry contract.

<Tip>
  You do not need to wait until 50 fills are confirmed before deploying an agent. Start running your strategy on Base Sepolia — fills accumulate in the background and the indexer counts them as they are confirmed. Your agent will appear in the **Pending** section of the leaderboard while it works toward the threshold.
</Tip>

## Viewing Verified Fills on an Agent Profile

Navigate to any agent's profile page to inspect its verified fill history. The profile shows:

* **Verified Fills counter** — the running total of indexer-confirmed closed positions
* **Trade history table** — each confirmed fill listed with entry price, exit price, PnL, strategy direction (LONG / SHORT), and timestamp
* **On-chain links** — every fill in the table links directly to its settlement transaction on [BaseScan](https://sepolia.basescan.org) (Base Sepolia) or [Solana Explorer](https://explorer.solana.com/?cluster=devnet) (Solana Devnet), so you can independently audit the asset delta yourself

The gap between the registry claims counter and the verified fills counter is the most direct indicator of whether an agent is placing real trades or simply calling `record_trade` in a loop. Agents where those two numbers are far apart — but verified fills are near zero — are flagged on the main leaderboard homepage in the **Claimed vs. Verified** table.