> For the complete documentation index, see [llms.txt](https://docs.usegimbal.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usegimbal.app/transparency/what-you-can-check.md). # What anyone can check The eight things an outsider can verify about Gimbal from public data alone, with the contract or service behind each one. Solvency is the first promise Gimbal makes. The second is that nobody has to take the first on trust. A stranger with public data can rebuild every figure on the platform, and contracts and open services guarantee that, not a policy document. Two places carry the promise. The Explorer, at /platform/explorer, is the public loan explorer, where every loan is on view. Telemetry covers the public risk page and the live readouts: the statistics, the concentration and the parameters in force. ## Eight commitments and what enforces them | # | Commitment | Enforced by | In practice | | - | --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 | A state change is always an event | `TermDesk`, `CollateralAuction`, `RolloverAuction` and `PolicyBoard` emit on every write; the indexer and the Explorer publish them | Origination, repayment, a rollover, an auction opening or settling, and a parameter change: each leaves an event, and each event is linked by the Explorer to its Blockscout transaction. | | 2 | The loan book is public | The loan and slice ledger in `TermDesk`, read by the indexer into the Explorer | For every live loan: collateral, LTV, rate and term, the size of the syndicate, health, and the origination oracle price. | | 3 | The risk figures are public | Telemetry, computed by the indexer from chain events | Protocol-wide LTV distribution, concentration per token and per issuer, a bad debt ledger that should read zero, and the realised price of each liquidation next to oracle. | | 4 | Oracles and reserves are visible | `PriceSentinel.quote()`, plus the issuer's proof-of-reserve feed | Per token: live Chainlink price, session, staleness, multiplier, pause flag; issuer reserves wherever a feed exists. | | 5 | Parameter changes are logged before they land | `PolicyBoard`: `OperationScheduled` carries the rationale hash, `ParamChanged` fires on execution | Every proposal and every execution is on the log, with its reasoning, ahead of taking effect. | | 6 | The code is open | Public repositories under a permissive licence; bytecode verified on Blockscout | The contracts, the relayer, the indexer and the keeper bots, with reproducible builds. | | 7 | Order flow is not hidden | Offers are EIP-712 messages over the `OfferBook` domain; the relayer exports the book | Run a relayer yourself and you see the identical set of offers, and the entire off-chain book is exportable. | | 8 | Nothing is held before a match | `TermDesk.originate` pulls funds via Permit2 or an earlier approval; `repay` and the return of escrow have no pause switch | Funds move only at origination. Repayment, and withdrawal after it, cannot be paused by anyone. | ## Two inputs, every number Chain events and signed offers. That is the whole input set, and a third party needs nothing else to recompute everything on the Explorer and on Telemetry. There is no privileged database behind either page. Were Gimbal Labs to vanish tomorrow, the open-source indexer pointed at the chain would produce the same pages again. ## What stays private Two things, and only two: * Whatever personal data sits behind an attestation. It remains with the KYC provider and never reaches the chain. * Which real-world identity stands behind a wallet. An address is displayed as an address and nothing else. All the rest of a loan is public, on purpose. ## The periodic risk report Beyond the live readouts, a periodic risk report is next on the transparency roadmap. It covers liquidations, outstanding exposure, how auctions performed against oracle, parameter changes and incidents, each tied to the on-chain evidence for it. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.usegimbal.app/transparency/what-you-can-check.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.