> For the complete documentation index, see [llms.txt](https://docs.zkshine.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zkshine.xyz/overview/core-philosophy.md).

# Core Philosophy

### **Core Philosophy**

zkShine is guided by four foundational principles that shape every design decision and technology layer:

#### 1️⃣ **Zero Trust Architecture**

No component, node, or endpoint is inherently trusted.\
Every operation whether computation, message relay, or proof generation is verified cryptographically through **zero-knowledge proofs**, ensuring trustless and tamper-resistant execution.

#### 2️⃣ **Zero Exposure Infrastructure**

User identities, IP addresses, transaction origins, and data contents remain **completely hidden**.\
Even zkShine nodes and validators cannot view user data they only handle encrypted payloads validated through ZK proofs.

#### 3️⃣ **Full Sovereignty for Users**

Privacy is ownership.\
zkShine ensures that users maintain full control over how their data, identity, and activity are used, shared, or proven removing dependence on centralized privacy custodians.

#### 4️⃣ **Verifiable Privacy via ZK Proofs**

Every private action in zkShine whether a transaction, computation, or access request produces a **verifiable proof**.\
This means the network can **confirm correctness** without needing to see the underlying data, ensuring both **integrity and invisibility**.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.zkshine.xyz/overview/core-philosophy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
