Dogecoin 15-minute to-beat windows

There is no high and there is no low, at any licence this desk can hold. The 15-minute crypto windows settle on a CF Benchmarks real-time index, which is an order-book-derived value published about once a second — it is a stream, not a bar, so an intra-window range would have to be constructed by us from data we are not permitted to store or show. Four doors, all closed, and they are closed for four different reasons. What this desk draws instead is a BODY-ONLY BAR: open is the number to beat, close is the realized settlement value, and the colour is the sign of the difference. Every pixel of that is a published venue number. `components/indices/IndexPriceChart.tsx:16-22` is the standing precedent for why the missing pieces are not simply filled with the pieces we have: "Feeding o=h=l=c to a candle renderer would draw a row of doji, and a doji is a CLAIM." So is a wick.

Measured 2026-09-10: Twenty-five sources surveyed against their own published terms, 2026-09-10. NOTHING is available free: Coinbase forbids redistributing or DISPLAYING the data and separately forbids using it to create "indexes, fixings, or other benchmarks"; Binance.US forbids "public display" of anything obtained through its API; Gemini permits personal and internal use only and requires a Redistribution Agreement; Kraken licenses its content "only for your own benefit"; and CF Benchmarks — the actual settlement basis, and Kraken-owned — requires a licence to use or distribute at all and publishes no fee. Pyth is explicit at the tier level: its free plan grants "No display, non-display, or redistribution rights". Alpaca is the one free keyless crypto-bar endpoint and it fails twice over: its terms allow the data "exclusively for personal and noncommercial access", and the bars are drawn from Alpaca's own venue, which returned n=0 trades on every 1-minute bar sampled — moving OHLC over zero volume. No exchange REST endpoint surveyed serves sub-minute bars either, so a genuinely smooth candle needs websocket aggregation, which is a derived work and a harder licence rather than an easier one.

Retires when A display licence is signed for a source that permits BOTH public display and derived calculation. Five surveyed sources grant some form of it and not one of them cleanly. CoinAPI publishes the plainest permission — its FAQ answers "Can I use the API to show graphs, charts or tables?" with "Yes, you can use our data to display graphs, charts, or tables", and it markets benchmark creation — from USD 79 a month, but its Customer Agreement licenses the service "for your internal business purposes only" and never once uses the word display, so that right has to be written into the order form before a chart ships on it. Bitstamp grants display AND "the right to create ratios, calculations, new original works, statistics" in published terms, at a quote-only fee. Kaiko sells a named display licence, and Amberdata grants display to a subscriber's own users plus dashboards and rankings — both quote-only, and both now one company. Tiingo is the trap: it publishes a display price (USD 250 startup, USD 500 enterprise) while its section 1.4(h) forbids "publishing or otherwise making available to the public any analysis" and forbids benchmarking, and its section 1.6(c) names CHARTS as a prohibited derived product. None of them retires the deeper problem: a candle built from exchange TRADE data is a different quantity from the order-book mid these contracts settle on, so it would sometimes draw a body crossing the threshold on a window the venue settled the other way. Only a CF Benchmarks licence, or a written data authorization from Kalshi — whose API already carries the BRTI value feed at 5Hz to entitled accounts — gives a wick at the basis this desk actually publishes.

No, and this desk measured that rather than asserting it. The resolution history is honest AS HISTORY — those windows really did settle that way — and it carries no predictive information about the next one. The conditional rate after a yes is 1.2 points LOWER than the rate after a no, which is the opposite direction from the one a continuation story needs, and the mean run is very slightly SHORTER than a fair coin's. Those figures ship on the surface beside the run itself, with their n, which is why the run is shown at all: hiding it would be hiding a real record, and showing it without the measurement would be publishing a suggestion. This desk prints no direction, ranks nothing, and recommends nothing.

Measured 2026-09-09: 1,000 consecutive settled KXBTC15M windows (251.75 hours): P(yes | previous yes) 0.4804 against P(yes | previous no) 0.4922; mean run 1.98 against a fair coin's exactly 2.00; run histogram {1:245, 2:140, 3:57, 4:36, 5:14, 6:10, 7:2, 8:2}, longest run 8.

Structural — nothing on a roadmap retires this.

No, and the breaks are drawn as breaks. Windows go missing at the venue, and a renderer that joined the rows either side of a hole would draw price action across a span nobody observed — the same fabrication as a wick, in a different direction. A missing window therefore emits an explicit null and the line breaks. `lib/indices/intraday.ts:30-36` is the estate's standing rule for this: renderers break the line, they do not bridge it. The statistics obey the same rule — a pair of outcomes either side of a hole is not a consecutive observation and is excluded from every conditional rate.

Measured 2026-09-09: a real 135-minute hole — eight missing consecutive windows — exists in a single 10.5-day span of the measured KXBTC15M sample.

Structural — nothing on a roadmap retires this.

It does not exist to fetch. The venue's archive of settled 15-minute windows is walled at roughly 60 days, and past the wall the API does not error — it returns HTTP 200 with an empty page, which is the failure mode a loader silently renders as "quiet market". Depth beyond the wall can only accrue from the day WET starts persisting windows, one day at a time, and until then an empty store publishes THIS SENTENCE rather than a blank chart or a "no history" label.

Measured 2026-09-09: max_close_ts 60 days back returns a full page; at 90 and at 150 days the same request returns 200 with ZERO rows. One request at limit=1000 covers 251.75 hours (10.5 days); limit=100 covers 24.75 hours, so an hourly capture has about 24x slack.

Retires when the stored window history is itself deeper than the venue's ~60-day wall. This one retires by the calendar rather than by a build — one day per day, from first capture.