> For the complete documentation index, see [llms.txt](https://docs.marinade.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.marinade.finance/marinade-protocol/security.md). # Security Security has always been a primary concern for Marinade. We are doing everything we can to set a high standard for security in our protocol and in the Solana ecosystem. ## Overview Marinade's security and availability commitment: ### On-chain contracts A list of Marinade's on-chain smart contracts is available here: {% hint style="info" %} The **referral program is paused** and there is currently no referral interface, so ordinary staking goes to Marinade's own programs. No partner fees are paid while it is paused, including under agreements signed before the pause. If the program relaunches and you stake through a referral link, the contract you interact with will be the referral program rather than Marinade's main smart contract. Either way, verify the program you are signing against the published address list above before you approve a transaction. {% endhint %} *** ### Risks When you participate in DeFi, you always expose yourself to risks. An investor's job is to mitigate these risks and stay informed on them to make the best possible decisions. Let's see what different types of risk exist when you use Marinade and how we worked to mitigate them. *** ### Technical risks #### Blockchain risks When you use Marinade.Finance, you use a protocol that relies on the Solana blockchain. If the Solana blockchain were to be attacked successfully, the funds on Marinade could be at risk. **Marinade's recipe**: Solana was chosen for many reasons, one of which was that it has high security. Solana has been audited by [Kudelski Security](https://solana.com/solana-security-audit-2019.pdf) and is a blockchain that has used Alpenglow consensus since October 2026. You can learn more about Solana through their [whitepaper](https://solana.com/solana-whitepaper.pdf). #### **Contract risks** In DeFi, any protocol can potentially be attacked by hackers. They will look for loopholes and bugs that allow them to abuse the protocol for their gain. **Marinade's recipe**: We emphasize security and have been conducting formal audits all along the way. We have successfully completed **6 audits and 1 code review**, the most recent by Neodyme in May 2026. We also run a **bug bounty** on Immunefi covering the liquid staking program (liquid-staking-program), with rewards of up to $250k for critical findings. Other Marinade programs are not part of the Immunefi scope; the Bug Bounty page below explains how to report issues in those. Click on the pages below to access them. ### Financial risks #### Trust risks As you may know, DeFi can be a brutal environment, and some actors have already abused the trust of people using their services. We did not want this to be a possibility with our protocol. **Marinade's recipe**: no single party can change Marinade on their own. Authority is split across four layers rather than held by one multisig: * The **mSOL liquid staking program** can only be upgraded by an **ecosystem multisig that requires 6 signatures out of 13**, where the majority of signers are founders and teams from other Solana projects. Marinade alone cannot reach the threshold. * **Everything else**, including Marinade Native, Marinade Select, Validator Bonds, Recipes, gauges and referrals, sits under **MNDE-locked DAO governance** on Realms. * Day-to-day operations sit with the **Marinade Council, 3 of 5**, within bounds the DAO sets. * Emergency **pause** authority sits with a separate **3-of-5 Emergency Pause Council**, which can pause but never upgrade. Click the page below for the full breakdown, including the on-chain addresses for each layer. #### Legal risks When you use Marinade, you take full responsibility for your actions. It is your duty as an investor to check the current regulations in your country of residence and to act accordingly. **Marinade's recipe**: All our legal content can be found on the page below. If you have any doubts, please get in touch with your financial authorities for confirmation. --- # 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.marinade.finance/marinade-protocol/security.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.