At Dynamic, security is foundational to everything we do. We believe in transparency and collaboration with our developer community to ensure robust protection for both developers and users. Both of which are fundamental when building secure systems and addressing potential threats head on. Our approach is guided by the following principles:

  • Proactive security: We conduct regular top-tier audits, continuous testing, and operate a bug bounty program to identify and remediate potential vulnerabilities before they can be exploited.

  • Active monitoring and defensive measures: We have real-time monitoring and automated response mechanisms that allow us to swiftly mitigate emerging threats and suspicious activities.

  • Multi-layered security: We implement multiple layers of security, including Trusted Execution Environments (TEEs), Threshold Signature Scheme Multi-Party Computation (TSS-MPC), encryption, authentication safeguards, and strict code-review and state management policies. These measures are designed to provide comprehensive protection of wallets or software created by Dynamic.

  • SOC 2 compliance: As a SOC 2 Type II compliant organization, we affirm the effectiveness of our security processes and controls. This certification underscores our commitment to maintaining the highest standards of security and trustworthiness.

  • Disaster recovery and mitigation strategies: We conduct regular disaster scenarios and readiness to assist developers in protecting applications and wallets. If there are disruptions or issues, we are here and with you.

  • Trust, transparency and collaboration: Threats and attacks in web3 are a common occurrence. By prioritizing transparency and collaboration with our Developer community, we ensure that security remains a shared responsibility, reinforcing trust and resilience in our offering.

Important note: Dynamic will never request login codes, secrets, or any information that could be used for impersonation. If you receive requests, it is likely a scam, and should be reported.

Was this page helpful?