> For the complete documentation index, see [llms.txt](https://docs.dexponent.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dexponent.com/sharpe-consensus/proof-of-returns.md).

# Checking performance records

Use transaction records and current position data to understand a DTF's reported results.

1. Confirm the DTF contract and network from the official app.
2. Match deposits, withdrawals and share changes to the relevant transactions.
3. Check the timestamp of the NAV or performance observation.
4. Account for external-venue positions and pending transfers for Perpetual DTFs.
5. Check whether reported returns include fees and funding.

[BaseScan](https://basescan.org/) can help inspect Base transactions. A Base transaction alone does not prove the full value of remote trading positions.

The beta does not promise an independent “proof of returns” consensus system, verifier certification or insurance for reported performance. Report discrepancies with the DTF address, observation time and transaction hashes.

See [troubleshooting](/troubleshooting.md).