> For the complete documentation index, see [llms.txt](https://reports.immunefi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://reports.immunefi.com/alchemix-v3/56326-sc-insight-variable-could-be-immutable.md). # 56326 sc insight variable could be immutable **Submitted on Oct 14th 2025 at 16:18:58 UTC by @PotEater for** [**Audit Comp | Alchemix V3**](https://immunefi.com/audit-competition/alchemix-v3-audit-competition) * **Report ID:** #56326 * **Report Type:** Smart Contract * **Report severity:** Insight * **Target:** * **Impacts:** ## Description ## Brief/Intro In the `AlchemistV3Position.sol` contract, the declared variable `alchemist` could be immutable. This would significantly save on gas costs during contract initialization and also during contract interactions. ## Vulnerability Details The variable `alchemist` could be set as immutable. This would save on gas costs \~2,100 gas per call, this variable is used in the `onlyAlchemist` modifier. This modifier is used a lot in this contract. ```solidity address public alchemist; ``` Setting this variable to immutable would save gas costs because immutable variables cost less gas when interacted with, because they are not taken from the contract's storage. ## Impact Details This is a code optimization.. This will save \~2,100 gas per interaction with this variable. ## References ## Proof of Concept ## Proof of Concept Setting variable to immutable saves gas, because the contract will not have to read from the contract storage when interacting with this variable. This saves \~2,100 gas per call. --- # 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://reports.immunefi.com/alchemix-v3/56326-sc-insight-variable-could-be-immutable.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.