DueWall logoDueWall Labs

The debt calendar, daily data & capital flows for tokenized credit

Subscribe to the Digest

DueWall / Verification / Methodology

Verification methodology — claim-vs-observed

This page is the citable definition of how DueWall verifies issuer claims. Everything here is derived from code that runs daily; nothing on this page is aspirational.

1. What a claim is

A claim is a statement an issuer makes that a buyer would rely on: liquidity frequency, settlement, minimum investment, management fee, domicile, maturity dates. Claims enter the registry (log) only from human-verified sources — grade-A fund factsheets read and checked by a human, and official calendars (e.g. tokenized MAS bills) — and each claim carries its source_url, so "who said this" is never ambiguous.

2. Three verdict states — defined once

VerdictMeaning
consistentThe claim matches the observation we can make today, by the stated rule.
discrepantThe claim and the observation do not match. Published with both sides shown and evidence links; the issuer is welcome to dispute, and the dispute is published too.
untestableNo independent observation exists today. Published as a result, not hidden — the proportion of untestable checks is itself part of the product narrative.

3. Rules

RuleWhat it checksIndependence
R1 liquidity_vs_onchain_queueClaimed redemption liquidity vs the on-chain redemption queue / contract epochs actually observable. This rule found the first real discrepancy: an issuer's documents say monthly redemptions; the on-chain vault runs 14-day epochs.Independent — claim source and observation are different layers (documents vs chain)
R2 factsheet_selfsourceHuman-verified factsheet terms, re-checked daily for staleness and revocation. Honestly labeled selfsource: the claim and the evidence share the same verified source today, and no independent on-chain check exists for this claim type yet — the gap is visible on purpose, and closes as adapters land.Same-source (labeled)
R5 official_calendar_selfsourceOfficial calendar entries (tokenized MAS bills) checked for presence and correctness against the published official file.Official-document layer (grade B)
Known discrepanciesHand-verified mismatches found during issuer onboarding (documents vs contract), each carried with claim, observed state and evidence link.Human-verified

Rule set is versioned with the daily run; the engine output is verification.json — every verdict carries method, observed state and evidence_url.

4. Badges are earned, never bought

A fund wears Verified automatically while its grade-A terms hold and its checks stay consistent. Any discrepant finding or stale data removes the badge automatically — and the removal is public. There is no way to purchase, renew or appeal a badge into existence. Verification is paid for by the buy side; never by issuers.

5. Seniority is provable

DueWall has published claim-vs-observed verdicts since 2026-11-19. Every daily snapshot is hash-chained (each day binds the previous anchor) and committed to Bitcoin via OpenTimestamps — when someone asks "who was checking claims before it mattered?", the answer is verifiable, not marketing.

6. Scope and limits (stated plainly)

v1 covers claim types available in verified terms (liquidity, settlement, minimum investment, management fee, domicile) plus official-calendar maturities. Claim types without an independent observation yet are labeled as such. Coverage grows automatically: every fund entering the human-verification pipeline adds its claims to the registry and its checks to the daily run. This page is generated from the same code that runs daily — it cannot drift from practice.

Public log: /verify/log.html · Feed: verification_log.json · Verdicts: verification.json