Haven1
  • Get started
    • 🧑‍🚀Welcome Havenauts!
    • 📄Haven1 Litepaper
    • 🧮H1 Tokenomics
  • Foundations of Haven1
    • 📐Architecture & network design
    • 🔐Network-level security
    • 📚Haven1 Core protocols
    • 💱Best in class liquidity
    • 👮Network Guardians: Firewall on Haven1
    • 🌉hBridge: Intro to Haven1 Bridge
  • Learn
    • 💵What does Haven1 solve?
    • 💡Haven1: Use Cases
    • 📚Understanding GoQuorum
    • 🔤Haven1 Blockchain basics
    • 🛂KYC policies on Haven1 blockchain
    • Security at Haven1
    • 🔓What is esH1?
    • ⚖️Dispute resolution mechanism
    • 🛣️Haven1 Roadmap
    • 🖥️Haven1 is EVM compatible
  • Products
    • 🔃hSwap - Spot DEX on Haven1
    • 📍hsETH on Haven1
    • Earn on Haven1
    • 🛡️2FA Wallet Shield
    • 🧊Haven1 block explorer
    • 🏛️Governance & veH1
    • 🆔hPassport - Key to Haven1
      • Advantages of having ID verification at a network level
      • Understanding the ID Verification Process
    • 💼Vesting esH1 - Converting esH1 to H1
    • 📍Staking H1 & esH1 - Earning rewards on your H1 holdings
      • Flexible Staking
      • Locked Staking
  • hPerpetuals - Perps DEX on Haven1
  • Haven1 Guides
    • 🔗Quick links
    • ✅Haven1 onboarding Guide
      • 🪪KYC Guide
      • Business KYC(KYB) Guide
    • Adding multiple wallets to a hPassport
    • 🌉Simple Bridging Guide on Haven1 network
    • 🏠Haven1 Portal - Your Gateway into Haven1
    • 🔑2FA Set up Guide
    • 🤑Haven1 Airdrop: Claim Process and Strategies
    • Claim Process Walkthrough on Team Finance
    • 📄Contract Addresses
  • Build
    • 📖Getting started
    • 🌐Haven1 Network information
    • 🍦Novel developer benefits on Haven1
    • 📑High level guide for secure deployment
    • ⚙️Detailed deployment Guide
    • 🧰Developer tools
      • 👛Haven1 Gnosis Safe wallet
      • 🛠️Haven1 SDK
        • 🔌@haven1/sdk-api-client
          • Class: Haven1SDK
          • Class: AuthModule
          • Class: SdkModule
        • ⛓️@haven1/blockchain-sdk
          • Contracts
        • 🧰@haven1/wagmi-sdk
          • Constant Module
            • Variable: haven1Devnet
            • Variable: haven1Testnet
            • Variable: H1
          • Contract Module
            • ProofOfIdentity
            • ProofOfIdentityV2
            • NativeAppFee
          • Utility Module
            • bigIntMax
            • formatBigint
            • bigintFromDecimals
          • Hook Module
            • useWatch
            • useBalance
            • useApproveERC20
            • useContractWrite
        • ⚛️@haven1/react-sdk
          • useHaven1SDK
          • useAuth
          • useIdentity
          • useNotifications
          • useOTP
          • useSignIn
        • 📜Use cases & Examples
          • Adding the Notification Component to Your React UI
          • Check Proof of Identity (POI) Status
      • Oracles on Haven1
      • Subgraph on Haven1
      • Haven1 block explorer
      • Web3 libraries and tools
    • Development frameworks
    • 🔐Using hPassport in Your dApps
      • Integrating hPassport into Your dApp
      • Implementing Identity Checks in Smart Contracts
        • Country codes
      • Sample Application - Country ID
      • Sample Application - Composable verification level
      • Sample Application - User type
      • Repository Information
    • ⛽Application fees
      • FeeContract.sol
      • Example FeeContract Interactions
      • Case Studies
    • 👷Builders grants program
  • Additional resources
    • 📚Haven1 terminology
  • Quick Links
    • Website
    • Twitter
    • Blog
    • Telegram
    • Customer Support
Powered by GitBook
On this page
  • Audit Requirements
  • hPassport obtained after Identity Verification
  • Specific Contract Requirements
  • Additional optional controls for users
  • Continuous Monitoring and Incident Detection by Network Guardians
  • Oracle Integration
  1. Foundations of Haven1

Network-level security

Haven1's network-level security measures are meticulously designed to mitigate risks like hacks, exploits, and malicious activities.

Audit Requirements

  1. Mandatory Audits: Every application or protocol launched on Haven1 must undergo a minimum of 2 comprehensive audits conducted by recognized and reputable audit partners. The Haven1 team is committed to facilitating connections between developer teams and our trusted audit partners.

  2. Objective of Audits: These mandatory audits are crucial to ensure that all applications are robust against vulnerabilities and conform to the highest industry standards. This rigorous auditing process significantly bolsters the security infrastructure of the Haven1 network.

For developers on the Haven1 platform, adhering to these protocols is crucial to ensure the integrity and safety of applications.

Statistical analysis reveals a compelling insight: Protocols in the blockchain space that have undergone at least 2 audits (in cases the bytecode remains identical for both audits) have a 99% lower probability of harboring undisclosed vulnerabilities. This underscores our commitment to ensuring the utmost security and reliability of protocols on Haven1.

hPassport obtained after Identity Verification

  • Haven1’s Passport plays a crucial role in ensuring network security by mandating strict identity verification for all on-chain transactions.

  • Security Enhancement: Mandatory identity verification for transactions significantly reduces fraudulent activities.

  • Dispute Resolution: This framework offers a reliable mechanism for resolving disputes, enhancing transparency and accountability.

  • Building Trust: Verified identities increase user confidence in the network, fostering a more secure blockchain environment.

Specific Contract Requirements

Haven1 imposes several contractual requirements for applications building on Haven1 to bolster network security:

  1. Role-Based Access Control (RBAC):

    • Purpose: RBAC is crucial for managing sensitive operations within smart contracts. It restricts critical functions like token minting and vote casting to authorized roles, thereby minimizing the risk of unauthorized access or manipulation.

    • Implementation: Developers must carefully assign roles and permissions, ensuring that only designated accounts have the authority to perform specific contract functions, enhancing the overall security and governance of the smart contract.

  2. Deployment Control:

    • Controlled Deployment: To safeguard the network from potentially harmful contracts, only accounts owned by the Haven1 Association are permitted to deploy contracts. This centralized control mechanism adds an additional layer of security against rogue or malicious smart contract deployments.

    • Quality Assurance: This approach also ensures that all deployed contracts adhere to Haven1's stringent security standards and have undergone necessary audits and reviews, maintaining a high level of trust and integrity within the network.

  3. Contract Pausability:

    • Emergency Response: The mandatory inclusion of a pausability feature in smart contracts allows for immediate response in emergencies. This feature can be crucial in halting operations in the event of detected vulnerabilities or attacks.

    • User Protection: Pausability serves as a protective measure, safeguarding users' assets and interests by promptly addressing unforeseen issues. It provides a mechanism for developers to rectify issues without jeopardizing the contract's integrity or user assets.

Additional optional controls for users

Haven1 introduces several optional controls which users can enable and take advantage of additional security guarantees

  1. 2FA: Haven1 is the first blockchain to have a 2FA integrated at network level. This prevents you from getting REKT in a scenario where you have lost your private keys

  2. Finer access controls: Users will also be able to turn on/off granular controls such as allowing access only from certain IPs and so. Anytime our RPC sees a transaction from an IP which is out of the selected IPs, the transaction is dropped

  3. Safe for Developers: Developers can take advantage of built in Haven1 Safe to be able to quorom based access controls on their treasury or their deployments

Continuous Monitoring and Incident Detection by Network Guardians

Haven1 places a strong emphasis on continuous monitoring and real-time detection of potential security threats. This proactive approach is crucial in identifying and mitigating risks promptly.

  1. Transaction Analysis: Monitoring all network transactions for signs of malicious activity like double-spending or high gas fees.

  2. Smart Contract Monitoring: Vigilant observation of smart contract interactions to identify vulnerabilities like reentrancy attacks.

  3. Price Manipulation Surveillance: Overseeing potential manipulation within DEXs or oracle services to maintain asset pricing integrity.

  4. Flash-Loan Attack Prevention: Detecting large-scale, rapid transactions to prevent market manipulation.

  5. Event and Call Trace Analysis: Analyzing smart contract-generated events and call traces to identify irregularities or malicious activities.

Oracle Integration

Mandatory Oracle Services: Haven1 mandates the integration of trusted oracle services such as Chainlink or Pyth in its applications.

Objective: This ensures data accuracy and overall network safety, essential for applications relying on external data feeds.

This approach is aimed at enhancing the overall security of the network and providing a reliable mechanism for dispute resolution.

PreviousArchitecture & network designNextHaven1 Core protocols

Last updated 9 months ago

🔐