DXAP

A recorded recovery · Historical Hyperliquid mainnet · August 25, 2026

Velvet resumed a turn after two transient render errors

Velvet’s first two attempts failed while assembling the prompt context. A third attempt assembled context and completed the same turn. Its final summary held an existing BTC long; the turn produced no execution or new live fill.

This is a selected pre-alpha record from Velvet Momentum Ranger. 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 recovery sequenceRender retry, then Render retry, then Completed hold 1 Render retry 2 Render retry 3 Completed hold
  1. 1Render retry
  2. 2Render retry
  3. 3Completed hold
The three stages above summarize the recorded sequence; the dated rows below carry the evidence and limits.

At a glance

Attempt outcomes
2 render failures; 1 completed turn
Executions in this turn
0
Live fills in this turn
0

What happened

  1. First attempt failed

    The archived attempt ended with a prompt-render connection reset before a decision could be completed.

  2. Second attempt failed

    The retry ended with the same prompt-render failure class. Neither failed attempt generated an execution or live fill.

  3. Third attempt completed

    Context assembled successfully and the turn completed. The final summary recorded a hold of an existing BTC position, with no new trade in this turn.

What the record supports

The attempt records show recovery within one turn after two transient rendering failures. The completed action and execution records show no increase in exposure from that turn.

What it cannot prove

This is evidence of a completed retry in one recorded turn, not a guarantee that every service failure recovers.

The turn’s summary describes an existing position; this case does not evaluate that position’s return or any later outcome.

Source and method

DXRG reconciled the selected archived records on September 26, 2026. The source classes used here are three finalized attempt records, context snapshot, completed turn action, execution and 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