> For the complete documentation index, see [llms.txt](https://docs.bitcarbon.com/diamond-standard-carats-bitcarbon/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitcarbon.com/diamond-standard-carats-bitcarbon/carats/carats-details/the-carats-ratio.md). # The Carats Ratio The wireless NFC chip inside a Diamond Standard Coin or Bar is programmed with a BCC (Coin) token, or a BCB (Bar) token. At launch, a BCC token is convertible into 5,000 Carats, and a BCB token is convertible into 50,000 Carats. The conversion ratio of BCC:BCB is permanently fixed at 1:10, and conversion is free (see Carats Redemption). **Initial Diamond Standard Carats Ratios** 5,000 Diamond Standard Carats = 1 Diamond Standard Coin 50,000 Diamond Standard Carats = 1 Diamond Standard Bar To pay for physical custody and network operations, fees are generated by the Carats Smart Contract by creating additional Carats. Over time, the number of Carats per underlying Diamond Standard Coin or Bar increases slowly, which is reported as the Carats Ratio, initially 5,000:1. This deflation distributes the costs fairly across all users proportional to their current holdings, without reducing their token balance. For example, if there are 10,000 Coins and the Carats Ratio is 5000:1, there are 50 million Carats held by users. By increasing the Carats Ratio to 5001:1, 10,000 new Carats are created by the smart contract to cover the operating costs, especially physical custody of the Diamond Standard commodities. The custody and administration costs should decline over time, as these expenses diminish as a proportion of total assets. --- # 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.bitcarbon.com/diamond-standard-carats-bitcarbon/carats/carats-details/the-carats-ratio.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.