> For the complete documentation index, see [llms.txt](https://docs.maple.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maple.finance/technical-resources/syrup/modules.md). # Modules ### Exposing Mints and Burns The `mint` and `burn` functions of the SYRUP contract need to be exposed only to authorized actors. While the ERC20 contract does not distinguish between different types of actors, SYRUP prefers using minting modules to enforce strict rules. The mint function in the base token will be kept simple and only include authorization checks. The control over the total supply or availability of tokens will reside with the authorized actors. ### Modules Modules are smart contracts with pre-defined rules that can mint or burn MPL tokens. Authorized modules have a significant impact on the token and the protocol and should aim for simplicity to avoid unintended consequences. The onboarding and offboarding of modules will be performed off-chain. The SYRUP contract will store a single authorized address that can add or remove modules. This entity, such as the `GovernorTimelock` (managed by a multisig) or another account, is assumed to act according to off-chain governance decisions. The token itself will not impose any restrictions or checks on the actions of allowing modules. To activate the module, the following actions needed to be taken: ``` 1. An off-chain proposal for adding the module was made. 2. If the proposal was passed, the allowed entity scheduled an execution in the Globals contract. 3. After the time lock period passed, the module could be added as an authorized minter. 4. According the the specific module rules, tokens can be minted or burned. ``` --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.maple.finance/technical-resources/syrup/modules.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.