# 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/)


---

# 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.minterest.com/minterest-faq/minterest-code-development-policy.md?ask=<question>
```

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.