Bitcoin above October 2 odds cluster under 86k

Bitcoin above October 2 is a ladder of Polymarket threshold contracts that resolve on the Binance BTC/USDT 1-minute close at 12:00 ET, and CoinRithm's live mirror on October 2 is the second surface this desk used beside Polymarket's own event page.

What actually happened

Bitcoin above October 2the threshold ladder is not the same market as Bitcoin up or down on October 2. The up-or-down contract already has a memcool note. This ladder asks whether BTC is above specific prints at a fixed minute. CoinRithm showed 24h volume around $1.1 million and liquidity around $538k on the aggregate event when checked. Those venue stats move. The hinge row on that check was 86,000 at 51%, with 88,000 already down at 10%.

Lower rungs at 100% are not a victory lap. They mostly say the market thinks those prints are already cleared or trivial. The information is in the first row that is not maxed. On the CoinRithm snapshot, that fight sat between 84k and 88k.

What Polymarket thinks

For the article field, this desk uses the 86,000 Yes probability near 51% from CoinRithm's Polymarket-sourced table on October 2. If you need 84,000, that row was about 92% on the same mirror. Do not average 51 with 92. They are different strikes.

Readers comparing the directional contract can open the October 2 Bitcoin odds note. Readers watching ETH thresholds can open the Ethereum above October 2 note once live. Macro-sensitive odds still live on the Polymarket October Fed odds note.

Primary links: CoinRithm's the threshold ladder mirror and Polymarket's event page.

How to read a noon-ET ladder

Resolution is a single Binance close, not your exchange, not a TWAP, not Coinbase. If Binance prints below the strike at that minute, Yes shares go to zero even if another venue was above. Fee and tick details on CoinRithm noted fees yes and a 0.1 point tick. That is venue plumbing, not alpha.

Up-or-down compresses the day into a binary against the previous window. Threshold ladders expose where the crowd's certainty breaks. On the October 2 morning mirror, certainty broke hard above 86k. That can change by lunch. The article's job is to show the shape of the board, not to freeze a candle that has not printed.

The desks and mirrors cited above are enough to report the board without inventing a third number. If a later screenshot disagrees, keep both timestamps and do not blend them.

Extra board notes

CoinRithm's related rails on the same page pointed at shorter BTC price markets for specific Eastern clock hours on October 2. Those are not the daily threshold ladder. Mixing a 2am EDT ladder into a noon ET sentence is how bad threads get born. Stick to the contract title you opened.

Liquidity near half a million dollars sounds deep until the strike you want is the thin one. The 86k row can move harder than the 74k row even if the event header shows fat total volume. Read the outcome line, not only the event header.

If you are comparing this board to last week's "Bitcoin above 84,000" style contracts already archived on memcool, remember those were different resolve dates. A 92% on 84k today is not a continuation of an older contract's chart without checking the slug.

Settlement arguments after the fact will cite Binance. If Binance is mid-incident at noon ET, read the market rules before you invent a backup index. The CoinRithm rules blurb pasted Binance as the source; it did not paste a committee of exchanges.

People hedging jobs-day macro into crypto thresholds should also keep the September jobs report note in another tab. Correlation narratives are cheap. Resolution rules are not.

What to do as a reader

Screenshot the row you care about with a timestamp. Cite the threshold ladder with the strike attached. Nothing here is a trade. Not financial advice. DYOR, ser.