# Architectural Overview ## A Decentralized Ecosystem for Carbon Removal Carrot's architecture is designed to serve a decentralized ecosystem of stakeholders involved in the carbon removal process. The key stakeholders in this ecosystem are: 1. **CDR credit buyers:** Organizations or individuals who aim to compensate for their emissions or to contribute to restoring the planet’s climate buy and retire Carrots to prove their commitment. For corporate buyers, a single smart contract handling all types of CDR solutions simplifies tracking credit portfolios. 2. **Tracer Community:** This community consists of Tracer token holders who govern the Carrot ecosystem through a DAO. They vote on key issues such as selecting endorsers, upgrading smart contracts, and revoking projects or endorsers that violate the rules of the ecosystem. 3. **Endorsers:** Endorsers are organizations, such as certification authorities or registries, that are recognized by the DAO as legitimate to select and endorse carbon dioxide removal projects. They play a crucial role in curating and tracking projects, ensuring their ongoing quality and compliance with the Carrot standards. 4. **Projects:** Projects are the entities that implement carbon removal solutions. They can range from nature-based solutions like reforestation and afforestation to industrial solutions like direct air capture and enhanced weathering. Projects are responsible for minting Carrot tokens, which represent the amount of carbon dioxide they have removed from the atmosphere. Financial service providers: CDR marketplaces, traders, and ETFs who thrive on a healthy and growing CDR market. --- # Agent Instructions: 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: ``` GET https://docs.endglobalwarming.net/overview/architectural-overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.