> For the complete documentation index, see [llms.txt](https://quantixfinance.gitbook.io/quantixfinance-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://quantixfinance.gitbook.io/quantixfinance-docs/platform-architecture/data-integrity.md).

# Data Integrity

Because the system spans on-chain and off-chain records, the integrity question is not only whether the ledger is correct, but whether the two records agree with each other. Quantix treats on-chain state as authoritative for anything that determines a lender's claim — balances, deployed capital, repayments — and off-chain records as authoritative for identity and legal obligation. The two are bound together rather than duplicated: a loan recorded on-chain references its agreement off-chain, and the eligibility that gates a wallet reflects the identity check performed behind it.

Every executed Master Loan Agreement is hashed, and that hash is anchored on-chain at execution. This allows a lender or auditor to independently confirm that a specific, executed agreement has not been altered since signing — without the document's contents ever being exposed on a public ledger — by comparing the off-chain file against its on-chain hash rather than relying on Quantix's own representation that the document is authentic.

The published metric set is part of data integrity as well. Because utilization, coverage, default rate, and the other core metrics are defined precisely, and because their inputs are on-chain, a third party can recompute them independently and arrive at the same answer. Metrics that can be reproduced are harder to misrepresent than metrics that must be taken on faith — and the same is now true of the legal documents underlying them, not just the numbers describing them.