# 10. Verification, Audits, and Transparency

[Back to whitepaper overview](/lsteak-protocol-docs/lsteak-whitepaper-v2.2/overview.md)

LSteak is designed to be verifiable by construction.

The system emphasizes explicit rules, observable state, and constrained authority.

### 10.1 Audits and Code Review

All core LSteak and LSaaS smart contracts are subject to independent third-party audits prior to launch.

Audit reports are made publicly available in full.

### 10.2 On-Chain Verifiability

All critical system state is observable on-chain.

This includes:

* Backing composition and total value
* Effective supply calculations
* Backing Per Token (BPT)
* Redemption Ratios (RR)
* Treasury inflows and allocations
* Protocol-Owned Liquidity (POL)
* LSaaS Queue (`Q`) and xl-backing (`B`) balances, plus resolution flows
* Emergency pause events and durations

### 10.3 Separation of Metrics and Marketing

LSteak separates accounting metrics from surface-level UX.

Nothing is hidden.

Not everything is promoted.

### 10.4 Governance Transparency

All governance actions are on-chain.

They are timelocked and bound by predefined parameter ranges.

### 10.5 Disclosure Philosophy

Material disclosure.

Signal over noise.

### 10.6 Trust Model Summary

Don’t trust:

* market timing
* governance discretion
* future inflows

Verify:

* fixed invariants
* bounded controls
* deterministic routing
* observable accounting
* explicit failure modes


---

# Agent Instructions: 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:

```
GET https://lsteak-protocol.gitbook.io/lsteak-protocol-docs/lsteak-whitepaper-v2.2/10.-verification-audits-and-transparency.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.