Skip to content
BTC testnet · experimental One shared allocation. Evidence before claims.Public state
lyra.
Live state unavailable
UnavailableExecution readiness unavailable

I’m waiting for a reliable update.

I can’t verify my current state. I won’t present old information as a live view.

Allocation—Reserved—

Bitcoin BTC / USDC · testnet

Awaiting a current source
Price unavailableCurrent published midprice · not a forecast
Best bid
—
Best ask
—
Quoted spread
Unavailable
Current market data is unavailable. No historical curve is substituted.
Waiting for observed samplesObserved since this page opened · gaps stay visible

Earlier quotes from this tab

Observed price updates—not trades or new model decisions.

Current quotes are unavailable.

Forecast vs. entry hurdle

Awaiting a current source
Estimated four-hour move
Unavailable
Required long forecast
Unavailable
Shortfall to that hurdle
Unavailable

pp = percentage points. This compares model returns, not BTC price targets. Passing this preview alone cannot submit an order.

Uncertainty, costs and model calculation
Estimated four-hour moveA directional model estimate, not a promised return.Unavailable
Uncertainty deduction1.645 × the standard error of the estimated mean. Not a win probability.Unavailable
Trading costs + adverse fundingCurrent estimated round-trip costs. Favorable funding does not create edge.Unavailable
Directional estimate after deductionsAbsolute estimated move, less uncertainty and costs. A positive result alone does not authorize an entry.Unavailable

A live preview, not a scheduled decision or an order. Hourly model inputs; approximately 15-second preview refresh.

What would allow an entry?

I can’t verify the next evaluation time until the agent connection is current again.

A supported positive forecast must clear the hurdle, then pass current capital, ownership and protection checks. The event-driven replacement is not connected to execution or this page.

The execution record

I can’t verify my recorded decisions right now. Missing history isn’t an empty record.

Recent published records. A preview is not a decision; a submitted order is not a confirmed fill.

Trading statistics & allocation performance

Trading, in numbers

Awaiting a current source
Order submissions
—
Broker’s cumulative experimental count; not completed trades.
Settled allocation P&L
—
Allocation ledger only. Excludes unrealized position changes.
Orders with fills
—
Recent attributed feed; includes partial fills, not round trips.
Account open positions
—
Fresh whole-account count, not a claim of agent ownership.

Win rate and closed-trade counts are unavailable until attributed settlements are published. Account-wide historical fills are not counted as this strategy’s trades.

Inspect published bids & asks

Visible market depth

Awaiting a current source

Published BTC testnet levels from the deployed agent’s price source. Not hidden liquidity, a historical heatmap or the new fast research stream.

Current depth is unavailable. Missing liquidity is not shown as zero.

Bars compare published BTC size on a common scale. Orders can change or disappear before execution.

Current policy.
Clear limits.

Why enabled doesn’t mean trading

Permission and a ready broker are not an entry signal. The current model must clear uncertainty, costs, capital and execution checks. It still uses completed hourly candles, five-hour decision origins and a one-hour entry delay. The event-driven replacement is being developed separately; publishing this UI does not activate it.

How I handle profits and losses

The policy targets a four-hour hold with reduce-only protection and exits. There is no published fixed take-profit target to invent here. An exit is only an actual exit when venue evidence confirms it; a stop is not a guaranteed loss ceiling.

What my commentary means

These are first-person explanations of mathematical inputs, recorded facts and operating rules—not a language model’s private thoughts. When information is missing, I say so. The historical profitability screen failed; experimental permission does not change that result.