DXAP

A recorded no-trade · Historical Hyperliquid mainnet · September 8, 2026

Why Owl passed on a VVV breakout

Owl logged a decision to stay flat. Its recorded market reading put VVV above the one-hour rally threshold but also above the owner’s four-hour no-chase ceiling. This was the agent declining an entry under its historical strategy, not the policy engine rejecting an order.

This is a selected pre-alpha record from Owl. It describes what the archived turns and fills show, not a current trading result or a return promise. The public agent profile shows the agent’s current shared configuration, which may differ from the historical one.

A recorded no-trade sequenceMarket scan, then Strategy ceiling, then No order 1 Market scan 2 Strategy ceiling 3 No order
  1. 1Market scan
  2. 2Strategy ceiling
  3. 3No order
The three stages above summarize the recorded sequence; the dated rows below carry the evidence and limits.

At a glance

Turn completed
22:55:43 UTC
Executions
0
Live fills
0

What happened

  1. Decision context assembled

    The turn used the historical strategy revision that contained a 15% four-hour no-chase rule.

  2. Agent recorded no trade

    Its summary reported VVV at +10.827% over one hour and +35.423% over four hours. It said all other candidates failed the first entry criterion.

  3. No order submitted

    The turn has one completed summary action, no execution record, and no live fill.

What the record supports

The logged reason names a specific owner-set rule rather than offering a generic “wait for better conditions” explanation.

The archived strategy revision contains that four-hour ceiling, and the action and fill records agree that the agent placed no order in this turn.

What it cannot prove

The market percentages are values in the agent’s recorded explanation. This case did not independently rebuild the point-in-time VVV market tape.

This one no-trade does not show that abstaining improved returns or that every later turn followed the same rule. The current public profile may use a different configuration.

Source and method

DXRG reconciled the selected archived records on September 26, 2026. The source classes used here are finalized turn, turn action, context snapshot, historical configuration revision, live-fill absence. Account and wallet identifiers, provider order IDs and unrelated private payloads are withheld. Download this public case record as JSON. For the evaluation standard behind these distinctions, read DXRG’s benchmark card.

See how DXAP works.

Describe a strategy, set the limits, and review your agent’s decisions on a Hyperliquid account you control. Historical cases are not instructions to copy these trades.

Explore the productBrowse public agents