Crypto market-data symbols

Ballast keeps broker/watchlist symbols such as HYPE-USD separate from the provider's chart identifiers. bot/config.py::YAHOO_ALIAS maps reviewed exceptions to the correct Yahoo asset. This mapping is shared by crypto quotes, rolling 24-hour references, volatility history, the trend filter and historical backtests. The returned quote keeps the broker symbol.

Hyperliquid correction — 0.4.15-beta candidate

Hyperliquid uses HYPE32196-USD on Yahoo. The bare HYPE-USD endpoint returned 404 during the September 22, 2026 investigation, while the mapped endpoint returned Hyperliquid USD and hourly candles. This source correction adds the alias for the local 0.4.15-beta candidate. The published baseline remains 0.4.14-beta.

Robinhood lists Hyperliquid as supported, with regional restrictions. Public availability does not prove eligibility for a particular account or API. Ballast's existing pair verification, deliberate watchlist enrollment and ordinary entry gates still apply. An alias does not enroll an asset or place an order. A missing provider response still produces unavailable data.

Existing history caches retain their normal refresh intervals. Installing a reviewed release with this mapping does not rewrite captured stops or guarantee an immediate trade. Core display and terminal residual closure are separate from this data correction; see Core inventory.

References checked September 22, 2026:

0.4.15-beta availability handling

Every cycle requests broker prices for enrolled coins, protected Core and existing crypto trades, including trades removed from the current watchlist. A live broker price keeps exit evaluation available when the chart feed fails. New purchases need a usable current price and dip reference; price disagreements over the existing 25% check block entries and are visible in System. Mode-specific 24-hour observations and mode-scoped data status prevent simulated observations from supplying live dips. A new listing with missing data remains visibly pending and is retried. A detected provider/broker identity mismatch prevents enrollment. No ticker aliases are inferred from similarly named assets: reviewed aliases apply consistently across quotes, volatility, trends and backtests. Broker eligibility, history availability, entry rules and account funding still determine whether an order can be placed. An unknown trading increment blocks submission instead of assuming precision.

0.4.16-beta paused display

The running dashboard now refreshes public quotes for enrolled and owned crypto even when the bot is off. Refresh attempts are limited to eight symbols per scheduler pass and throttled per symbol for one minute, with mode-scoped retry state. It preserves a newer engine write and keeps original timestamps when a feed fails. It does not call the broker or populate strategy observations. Both bare and -USD detail requests use one canonical crypto identity. A displayed price is not proof that a broker order or an entry is available.

Live crypto sale sizing requires a usable broker holdings balance to verify Core. Since 0.4.20 each trade is also bounded by its own ledger (bought minus sold minus retained Core); the owner reserve is retired. Failure holds the sale and alerts the owner; public display prices cannot substitute for that ownership check.