Minterest FAQ
  • Minterest Protocol
  • Ethereum Network
  • Mantle Network
    • Setting up a Mantle Wallet
    • Withdrawing Tokens from Centralised Exchanges to Mantle
    • Bridging assets to Mantle
    • Bridging Minterest NFTs
    • Current collateral factors
    • Squid Router
    • Exploring the Mantle Ecosystem
    • Changing networks to Mantle
    • Using Minterest on Mantle
    • Troubleshooting and support
    • Community FAQ
  • Taiko Network
    • Set up a Taiko Wallet
    • Change networks to Taiko in the Minterest App
    • Bridge assets to Taiko from Ethereum
    • Use Minterest on Taiko
    • Community FAQ
    • Troubleshooting and Support
  • Morph Network - adaptiFi
    • Set up a Morph Wallet
    • Change networks to Morph (adaptiFi) in the Minterest App
    • Bridge ETH to Morph (Official Bridge)
    • Use adaptiFi
  • Updated Tokenomics (April 2024)
    • CAE Stack or Skip Campaign FAQ
  • Supplying
  • Borrowing
  • Minterest NFTs
  • Minterest MINTY
  • Emissions
  • Cooldown Engine: $MINTY staking and emission rewards
  • Staking
  • Minterest Leaderboard Points System
    • How to Earn Mints
    • Leaderboard Mechanics
    • Additional Incentives
    • How to Check Your Mints
    • Frequently Asked Questions
    • Troubleshooting
  • Buyback Engine
  • Withdraw & Repay
  • Risks Involved
  • Security Audits
    • Audited Token Markets
    • Minterest Security Incident Documentation
  • Minterest: Code Development Policy
  • 🆘Troubleshoot
  • COMMUNITY ASKS
    • Business
    • Roadmap
    • Strategy
    • Support
  • Technical documentation
    • Overview
  • Contracts overview
  • Contracts addresses for verification on Ethereum
  • Contracts addresses for verification on Mantle
  • Contracts addresses for verification on Taiko
  • Guides
    • Lending and borrowing using Ethers.js
    • Staking and accruing rewards using Ethers.js
  • Technical paper
Powered by GitBook
On this page

Minterest: Code Development Policy

PreviousMinterest Security Incident DocumentationNextTroubleshoot

Last updated 10 months ago

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