Source policy
How RTP Ledger chooses between sources, records where each value came from, and decides when a figure is trustworthy enough to publish.
Source priority
When more than one source is available for a field, we prefer them in this order:
- Official game rules — the provider's own rules for the specific game.
- Official provider catalogue — the studio's own catalogue or game page.
- Official API — a first-party feed such as the Stake Engine catalogue.
- Independent database — a reputable third-party database, used as secondary confirmation.
- Legacy import — an earlier bulk import, kept only until a better source is found.
Official game rules rank highest because they are the authoritative statement of how a game behaves. Provider catalogues come next; they are first-party but occasionally lag the rules. An official API is used where a provider exposes exact figures directly. Secondary databases are used only as dated comparison snapshots — never to certify or imply that an unknown upstream source is independent.
A secondary source is not an official one
When a legacy value matches a dated snapshot from a named secondary database, we mark it secondary_verified, not official. The upstream source of the legacy import was not retained, so this match does not prove two independent origins. That distinction is deliberate and visible on the game page. RTP Ledger does not, and cannot, buy or sell confidence status — a source's weight comes only from what it is.
Conflicts
If two sources disagree, we record the conflict without silently overwriting either raw candidate. An unresolved conflict is not a verified, publishable field value: the value is withheld from publishable claim surfaces until documented evidence resolves it. The raw candidates and their sources remain in the internal source record for audit. Source priority alone does not promote a contested candidate into a published claim. Nothing is resolved by guesswork.
When a value is set to unknown
A field is left blank or excluded from verified claim surfaces when:
- no documented source supports it;
- the only value available is implausible and no source proves a correct one;
- sources conflict and none can be treated as authoritative.
A legacy value can remain visible when the page clearly labels it unverified; it does not enter source-qualified rankings or claim schema. Unknown is an honest answer, and RTP Ledger never fills a gap with an estimate.
Dead links and archiving
Source pages move and disappear. When a source link dies, the value retains its previous check record. RTP Ledger does not present a dead link as a live citation. RTP Ledger does not currently maintain a public archive of every source document. When a value's source can no longer be confirmed, RTP Ledger treats it as legacy and flags it for re-verification. See the corrections policy for how re-checks are triggered.
Maintained by the RTP Ledger Data Team — Maintains the game database, validation rules and source records. Published · Last materially updated . Spot something wrong? Report a data issue.