> For the complete documentation index, see [llms.txt](https://deluthium.gitbook.io/tutorial/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://deluthium.gitbook.io/tutorial/core-technology/zk-merkle-tree-verification.md).

# ZK-Merkle Tree Verification

Deluthium employs a ZK-Merkle Tree verification mechanism that allows users to independently validate their execution outcomes.

* **Mechanism:** Execution proofs are published onchain immediately upon settlement. These proofs capture the full execution chain: the RL engine's inputs (market state), decisions (routing strategy), and outputs (execution results).
* **14-Day Challenge Window:** Users possess a 14-day audit window to cross-validate the process and challenge the fairness of the engine's execution decisions. This provides both compliance auditability (did the trade settle correctly?) and model auditability (did the RL engine act in the user's interest?).

This mechanism replaces trust-based execution with cryptographically verifiable execution. Users do not need to trust Deluthium's reporting. They can independently verify every aspect of the execution process.