Orbit Bridge
  • Introduction
  • Overview
  • Core Concept
  • How it works
    • Features
    • Differentiation
    • Bridge Validator
    • Bridge Operator
    • Governance
  • Bridging Transactions
    • Ethereum
    • BNB Chain
    • Klaytn
    • Heco
    • Polygon
    • Celo
    • ICON
    • XRP
  • Validator Guide
    • Notes for Validator Nodes
    • Hardware Specifications
    • Validator Reward Structure
    • Quick Start
    • REST API
    • Configuration
    • Troubleshooting
  • Operator Guide
    • Hardware Specifications
    • Quick Start
    • REST API
    • Configuration
    • Troubleshooting
  • Official Bridge Governance
  • Token Registration for Bridging
    • Registration Using Etherscan
    • Registration Using Remix
    • Bridge to The Open Network(TON)
      • Registration on TON Using Etherscan
      • Registration on TON Using Remix
  • FAQ
    • General [EN]
    • General [KO]
    • Gas Fee Guide [EN]
    • Gas Fee Guide [KO]
    • Guide for Adding RPC Network [EN]
    • Guide for Adding RPC Network [KO]
    • Anti-Phishing [EN]
    • Anti-Phishing [KO]
    • Transaction delay after setting the gas fee
    • Integration Guide
      • 1. List of supported chains
      • 2. Contract Addresses
      • 3. How to use an Orbit Bridge
      • 4. Chain Explorers
      • 5. API
  • Contract
    • OrbitHub
    • Bridge
      • Ethereum
      • BNB Chain
      • Klaytn
      • Heco
      • Polygon
      • Celo
      • ICON
      • XRP
    • Vault (Layer 1)
      • Ethereum
      • BNB Chain
      • Klaytn
      • Heco
      • Polygon
      • Celo
      • XRP
    • Minter (Layer 2)
      • Ethereum
      • Avalanche
      • BNB Chain
      • Klaytn
      • Celo
      • Fantom
      • Harmony
      • Polygon
      • Moonriver
      • OKExChain
      • Orbit
      • Gnosis
      • ICON
      • XRP
    • BridgeReceiver
    • Governance
    • Glossary
  • LINK
    • Orbit Bridge Github
    • Orbit Bridge Website
  • POLICIES
    • Layer Fee
    • Bridge Fee
      • Current
      • History
        • Ethereum Layer1
        • BNB Layer 1
        • Ripple Layer 1
        • Klaytn Layer 1
    • Terms of Use [EN]
    • Terms of Use [KO]
  • Bridging Assets
    • Ethereum Layer 1
    • Ripple Layer 1
    • BNB Layer 1
  • CROSS CHAIN TIPS
    • ICON
    • Celo
    • HECO
    • XRP
Powered by GitBook
On this page
  • Operator
  • Validator
  • Vault
  • Minter

Was this helpful?

  1. How it works

Features

How Orbit Bridge works - Fully on-chain/decentralized alidation/Vaults/Minters

The Orbit Bridge system has Governance groups composed of the roles: Operator and Validator. Orbit Bridge uses Multi-sig based transaction consensus. Through this, the Operator, who sends data, and the Validator work together to efficiently and quickly process transactions. Additionally, as the consensus and validation processes are recorded on Orbit Chain, they are transparent and trustworthy.

Operator

Relays the information needed by Governance for actual operation. Each piece of data signed by the Validators is assembled and executed by forming a transaction that runs on the chain. Collect signatures of validators gathered in OrbitChain MIG (MultisigWallet) and generate a transaction of withdrawal from Vault or mint from Minter.

Validator

A group of Validators constituting Governance verify the TX generated by each chain and record verification in the chain to reach a consensus.

Vault

The place where assets are deposited into when a bridging transaction occurred on Native Chain(Origin Chain).

Minter

Receive a request to withdraw from a chain that oToken(a token bridged via Orbit Bridge) was minted, or mint an oToken to another chain from a chain where the token is originally issued on.

PreviousHow it worksNextDifferentiation

Last updated 2 years ago

Was this helpful?