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
  • BridgeGovernance Setting Authorization
  • OrbitHub
  • Minter ( Ethereum / Klaytn / Icon )
  • Vault ( Ethereum / Klaytn / Icon )

Was this helpful?

  1. How it works

Governance

  • Orbit Bridge defines Governance on each chain on the basis of their respective vault.

  • The Origin Chain's vault is created with a Multi-Sig wallet, so if there is no governance concensus, no assets can be moved.

  • Governance has mint/burn/execute permissions on the Destination chain

  • A pair of what destination chain to bridge must be registered.

  • Depend on specification of each chain governance have different consensus in same governance.

BridgeGovernance Setting Authorization

OrbitHub

  • function addBridgeInfo

    • Function to save data such as Multi-Sig Wallet, Nonce, Sequence, etc. to be used and managed in Bridge Contract

    • The function must be executed using the Multi-Sig Wallet registered in Orbit Hub.

    • Params

      • string memory chain : Chain Symbol of Bridge Contract (ex, ETH, KLAYTN, TERRA)

      • address mig : Multi-Sig Wallet Contract Address to be used in Bridge Contract

      • uint[] memory uints : Uint Data Array to be managed in the Bridge Contract

      • bytes32[] memory bytes32s : Bytes32 Data Array to be managed in the Bridge Contract

      • bytes memory comment : Bytes Data to be managed in the Bridge Contract

  • function removeBridgeInfo

    • Function to delete data used and managed in Bridge Contract

    • The function must be executed using the Multi-Sig Wallet registered in Orbit Hub.

    • Params

      • string memory chain : Chain Symbol of Bridge Contract (ex, ETH, KLAYTN, TERRA)

  • function changeHubMig

    • Function to replace the Multi-Sig Wallet registered in Orbit Hub Contract

    • The function must be executed using the Multi-Sig Wallet registered in Orbit Hub.

    • Params

      • address mig : Multi-Sig Wallet Contract Address

  • function changeBridgeMig

    • Function to replace the Multi-Sig Wallet registered in Bridge Contract

    • The function must be executed using the Multi-Sig Wallet registered in Orbit Hub.

    • Params

      • string memory chain : Chain Symbol of Bridge Contract (ex, ETH, KLAYTN, TERRA)

      • address mig : Multi-Sig Wallet Contract Address

Minter ( Ethereum / Klaytn / Icon )

  • function changeActivate

    • Functions to control Minter functions to respond to problems

    • The function must be executed by the governance of Minter.

    • Params

      • bool activate : Minter Status

  • function setValidChain

    • Function to make it possible to receive requests only through a bridging-capable chain

    • The function must be executed by the governance of Minter.

    • Params

      • string memory _chain : Chain Symbol ( ex, ETH, KLAYTN, TERRA )

  • function addToken

    • Function to add mapping about tokens to be minted when bridging is executed

    • The function must be executed by the governance of Minter.

    • Params

      • bytes memory token : Token Information to be requested bridging from Vault

      • address tokenAddress : Token Address to be minted by Bridging execution in Minter

  • function setBridgingFee

    • Function to set the fee amount for Bridging execution.

    • The function must be executed by the governance of Minter.

    • Params

      • uint _bridgingFee : Fee Amount for Bridging execution.

  • function setFeeGovernance

    • Function to set the feeGovernance.

    • The function must be executed by the governance of Minter.

    • Params

      • address _feeGovernance : Address of FeeGovernance.

Vault ( Ethereum / Klaytn / Icon )

  • function changeActivate

    • Functions to control Vault functions to respond to problems

    • The function must be executed through Vault's own SubmitTransaction/ ConfirmTransaction logic

    • Params

      • bool activate : Minter Status

  • function setValidChain

    • Function to make it possible to receive requests only through a bridging-capable chain

    • The function must be executed through Vault's own SubmitTransaction/ ConfirmTransaction logic

    • Params

      • string memory _chain : Chain Symbol ( ex, ETH, KLAYTN, TERRA )

  • function setBridgingFee

    • Function to set the fee amount for Bridging execution.

    • The function must be executed through Vault's own SubmitTransaction/ ConfirmTransaction logic

    • Params

      • uint _bridgingFee : Fee Amount for Bridging execution.

  • function setFeeGovernance

    • Function to set the feeGovernance.

    • The function must be executed through Vault's own SubmitTransaction/ ConfirmTransaction logic

    • Params

      • address _feeGovernance : Address of FeeGovernance.

PreviousBridge OperatorNextBridging Transactions

Last updated 4 years ago

Was this helpful?