> For the complete documentation index, see [llms.txt](https://docs.tren.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tren.finance/protocol/asset-risk/centralisation-risk.md). # Centralisation Risk As mentioned in the [Security Risk](/protocol/asset-risk/security-risk.md) section, the technical security risk review encompasses a large portion of the centralisation risk process. This is because the smart contract of an asset can be assessed based on centralisation factors such as whether the contract is multi-sig, whether the contract is upgradeable vs immutable, whether the contract is permissionless, and if there are any built-in functions like minting in the contract. A more qualitative approach is also used to assess the governance structure of an asset. Block explorers and bubble maps will be used to determine the percentage of the supply the top holders of the token control. In general, the more decentralised an asset is, the better. Governance rules and functionalities of the protocol governing an asset will also be analysed to account for centralisation risk. --- # 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.tren.finance/protocol/asset-risk/centralisation-risk.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.