> For the complete documentation index, see [llms.txt](https://docs.onta.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onta.network/basics/interactive-blocks/traceshield.md).
# TraceShield
TraceShield creates a transaction verification and privacy framework that records all network activity on-chain while protecting sensitive details through zero-knowledge cryptography. Every transaction generates a cryptographic proof validating compliance with network rules without exposing amounts, identities, or other confidential information.
This gives regulators and auditors cryptographically verifiable assurance about system integrity while maintaining user privacy. For businesses and institutions, the system enables confidential transaction verification that satisfies compliance requirements without exposing competitive information.
TraceShield represents a fundamental evolution beyond both the excessive transparency of traditional blockchains and the opacity of private financial networks, establishing a new standard for financial privacy with accountability.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.onta.network/basics/interactive-blocks/traceshield.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
