Documents
A benchmark is a number plus the rules that produced it, published in advance. This is that set. Every document is versioned, and superseded versions stay published so the trajectory is visible.
Precedence. Methodology v1.0 is the sole governing methodology; the Rulebook v0.2 describes process only where it is consistent with it, and where any text differs, Methodology v1.0 governs.
Status. Every benchmark document below is a draft (the methodology is at version 1.0, the rulebook, benchmark statement and chain-event policy at 0.2, the others at 0.1), and the policies and notices are drafts pending counsel review unless marked otherwise. No benchmark has been published for commercial use, no committee holds a seat, and no value attested by an independent committee has been published. These rules are written before the numbers exist, which is the order that makes them rules.
| Document | What it answers | Version | |
|---|---|---|---|
| Methodology Benchmark determination, input hierarchy and committee governance; Signer Protocol v4 |
What does each seat submit, how is the fixing computed from it, what gates it, and what precedent is each rule modelled on? Crypto strike: 16:00 London (adopted 28 Sep 2026). For tokenised stocks off-hours: the OFF-HOURS SIGNED fixings at 00:00, 08:00 and 16:00 UTC, with a data-quality band (§3A; specified, not built). | 1.0 · 28 Sep 2026 Supersedes Fixing Methodology v0.1 in full, and rulebook v0.1 and v0.2 wherever they differ. Readable version: /methodology |
Read |
| Rulebook Process, where consistent with Methodology v1.0 |
Who does what, on what schedule, and what happens when a value cannot be made? Where it differs from the Methodology, the Methodology governs. | 0.2 · 28 Sep 2026 (strike rule adopted 28 Sep 2026) v0.1 stays published, marked superseded: 0.1 · 21 Sep 2026 |
Read |
| Benchmark statement Canton Series |
What does it measure, what are its limitations, and who may use it for what? | 0.2 · 29 Sep 2026 Conformed to Methodology v1.0. v0.1 stays published, marked superseded: 0.1 · 22 Sep 2026 |
Read |
| Chain and wrapper event policy | What happens on a hard fork, a reserve shortfall, a de-peg, a registrar failure or a registry migration? | 0.2 · 29 Sep 2026 Conformed to Methodology v1.0 ( NO FIXING, EVENT-<type>, one meaning of EXCEPTIONAL). v0.1 stays published, marked superseded: 0.1 · 22 Sep 2026 |
Read |
| Suitability analysis | Is this fit to underlie a regulated financial product? Today: no — and here is exactly why. | 0.1 · 22 Sep 2026 Its description of the method is superseded by Methodology v1.0; its conclusion stands. |
Read |
| Factsheets Template, cBTC Close, cBTC–cETH 50/50 |
What parameters does this specific benchmark use? | 0.1 · 22 Sep 2026 Superseded by Methodology v1.0; kept for the record. |
Read |
Policies and notices
How the administrator and the service are run. Documents marked “draft” are Draft v0.1, pending counsel review.
| Document | What it answers | Version | |
|---|---|---|---|
| Committee terms of reference | Who may hold a seat, for how long, what they must do, and how they are removed? | 1.3 · 28 Sep 2026 (Methodology v1.0 §3A, 24/7) Earlier versions stay published, marked superseded: 1.2 · 28 Sep 2026 · 1.1 · 28 Sep 2026 · 1.0 · 24 Sep 2026 |
Read |
| What we ask committee members | What each seat submits under Signer Protocol v4, what is public and what only it provides, what it never has to share, and why this is not rubber-stamping. | 2 · 28 Sep 2026 v0.1 (Signer Protocol v3, yes/no) stays published, marked superseded: 0.1 · 28 Sep 2026 |
Read |
| Policies | Complaints, consultation, errors and restatements, constituent venues, insufficient data. | 1.0 · 24 Sep 2026 | Read |
| Administrator conflicts policy | What stops the administrator pricing in its own interest? | 0.2 draft · 28 Sep 2026 Discloses the AUM-linked licence component as a conflict. v0.1 stays published, marked superseded: 0.1 draft |
Read |
| Privacy notice | What personal information do we hold, why, for how long, and what are your rights? | 0.1 draft · 28 Sep 2026 | Read |
| AI-use disclosure | What can the in-console assistant do, what can it not do, and what is stored? | 0.1 draft · 28 Sep 2026 | Read |
| Sub-processors | Which third parties host or carry the service, and which receive personal data? | 0.1 draft · 28 Sep 2026 | Read |
| Security overview | How is the service hosted and protected, what is not yet in place, and how do I report a vulnerability? | 0.1 · 28 Sep 2026 | Read |
| Incident response | How are incidents classified, and when are licensees told? | 0.1 draft · 28 Sep 2026 | Read |
| Business continuity | What happens if a component fails, or if the operator cannot continue? | 0.1 draft · 28 Sep 2026 | Read |
Not yet written
Listed so the gaps are visible rather than discovered.
- Oversight function — not constituted. The committee of seats is not an oversight function; until one exists, the administrator performs the reviews and publishes them (methodology §9).
- Constituent venue list — the criteria are in the rulebook §4.0; no venue has been admitted.
- Independent assurance — an external audit against the IOSCO principles, when a licensee requires one.
How these change
A material methodology change needs a public consultation of at least thirty days, a published summary of the comments, and then at least thirty days’ notice before it takes effect (methodology §9). Non-material clarifications take effect on publication. No change is ever retroactive: a fixing is read under the version in force at its strike.