# Audits ![](https://3472993914-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MZnGVeFxEK1AnDgb1Nq%2F-MlI359ScYaF-8GsGikI%2F-MlI8VkThA6GDR-hL-fg%2Fimage.png?alt=media\&token=1ba8a812-00df-4f9a-aa55-5f712ec83d78) We have completed a full audit of our AMM and Masterchef contracts from [**Paladin Blockchain Security.**](https://paladinsec.co/) The full audit report is provided below or may be viewed [here](https://github.com/glide-finance/audits/blob/master/Paladin_Glide_Finance_Final_Report.pdf). All identified issues have been acknowledged or resolved. {% file src="" %} Paladin Audit {% endfile %} One point of clarification resulting from this audit. * Since the Glide token has a 10-year distribution, we wanted to prepare for the **likely situation that we'll want to upgrade our staking contract to a more modern iteration at some point in the future**. The way most Sushiswap-based protocols work is the Masterchef contract is made the owner of the rewards token contract and this cannot be changed. This has some advantages in terms of investor confidence, but disadvantages in that improvements cannot be made after launch. Thus, we have decided to include a function on our Masterchef contract that allows us to transfer ownership of the Glide token. The DeFi space moves quickly, and **we want to ensure Glide can remain adaptive to evolving standards.** Therefore, our **Masterchef contract will be placed behind a 7-day timelock to ensure users have ample time to react should the Glide token ownership be transferred**, maliciously or not. ## Liquid Staking The results from the audit completed for the stELA liquid staking protocol can be viewed [here.](https://paladinsec.co/projects/glide-finance/) --- # 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.glidefinance.io/security/audit.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.