SMALL-SAMPLE OBSERVATION REPORT · 2026-09-16
BTC Five-Minute Liquidity Observations: A Reproducible September 16 Sample
A small, dated sample of public BTC order books: budget-dependent slippage, fee estimates, sampling coverage, excluded observations and reproducible inputs.
The short answer
The September 16 collection returned 12 public snapshots from 12 requests; 11 were usable for fee-inclusive cost models across 2 market windows. The report publishes budget-level distributions, phase coverage, exclusions and complete inputs. This is a short convenience sample with correlated observations, not a representative market benchmark, trading signal or claim about future liquidity.
Evidence boundary: official documentation establishes platform mechanics and source behavior; calculations, examples and interpretations are PolyCerno Research analysis. They do not guarantee an outcome or profit.
Terms used in this guide
- Observed snapshot
- A frozen public order-book observation with its source and capture timestamps retained.
- Modeled fill
- An arithmetic allocation across supplied asks, without simulating order execution or queue priority.
- Convenience sample
- A bounded collection made when available, not a randomized or representative market-wide sample.
Collection method and denominator
On September 16, 2026, we made six paired UP/DOWN requests approximately 45 seconds apart through PolyCerno’s public read-only snapshot adapter. It normalizes Polymarket Gamma market metadata and CLOB asks. Requests were sequential, not simultaneous. The collection interval was to .
This convenience sample covers 2 market windows and 12 returned snapshots from 12 requests. 0 requests failed; 1 returned snapshots were excluded from cost summaries. Only non-empty, untruncated books with known fees and timestamps, marked VERIFIED by the adapter at capture, are usable. VERIFIED checks source context and timing; it is not a fill guarantee or an independent audit of every upstream value.
Observed cost distribution by total budget
Each budget uses the same 11 usable snapshots. Min, median and max describe this sample only; no population estimate or confidence claim is implied.
| Budget ($) | n | Complete models | Slippage min / median / max (%) | Fees min / median / max ($) |
|---|---|---|---|---|
| 10 | 11 | 11/11 | 0 / 0 / 0.000016 | 0.02096 / 0.42237 / 0.64809 |
| 50 | 11 | 11/11 | 0 / 0 / 6.195889 | 0.10478 / 2.11187 / 3.24044 |
| 100 | 11 | 11/11 | 0 / 0 / 22.987774 | 0.20956 / 4.22373 / 6.48088 |
| 200 | 11 | 11/11 | 0 / 0.06008 / 49.870928 | 0.40298 / 8.44747 / 12.96175 |
Complete means the supplied model supported the requested total budget; it does not mean a real order was filled. A zero median does not imply every observation had zero slippage.
Phase coverage, not a phase ranking
| Phase | Snapshots |
|---|---|
| opening (0–59s) | 2 |
| middle (60–239s) | 8 |
| closing (240–299s) | 1 |
Phase groups are imbalanced and too small for comparative claims. A future edition needs a predeclared sampling window and substantially broader independent coverage before discussing typical behavior.
Observation and exclusion ledger
| Index | Market / side | Fetched at | Included | Exclusion |
|---|---|---|---|---|
| 0 | btc-updown-5m-1789533900 / UP | 2026-09-16T04:46:37.734Z | Yes | — |
| 1 | btc-updown-5m-1789533900 / DOWN | 2026-09-16T04:46:38.437Z | Yes | — |
| 2 | btc-updown-5m-1789533900 / UP | 2026-09-16T04:47:24.234Z | Yes | — |
| 3 | btc-updown-5m-1789533900 / DOWN | 2026-09-16T04:47:24.845Z | Yes | — |
| 4 | btc-updown-5m-1789533900 / UP | 2026-09-16T04:48:10.505Z | Yes | — |
| 5 | btc-updown-5m-1789533900 / DOWN | 2026-09-16T04:48:11.226Z | Yes | — |
| 6 | btc-updown-5m-1789533900 / UP | 2026-09-16T04:48:57.025Z | Yes | — |
| 7 | btc-updown-5m-1789533900 / DOWN | 2026-09-16T04:48:57.851Z | Yes | — |
| 8 | btc-updown-5m-1789533900 / UP | 2026-09-16T04:49:43.543Z | Yes | — |
| 9 | btc-updown-5m-1789533900 / DOWN | 2026-09-16T04:49:44.251Z | No | Empty, truncated, stale/provisional book or unknown fees/time |
| 10 | btc-updown-5m-1789534200 / UP | 2026-09-16T04:50:29.953Z | Yes | — |
| 11 | btc-updown-5m-1789534200 / DOWN | 2026-09-16T04:50:30.640Z | Yes | — |
Download and independently recalculate
Download observed inputs (JSON) · Download calculated results (JSON)
Input file SHA-256: 8968097efcbbba3c45b6a66183b3ef2e14ed1a2a96d93e2ce6ebcf4b51829add. Values are frozen historical observations, not current quotes. The files contain public market data, not account or user records.
The companion recorded-book case walks through two inputs. Use the calculator to reproduce the arithmetic. To cite this edition, link this page and retain its date, 11-snapshot denominator and limitations.
Limitations and future editions
There are only 11 usable snapshots from 2 windows. Repeated observations are correlated, and UP/DOWN quotes were not fetched simultaneously. This is not a random sample, a long-term market benchmark, a latency study, a settlement reconstruction or evidence of a profitable strategy. The sample cannot establish which phase is normally more liquid.
We walk visible asks with fractional shares and the captured fee curve, using a total budget including estimated fees. Slippage is relative to the best ask in that same snapshot. Per-level fee rounding differs from possible real per-match rounding. Minimum size, tick/order constraints, cancellations, queue position and changing prices are not simulated. Unavailable values are excluded, never replaced by zero.
This edition is frozen. Future observations must have a new dated input artifact, documented capture interval and reviewed method. There is no automatic production collector or auto-publication job.
Sources and further reading
Article updated . Source interfaces and market rules can change; verify the current market before relying on a field. Teaching numbers are constructed examples; source facts and calculations should be read separately.
Put settlement, direction, execution and confirmation on one clock.
Explore the recorded BTC 5-min demo and the evidence behind each directional read.