High level guide for secure deployment
Best practices for deploying secure and robust smart contracts on Haven1.
Haven1 aims to be the most secure blockchain in the industry. Our mission is to provide a platform where third-party protocols can thrive in a secure, efficient, and trustworthy environment.
This guide outlines the essential requirements and best practices for developers seeking to deploy their protocols on the Haven1 network. Adherence to these standards is crucial for maintaining the network's integrity and delivering a superior user experience.
1. Specific Contract Requirements
Haven1 imposes several contractual requirements to bolster network security:
Integration with Haven1 Fee Library:
Mandatory integration with the Haven1 Fee Library standardizes fee handling, enhancing transparency and consistency for users.
This integration reduces the complexity of the development process by abstracting the intricacies of fee management.
Contract Pausability:
Smart contracts must include a pausability feature to address emergencies effectively.
This feature ensures the safeguarding of user assets and allows developers to rectify issues without compromising the contract's integrity.
Role-Based Access Control (RBAC):
RBAC is essential for secure management within smart contracts, limiting critical functions like token minting and vote casting to authorized entities.
Developers must implement precise role assignments and permissions, ensuring only authorized accounts can execute specific contract functions.
Deployment Control to Haven1 Association:
To safeguard the integrity of the Haven1 network against potentially adverse contracts, deployment privileges are is reserved by the Haven1 Association. Development teams are required to provide access to their code for review, facilitating secure and accurate deployment onto the network. While GitHub is commonly utilized for this purpose, alternative methods of code sharing are also acceptable.
This measure guarantees that all contracts meet Haven1’s strict security criteria for quality assurance and have passed necessary audits and reviews.
It is imperative to emphasize that developers retain ownership and attribution for their code, with the Haven1 Association solely ensuring compliance with network standards.
2. Audit Requirements
Protocols intending to launch on Haven1 must have two comprehensive security audits from our reputable audit partners. The Haven1 team is dedicated to assisting developers in establishing connections with these trusted auditors in the Web3 space.
The purpose of these compulsory audits is to ascertain the resilience of applications against vulnerabilities, ensuring compliance with the highest industry standards. This thorough auditing not only reinforces the security of the Haven1 network but also instills confidence in the applications deployed.
3. Developer ID Verification
To bolster the security and integrity of the Haven1 network, developers must undergo comprehensive KYC/KYB procedures.
This verification process ensures that all developers are thoroughly vetted and adhere to regulatory standards, thereby fostering a trusted and transparent ecosystem within the Haven1 network.
Haven1 is committed to fostering a secure and innovative blockchain ecosystem. By adhering to the guidelines and requirements outlined in this document, developers can contribute to this vision, ensuring their protocols integrate seamlessly with Haven1’s infrastructure. We look forward to seeing your contributions to the Haven1 network and are here to support you through every step of the deployment process. Together, we can build a safer and more reliable blockchain future.
Last updated