> For the complete documentation index, see [llms.txt](https://doc.cryptostone.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.cryptostone.org/crypto-stone/crypto-stone-wp-in/undefined/04_protocol_trust_principles.md).

# 04 प्रोटोकॉल विश्वास सिद्धांत

CryptoStone का trust model किसी central issuer की घोषणा पर नहीं, बल्कि public rules और verifiable records पर आधारित होना चाहिए।

प्रमुख सिद्धांत:

| Principle             | Meaning                                                                       |
| --------------------- | ----------------------------------------------------------------------------- |
| Public Rules          | mining, claim, rarity और supply rules publicly documented होने चाहिए          |
| On-chain Records      | ownership, tokenId और key protocol actions blockchain पर verify होने चाहिए    |
| Limited Supply        | प्रत्येक stone type की maximum supply तय और सार्वजनिक होनी चाहिए              |
| No Arbitrary Mint     | operator को मनमाने तरीके से Gem NFT mint करने की शक्ति नहीं होनी चाहिए        |
| Metadata Transparency | NFT metadata wallets और marketplaces के लिए readable और consistent होना चाहिए |

Decentralization केवल blockchain पर deploy करने से पूरी नहीं होती। यह तब मजबूत होती है जब operator core supply, rarity और issuance rules को मनमाने तरीके से बदल नहीं सकता।


---

# 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://doc.cryptostone.org/crypto-stone/crypto-stone-wp-in/undefined/04_protocol_trust_principles.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.