> For the complete documentation index, see [llms.txt](https://docs.minterest.com/minterest-faq/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.minterest.com/minterest-faq/minterest-code-development-policy.md).

# Minterest: Code Development Policy

We are committed to transparency in our code development. Here’s a summary of our process:

• Planning: Features are designed with clear objectives and planned into 2-week sprints for incremental improvements.

• Coding Guidelines: Development follows Solidity best practices and OpenZeppelin’s standards.

• Coding Style: Consistent with the official Solidity Style Guide.

• Analysis Tools: Tools like Slither, Solhint, Hardhat, and Mocha are used to identify potential issues early.

• Simulations and Testing: Code is tested in real-world scenarios.

• Peer Review: Code is reviewed by peers familiar with Minterest’s architecture.

• Independent Peer Review: External experts now review code for unbiased security and best practices.

• Third-Party Audit: Code interacting with user assets undergoes thorough third-party audits before deployment.\
\
You can read more in this article: [Minterest: Code Development Policy](https://minterest.com/blog/minterest-code-development-policy/)