> For the complete documentation index, see [llms.txt](https://docs.cournot.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cournot.ai/architecture/privacy-and-confidential-truth.md).

# Privacy & Confidential Truth

While blockchain thrives on transparency, the real world runs on privacy. A prediction market for "Corporate Mergers" or "Supply Chain Delays" requires analyzing sensitive data that cannot be publicly exposed on-chain.

Cournot Protocol introduces a **"Confidential Truth"** paradigm, enabling the verification of facts without revealing the underlying raw data. This is achieved through the synergy of **zkTLS** and **TEEs**.

#### **Zero-Knowledge Inputs (zkTLS)** <a href="#zero-knowledge-inputs-zktls" id="zero-knowledge-inputs-zktls"></a>

* **The Challenge:** Traditional oracles require data to be public (e.g., a public API URL) to be verified. This makes it impossible to resolve markets based on private data, such as *"Did I receive a transaction confirmation email from PayPal?"* or *"Is my private bank balance above $1M?"*
* **The Cournot Solution:** Through **zkTLS**, the Collector Node acts as a blind notary.
  * The user generates a proof locally in their browser (Client-Side Proving).
  * The proof confirms: *"This data originated from `paypal.com` via a secure TLS session, and the field `amount` > 1000."*
  * **Privacy Guarantee:** The Collector Node verifies the *proof* of the email, but never sees the *content* of the email. No sensitive PII (Personally Identifiable Information) ever leaves the user's device.

#### **Eyes-Off Reasoning (TEE Confidential Computing)** <a href="#eyes-off-reasoning-tee-confidential-computing" id="eyes-off-reasoning-tee-confidential-computing"></a>

* **The Challenge:** Even if the input is private, sending it to an AI model usually means the model operator (or the node runner) can see it. This "Reasoning Leakage" is unacceptable for institutional use cases.
* **The Cournot Solution:** All Fast Path inference occurs within **Hardware Enclaves (TEEs like Intel TDX / NVIDIA H100 Confidential Computing)**.
  * **Memory Encryption:** The AI model's weights and the user's input data are encrypted in the RAM. Even the physical owner of the Anchor Node server cannot peep into the reasoning process.
  * **Remote Attestation:** The TEE generates a cryptographic quote proving: *"I am running the official, un-tampered Cournot Auditor code, and I processed this specific encrypted input."*
  * **Result:** We achieve **"Eyes-Off Reasoning";** the AI judges the case, but no human ever sees the evidence.

#### **Use Case: Private Prediction Markets (Dark Pools)** <a href="#use-case-private-prediction-markets-dark-pools" id="use-case-private-prediction-markets-dark-pools"></a>

This privacy architecture unlocks a new trillion-dollar market: **Enterprise Hedging**.

* *Scenario:* A shipping company wants to hedge against a delay in their specific cargo shipment.
* *Mechanism:* They open a prediction market on Cournot. The resolution relies on their private ERP data.
* *Privacy:* Cournot's TEE nodes ingest the private ERP API feed via zkTLS, verify the delay, and settle the market. **Competitors never see the shipping data; they only see the settlement result.**


---

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

```
GET https://docs.cournot.ai/architecture/privacy-and-confidential-truth.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.