> 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/protocol-architecture/39_balance_between_security_response_and_decentralization.md).

# 39 Security response और decentralization balance

CryptoStone का लक्ष्य No Admin Mint और No Central Server principles को अपनाना है। फिर भी early development और testnet phase में limited administrative functions की आवश्यकता हो सकती है।

उदाहरण:

| Phase              | Admin role                             |
| ------------------ | -------------------------------------- |
| Before launch      | testing, audit, parameter verification |
| During testnet     | bug response और emergency pause        |
| After finalization | core issuance authority removal        |

Emergency pause हो तो उसका उपयोग केवल security incident रोकने के लिए होना चाहिए, rarity या supply manipulation के लिए नहीं।

Core contracts को public source verification और audit review से गुजरना चाहिए। Probability table hash और finalization events भी publicly documented होने चाहिए।


---

# 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/protocol-architecture/39_balance_between_security_response_and_decentralization.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.