Does the currently published dataset contain enough usable evidence for my research task? · By CoinNudge Research · Method reviewed 2026-09-13 · Guide updated 2026-09-13 · Historical study updated · Observation range: – · Calculation historical-evidence-1.2 · Auto-refresh about every 21600 seconds
Market Events v1 coverage by symbol and event type
Current answer: As of , using CoinNudge local archive; source and scope stated in each row: 9 active daily releases contain 1567 published rows. The downloadable symbol × event-type matrix separates locally-known, retrospective, active-buy-valid, 24h-complete and missing-any counts, including explicit zero cells for every fixed symbol and event family. Counts describe Market Events v1, not reconstructed studies elsewhere in this batch.
Historical study updated
Subscribe to research data · Check a real sample · Get Telegram alerts
Current source-backed snapshot
This coverage report reads active Market Events v1 releases and separates the daily release ledger from a downloadable symbol × event-type matrix. The matrix reports total rows, events or controls, locally-known versus retrospective features, usable active-buy context, complete 24-hour outcomes and rows missing any required research dimension. Use the matrix—not the all-release total—to decide whether a specific research question has enough evidence. Reconstructed studies elsewhere in Research remain separate outputs.
Input documentation: CoinNudge public data API documentation · CoinNudge methodology
Observation window: Requested windows and actual coverage are recorded separately
Calculation cadence: Auto-refresh about every 21600 seconds
Calculation version: historical-evidence-1.2
Download current dataset: JSON · CSV Raw values retain the dataset's published precision. Free fair-use limit: 60 requests per minute per IP, shared across all Research JSON and CSV endpoints.
| UTC day | Rows | Events | Controls | 24h complete | Feature availability | Active-buy validity | Pinned release ID |
|---|---|---|---|---|---|---|---|
| 2026-09-13 | 101 | 71 | 30 | 0 | {"locally_known":101} | {"usable":101} | 5aa0da525878597cfc5bd55203808d50cca25e348e8312538bc2624e2411bfc6 |
| 2026-09-12 | 172 | 97 | 75 | 78 | {"retrospective":75,"locally_known":97} | {"usable":172} | 9e1895212765e234b4caa507ff8fb5093bee1557d9319e1ac8f1c4fb728a5636 |
| 2026-09-11 | 196 | 133 | 63 | 196 | {"retrospective":196} | {"usable":196} | 71dec5b90caba1cb43a485fb348d0fac12aa6dabdea3cfe02bc50a41ba296f50 |
| 2026-09-10 | 179 | 98 | 81 | 179 | {"retrospective":179} | {"usable":179} | 77ac0f931e719c89ac91bd0689916dfafe9476af8f0731c4ee9b1fe4c12fb59a |
| 2026-09-09 | 212 | 151 | 61 | 212 | {"retrospective":212} | {"usable":212} | c4cc2e5ad018104f10eae1cb91382c448a07258d2fac8f6dcda8f3127735e5d7 |
| 2026-09-08 | 188 | 116 | 72 | 188 | {"retrospective":188} | {"usable":188} | 01fc93bd44c716d482d50890253ece2b3672baa97b23463f65a781a90d7c0116 |
| 2026-09-07 | 196 | 133 | 63 | 196 | {"retrospective":196} | {"usable":196} | 573000cfa81ba29a15a03776026e476d76dfa6d808dc3132532c253965e97c0e |
| 2026-09-06 | 189 | 125 | 64 | 189 | {"retrospective":189} | {"usable":189} | 6136ed31245cd95c92e46a8e14e146eba694cd891d64b8705a03fec731f135d8 |
| 2026-09-05 | 134 | 99 | 35 | 134 | {"retrospective":134} | {"usable":134} | 43eee62b3744f4c9361b204e01b6e03d6483a93b8f050d948292d5444356579d |
Observation evidence
First 30 of 48 observations. JSON and CSV contain all published evidence. CSV dataset_section distinguishes summary and observation rows.
| symbol | event_type | rows | events | controls | locally_known | retrospective | feature_missing | active_buy_usable | outcome_24h_complete | missing_any | coverage_status | calculation_version |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| BNBUSDT | price | 5 | 5 | 0 | 0 | 5 | 0 | 5 | 5 | 0 | observed rows | historical-evidence-1.2 |
| BNBUSDT | volume | 23 | 23 | 0 | 5 | 18 | 0 | 23 | 18 | 5 | observed rows | historical-evidence-1.2 |
| BNBUSDT | rsi | 4 | 4 | 0 | 0 | 4 | 0 | 4 | 4 | 0 | observed rows | historical-evidence-1.2 |
| BNBUSDT | macd | 50 | 50 | 0 | 3 | 47 | 0 | 50 | 47 | 3 | observed rows | historical-evidence-1.2 |
| BNBUSDT | ema | 28 | 28 | 0 | 3 | 25 | 0 | 28 | 25 | 3 | observed rows | historical-evidence-1.2 |
| BNBUSDT | bollinger | 43 | 43 | 0 | 5 | 38 | 0 | 43 | 38 | 5 | observed rows | historical-evidence-1.2 |
| BNBUSDT | flow | 9 | 9 | 0 | 2 | 7 | 0 | 9 | 7 | 2 | observed rows | historical-evidence-1.2 |
| BNBUSDT | control | 92 | 0 | 92 | 15 | 77 | 0 | 92 | 77 | 15 | observed rows | historical-evidence-1.2 |
| BTCUSDT | price | 5 | 5 | 0 | 0 | 5 | 0 | 5 | 5 | 0 | observed rows | historical-evidence-1.2 |
| BTCUSDT | volume | 27 | 27 | 0 | 2 | 25 | 0 | 27 | 25 | 2 | observed rows | historical-evidence-1.2 |
| BTCUSDT | rsi | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | zero observed rows | historical-evidence-1.2 |
| BTCUSDT | macd | 58 | 58 | 0 | 7 | 51 | 0 | 58 | 51 | 7 | observed rows | historical-evidence-1.2 |
| BTCUSDT | ema | 39 | 39 | 0 | 7 | 32 | 0 | 39 | 32 | 7 | observed rows | historical-evidence-1.2 |
| BTCUSDT | bollinger | 39 | 39 | 0 | 5 | 34 | 0 | 39 | 34 | 5 | observed rows | historical-evidence-1.2 |
| BTCUSDT | flow | 16 | 16 | 0 | 5 | 11 | 0 | 16 | 11 | 5 | observed rows | historical-evidence-1.2 |
| BTCUSDT | control | 78 | 0 | 78 | 10 | 68 | 0 | 78 | 69 | 9 | observed rows | historical-evidence-1.2 |
| DOGEUSDT | price | 6 | 6 | 0 | 0 | 6 | 0 | 6 | 6 | 0 | observed rows | historical-evidence-1.2 |
| DOGEUSDT | volume | 22 | 22 | 0 | 4 | 18 | 0 | 22 | 18 | 4 | observed rows | historical-evidence-1.2 |
| DOGEUSDT | rsi | 4 | 4 | 0 | 0 | 4 | 0 | 4 | 4 | 0 | observed rows | historical-evidence-1.2 |
| DOGEUSDT | macd | 53 | 53 | 0 | 5 | 48 | 0 | 53 | 48 | 5 | observed rows | historical-evidence-1.2 |
| DOGEUSDT | ema | 34 | 34 | 0 | 3 | 31 | 0 | 34 | 31 | 3 | observed rows | historical-evidence-1.2 |
| DOGEUSDT | bollinger | 36 | 36 | 0 | 6 | 30 | 0 | 36 | 30 | 6 | observed rows | historical-evidence-1.2 |
| DOGEUSDT | flow | 2 | 2 | 0 | 0 | 2 | 0 | 2 | 2 | 0 | observed rows | historical-evidence-1.2 |
| DOGEUSDT | control | 93 | 0 | 93 | 14 | 79 | 0 | 93 | 80 | 13 | observed rows | historical-evidence-1.2 |
| ETHUSDT | price | 6 | 6 | 0 | 0 | 6 | 0 | 6 | 6 | 0 | observed rows | historical-evidence-1.2 |
| ETHUSDT | volume | 22 | 22 | 0 | 3 | 19 | 0 | 22 | 19 | 3 | observed rows | historical-evidence-1.2 |
| ETHUSDT | rsi | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | zero observed rows | historical-evidence-1.2 |
| ETHUSDT | macd | 52 | 52 | 0 | 8 | 44 | 0 | 52 | 44 | 8 | observed rows | historical-evidence-1.2 |
| ETHUSDT | ema | 35 | 35 | 0 | 3 | 32 | 0 | 35 | 32 | 3 | observed rows | historical-evidence-1.2 |
| ETHUSDT | bollinger | 43 | 43 | 0 | 5 | 38 | 0 | 43 | 38 | 5 | observed rows | historical-evidence-1.2 |
Historical reconstruction is not proof of information available then or an executed return.
How to read this page
- Does the currently published dataset contain enough usable evidence for my research task?
- Market Events v1 active daily releases; six specified Binance spot pairs, not the full internal archive.
- Read actual coverage and missing values before comparing outcomes.
- Download the evidence; distinguish historical reconstruction from locally recorded events.
What can this page tell you quickly?
- Best for
- Does the currently published dataset contain enough usable evidence for my research task?
- Measured scope
- Market Events v1 active daily releases; six specified Binance spot pairs, not the full internal archive.
- Update schedule
- Recalculated every six hours; completed-window studies exclude the ongoing UTC day.
- Do not infer
- No guaranteed trading edge, complete point-in-time history or automatic entitlement to every data family.
What do event and control counts actually represent?
An event is a recorded public rule trigger represented by the product's schema. A control is a scheduled hourly observation without a recorded qualifying event in the preceding hour. It is not proof that no other signal existed, and it is not a statistically matched control.
The counts help reveal selection imbalance before analysis. A large number of controls cannot compensate for too few events of a specific kind, coin or market regime. Inspect the real sample and filter by your intended research question instead of relying on total rows.
Why separate feature availability from completed outcomes?
A fully matured forward return does not establish that its input features were available at the original event time. Retrospective context was recovered later and must not enter a point-in-time model as if it were known then.
Similarly, a valid price field does not guarantee valid active-buy context. The manifest preserves each dimension's quality counts so a researcher can determine which filters will reduce usable sample size. Missingness is part of the product description, not an inconvenient detail to hide.
How do I reproduce a downloaded study later?
Choose a daily release ID, save its field dictionary and verify the file checksum. Keep the same release when querying additional API pages. A later active release can improve coverage without silently changing the rows in the release you pinned.
This public ledger is not the full paid dataset. Inspect sample rows first, review the public API documentation and only then compare data plans. Specialized derivatives, longer history or redistribution requirements need a separate confirmed scope; a fixed subscription does not grant every internal data family.
How can I audit and cite this measurement?
| Check | What to verify | Why it changes interpretation |
|---|---|---|
| Scope | Market Events v1 active daily releases; six specified Binance spot pairs, not the full internal archive. | Do not generalize a named sample to the whole crypto market. |
| Formula | Read only active immutable releases, verify stored row counts, and aggregate a second ledger by symbol and event type. Publish locally-known, retrospective, feature-missing, active-buy-usable, 24-hour-complete and missing-any counts without mixing superseded release versions. | A similarly named indicator can use a different convention. |
| Data time | Observation window versus materialization time | A fresh computation is not necessarily a fresh source observation. |
| Delivery | Public evidence versus subscribed Market Events v1 | Inspect the data catalog before assuming commercial inclusion. |
What is measured, and what is not?
| Measured claim | Evidence on this page | Boundary |
|---|---|---|
| Does the currently published dataset contain enough usable evidence for my research task? | The current table and downloadable rows using event-dataset-coverage. | Market Events v1 active daily releases; six specified Binance spot pairs, not the full internal archive. |
| Results can be checked against an explicit computation. | Read only active immutable releases, verify stored row counts, and aggregate a second ledger by symbol and event type. Publish locally-known, retrospective, feature-missing, active-buy-usable, 24-hour-complete and missing-any counts without mixing superseded release versions. | Archive availability and revisions constrain historical reproducibility. |
Method and data boundary
Read up to 100 active daily manifests without adding superseded versions. Verify each immutable row file against its declared row count, then group records by symbol and event type; controls form their own type. Count locally-known, retrospective, feature-missing, active-buy-usable and 24-hour-complete rows. missing_any means at least one of feature availability, active-buy validity or 24-hour outcome maturity is absent. Daily and matrix totals remain independently downloadable.
Market Events v1 active daily releases; six specified Binance spot pairs, not the full internal archive. Historical results are descriptive, not executed profits or guaranteed future behavior.
Sources and verification
- CoinNudge public data API documentationRelease selection, fields, delivery boundaries and reproducible querying.
- CoinNudge methodologyShared boundaries, data time semantics and calculation contracts.
Frequently asked questions
Does the currently published dataset contain enough usable evidence for my research task?
This coverage report reads the active published daily releases of Market Events v1 and exposes their row counts, event/control split, feature availability, active-buy validity and complete 24-hour outcomes. It is a data-quality ledger, not another pricing page. Use it to decide whether the current release history can support your proposed study before purchasing. The reconstructed breakout, volume and RSI studies elsewhere in Research are separate analytical outputs and are not automatically included in this subscription.
How often do the numbers change?
A bounded background calculation runs at most every six hours. Look at the actual observation interval as well as the calculation time; missing and pending data are not filled with zero.