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
  • Key network design elements
  • 1. Network-Level Guardrails
  • 2. Network Guardians
  • 3. Secure Bridging onto Haven1
  • 4. Best-in-Class Liquidity
  • 5. Core Protocols
  1. Foundations of Haven1

Architecture & network design

Explore Haven1's architecture and network design, featuring Proof of Authority consensus, advanced permissioning, and robust security measures to create a scalable and secure blockchain ecosystem.

Haven1 is an EVM-compatible blockchain that extends GoQuorum, originally developed by JP Morgan and open-sourced by Consensys. This architecture leverages Haven1's Proof of Identity Framework and Network-level Guardrails, providing a secure and reliable blockchain solution. The tailored design enhances permissioning and security measures, positioning Haven1 as a robust solution for on-chain finance and enterprise applications.

Client

Haven1 utilizes GoQuorum, a fork of Geth tailored for permissioned blockchain environments. GoQuorum introduces advanced permissioning, essential for managing security and user verification within Haven1โ€™s ecosystem. These features enable precise control over user access, roles, and permissions, meeting the rigorous demands of traditional finance systems.

Consensus Mechanism

Haven1 employs a Proof of Authority (PoA) consensus mechanism using Istanbul Byzantine Fault Tolerance (IBFT). This consensus model enables trusted validators to establish consensus and validate transactions. By choosing IBFT over Proof of Work (PoW), Haven1 provides a more efficient, scalable solution for permissioned networks, ideal for enterprise blockchain applications.

Nodes

Validators in Haven1 play a critical role in maintaining the networkโ€™s integrity. They process transactions, participate in the IBFT consensus mechanism, and execute smart contracts, ensuring the network remains secure and reliable.

Data Flow

Haven1 exclusively uses the public transaction layer of GoQuorumโ€™s architecture. Transactions are disseminated across all nodes following Ethereumโ€™s standard data flow protocol, ensuring a consistent and universal state across the network.

Network Manager

The Network Manager controls access to the Haven1 blockchain and enables the creation of a permissioned network, ensuring that only verified participants can interact with the ecosystem.

Security and Permissioning

Haven1 enhances GoQuorumโ€™s permissioning features by integrating network-level guardrails. This ensures that access to the network is strictly controlled and that sensitive data and transactions are managed with the utmost security. These permissioning measures meet the stringent security requirements of traditional financial institutions.


Key network design elements

Haven1โ€™s architecture incorporates security baked into the protocol, ensuring users are protected at every layer without imposing unnecessary restrictions. Every contract deployed on Haven1 must go through a whitelisting and approval process, involving governance participation and risk assessments by the Haven1 team. This stringent process guarantees that deployed contracts adhere to the highest industry standards, offering a secure environment for both developers and users.

At the core of Haven1's guardrails is the hPassport, a robust identity verification framework. Every user must complete KYC/AML verification before they can engage in on-chain activities. This ensures that all participants are verified, minimizing counterparty risk, preventing fraudulent activities, and streamlining dispute resolution. Despite this stringent identity check, Haven1 maintains privacy by storing minimal data on-chain, preserving the user's personal information while enhancing security.


The Network Guardians program acts as a proactive firewall, preventing malicious transactions from reaching the networkโ€™s RPC. By partnering with leading Web3 security firms, Haven1 leverages real-time smart contract monitoring, two-factor authentication (2FA), and customizable transaction policies to safeguard users.

This approach offers multiple layers of defense:

  • Smart contract monitoring actively detects vulnerabilities and potential exploits in real time.

  • 2FA provides users with additional security for their assets, ensuring that even if their private keys are compromised, unauthorized transactions can be blocked.

  • Customizable transaction policies allow users to set rules on IP, time limits, and transaction size, providing further protection against unauthorized activities.

As Haven1 continues to evolve, the Network Guardians program will expand, bringing additional security layers to meet the growing threats within the blockchain ecosystem.


Haven1โ€™s Asset Bridge and Storage System ensures secure and transparent transfers of digital assets between Haven1 and other blockchains. Key elements of this system include cryptographic attestation and 1:1 verifiable asset backing, where tokens bridged onto Haven1 are fully backed by assets held in secure Fireblocks vaults. This provides users with complete transparency and access to proof of reserves.

Additional bridge security measures include:

  • Distributed keys managed by seven globally recognized validators from both Web2 and Web3, exceeding the security of typical multi-signature setups.

  • Rate limits and time delays on withdrawals, ensuring that transactions are processed in an orderly and safe manner.

  • Bridge audits conducted before mainnet launch to further strengthen community trust.

The bridge facilitates seamless deposits and withdrawals: tokens deposited into the Fireblocks vault are mirrored as minted tokens on Haven1, while withdrawals involve burning these tokens and transferring the assets back to the userโ€™s destination network.


Haven1 addresses one of the critical challenges in DeFi: liquidity fragmentation. By consolidating liquidity across its ecosystem, Haven1 ensures that market participants benefit from seamless trading and maximized arbitrage opportunities. This enhances overall market efficiency and provides a smoother experience for users.

By concentrating liquidity into its core protocols, Haven1 allows traders to interact with deep pools of capital, optimizing slippage and making cross-application arbitrage much more efficient than on fragmented ecosystems. This ensures better execution for traders and enhances the value of the H1 token by driving more activity and demand within the ecosystem.


At the heart of Haven1โ€™s ecosystem are its six core protocols, which form the foundation for a more integrated on-chain infrastructure. These protocols, including Automated Market Makers (AMMs), Lending & Borrowing, and Derivatives platforms, are directly owned and governed by Haven1.

This unique ownership structure eliminates the need for fragmented liquidity across multiple external protocols, instead consolidating it into a single ecosystem. As a result, Haven1โ€™s core protocols generate direct value for sustainable, ongoing ecosystem participation incentives through fees, revenues, and governance rights. This integrated approach not only ensures liquidity but also strengthens the utility and value of the H1 token, making it central to the networkโ€™s success.

PreviousH1 TokenomicsNextNetwork-level security

Last updated 1 month ago

1.

2.

3.

4.

5.

๐Ÿ“
Network-Level Guardrails
Network Guardians
Secure Bridging onto Haven1
Best-in-Class Liquidity
Core Protocols