> 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/protocol-architecture/38_protocol_finalization_principles.md). # 38 Protocol Fixed Principles For CryptoStone to aim for decentralized asset characteristics similar to Bitcoin, its core rules must not be arbitrarily changed after deployment. | Fixed Item | Description | | ----------------------------- | ------------------------------------------------ | | Total STONX supply | 1,200,000,000 STONX | | STONX circulation structure | Open Market Allocation | | Max Supply by STONX | Maximum NFT issuance quantity by each STONX | | Base Mining Interval by STONX | Basic mining interval | | Target Pool Power | Initial reference value of 40,000,000 Power | | Base Mining Unit | 1,000 STONX | | Weight probability table | Weight generation probability | | Color probability table | Color grade generation probability | | Clarity probability table | Clarity grade generation probability | | Cut probability table | Cut grade generation probability | | Scarcity Multiplier | Halving-based difficulty multiplier | | Claim Burn formula | Burn formula at claim | | Mining Power formula | Staking-based Mining Power formula | | PoM formula | Proof of Mining accumulation and claim condition | | Lock Multiplier | Mining multiplier by lock-up period | | Maturity Burn formula | Depreciation burn formula at lock-up maturity | Once initial settings are completed, the protocol should be finalized. After this, the operator must not be able to arbitrarily increase supply, change rarity probabilities, or manually issue NFTs to specific users. The core contracts of CryptoStone should have source code publicly verified after deployment, and token supply, NFT supply, probability tables, mining formulas, and PoM threshold calculation structures must not be changeable after finalization. If limited administrative functions are necessary before finalization, the list, purpose, removal timing, and control method of those functions must be clearly disclosed. After finalization, administrative authority related to core issuance quantity, probability tables, issuance rights, and PoM calculation method should be removed or disabled. Decentralization is not completed simply because something is deployed on a blockchain. Decentralization is formed through rules that the operator cannot change, code that anyone can verify, and structures in which anyone can participate. --- # 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/protocol-architecture/38_protocol_finalization_principles.md?ask=&goal= ``` `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.