Heima Docs
  • About Heima
    • Problem & Solution
    • Use Cases
    • FAQ Heima Network
  • Parachain
    • Get Started
      • Heima Network
        • Collator
        • Full Node
    • Pallets and Modules
      • Verifiable Credential Management Pallet (VCMP)
        • Parts of a VCMP
        • VCMP Extrinsic, Events, and Error Events
        • Assertion definitions and parameters
      • Identity Management Pallet (IMP)
        • Components of the IMP
        • IMP Extrinsic, Events and Error Events
      • Teebag Pallet
      • Token Bridge
        • Tokenomics revisit
        • Architecture model
        • Token Bridge Commission
      • TEE
        • Background
        • Architecture diagram
        • Core components
        • FAQ Trusted Execution Environment
      • Omni Account
    • Developer Documentation
      • Build parachain
      • Launch a local network
      • Run tests
    • Verifiable Credential Solidity Contract
      • How to create a new Verifiable Credential Solidity contract
      • How to add a new token to example TokenHoldingAmount VC contract
      • VC output example introduction
      • How to deploy contract
    • SDK Documentation
      • Linking an Identity
      • Requesting a Verifiable Credential
      • Validating Verifiable Credentials
      • Retrieving the Hash of any ID Graph
      • Getting the User id_graph
      • SDK Use Case Example
      • How to Run Setup and Run Parachain + Worker
    • How-to guides
      • Interact with parachain
      • Transfer HEI from Ethereum to parachain
      • Transfer HEI from parachain to Ethereum
      • Participate in Heima Governance
  • Featured DApps
    • IdentityHub
      • Product Features
        • Direct Invocation
        • EVM Sign-In
        • Identity Score
        • Verifiable Credentials (VCs)
          • VC Summary
            • Assertion - TokenHoldingAmount
            • Assertion - NftHolder
            • Assertion - PlatformUser
            • Assertion - Achainable
            • Assertion - OneBlock
            • Assertion - BnbDigitDomainClub
            • Assertion - VIP3MembershipCard
        • IdentityHub Client
        • Securing Privacy
      • User Guide
        • Getting Started with the IDHub
        • Set up a Shielding Key
        • Link Identity
          • Link Web3 Account
          • Link Web2 Account
        • BRC 20 Sign-in
        • Generating Credentials
        • How to Stake, Bridge, and Unstake on IdentityHub
      • FAQ IdentityHub
      • Rules of IDHub v0.8
  • The Foundation
    • HEI Tokenomics
    • Ecosystem Wallet
    • Team Wallet
    • Foundation Wallet
  • Misc
    • Glossary of Terms
    • Related Links
Powered by GitBook
On this page

Was this helpful?

  1. Parachain
  2. Developer Documentation

Launch a local network

How to get our parachain running on localhost

PreviousBuild parachainNextRun tests

Last updated 2 months ago

Was this helpful?

A minimum local dev network consists of 2 relay chain nodes and 1 parachain node. To launch it (taking heima as an example, paseo is similar):

  1. make sure docker and yarn are installed

  2. git clone https://github.com/litentry/heima

  3. cd heima

  4. make launch-network-heima

litentry/heima images will be pulled automatically. Besides, zombienet, polkadot, polkadot-prepare-worker, and polkadot-execute-worker will be downloaded automatically and launched.

Wait a while until you see such logs:

Up to this point the network is launched successfully. You should be able to connect to the chain websocket via browser:

  • https://polkadot.js.org/apps/?rpc=ws://127.0.0.1:9944#/explorer for parachain

When finished with the dev network, run make clean-network to stop the docker containers and tidy things up