Every value of the OCX index is cryptographically sealed, and each daily record is anchored in Bitcoin. Once sealed, the history cannot be altered, and any third party can verify the complete record directly, without relying on OCAPACITY. The resources below make this verification possible.
The chain head is a hash that reveals no index values, so it is served in real time. The anchors list shows which heads have been timestamped in Bitcoin, together with their status.
Download a daily OpenTimestamps proof and verify it against Bitcoin, either with the ots client (ots verify) or by uploading it at opentimestamps.org. The result identifies the exact Bitcoin block attesting that the head existed at that time.
The full history is published on a time delay: the sealed records, the published index values, and the raw onchain inputs. After retrieving them, run the open-source verifier, which re-derives every value from its inputs and validates the hash chain from genesis to head. Any alteration to the data causes verification to fail.
The complete sealed history is public but time-delayed, allowing any party to audit the index independently. The live, real-time feed is the licensed product. This is the same structure used by established benchmarks such as S&P, MSCI, and CBOE.
Hash-only resources, namely the head and the Bitcoin anchors, are served in real time because they reveal no values. The resources that carry index values (the chain payloads, observations, and raw inputs) are released after a delay.
What is cryptographically guaranteed: that the published history has not been altered since it was sealed and anchored in Bitcoin, and that every value can be recomputed from its inputs.
What is governed rather than fixed: the methodology may be refined over time. Each sealed record records its methodology version, and every change is documented in a public changelog, so the index can evolve while the historical record remains immutable. Methodology changes are decided and announced before their effect is known.
What remains in development: the track record is short and accrues forward. Certain inputs, such as live mempool and priority-fee sampling, cannot be reconstructed retroactively, so coverage increases over time. These limitations are disclosed deliberately, as the credibility of a benchmark derives from transparent disclosure rather than from claims of maturity it has not yet attained.