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
  • MetaMask
  • Remix IDE

Was this helpful?

  1. Token Registration for Bridging
  2. Bridge to The Open Network(TON)

Registration on TON Using Remix

Bridge KIP-7 (fungible token, original token on KLAYTN) to TON

PreviousRegistration on TON Using EtherscanNextGeneral [EN]

Last updated 2 years ago

Was this helpful?

This guide is based on the contract address and amount supplied. Take this guide as a reference and type in the exact numbers and address as told.

MetaMask

  • Networks

KLAYTN : https://public-node-api.klaytnapi.com/v1/cypress
  • Add Network from the networks dropdown if needed

  • Open Networks again and select the network you added

Remix IDE - an online IDE to develop smart contracts.

  • Download abi files

  • Load abi files into Remix IDE

  • Select ft.abi

  • Approve Token

    • Select Deploy & Run Transaction on left bar

    • Select Injected Web3 for Environment

      • For Metamask

      • Check chainID (ex. KLAYTN : 8217)

    • Put your token address and Load Contract (ex. KSP : 0xc6a2ad8cc6e4a7e08fc37cc5954be07d499e7654)

    • Put spender and the amount to be bridged

      • In this case KLAYTN Layer 1 contract : 0x9Abc3F6c11dBd83234D6E6b2c373Dfc1893F648D

      • If your original token is on a chain other than KLAYTN, please refer to the Layer 1 contract addresses

    • Click transact button

  • Send Transaction using Metamask

  • Bridge Token

    • Load the Layer 1 contract referring to the Approve Token step

    • KLAYTN Layer 1 contract : 0x9Abc3F6c11dBd83234D6E6b2c373Dfc1893F648D

    • Get ChainId for toChain (Use TON for TON due to predefined bridge rules)

    • Put chainId to check if toChain is a supported chain

    • Put chainId to check the bridge fee to toChain

      • If chainFee is zero, then value set 0

      • if not, you do not need to put chainFee in VALUE. (ether = 10^18 wei)

    • Dropdown depositToken, fill params and click transact

      • token : your token address (ex. KSP : 0xc6a2ad8cc6e4a7e08fc37cc5954be07d499e7654)

      • amount : 1 Basically, you are sending the minimum amount to register the token, 1/10^18 since the contract is based on the standard of decimal 18

    • Send Transaction referring to the Send Transaction using Metamask step

    • You can check the bridged token by searching for toAddr in toChain's explorer

toAddr : [Your TON based wallet address that want to receive your token] TON based wallet has different type as we generally use for KIP7. Please refer to the scripts' hashPart for switching your address to 32byte address

Remix IDE
Docs
https://github.com/jaybbbb/bridge-utils
801B
layer1.abi
Layer 1 means original token platforms (ex. KSP's Layer 1 => KLAYTN)
222B
ft.abi
ft means Fungible Token (ERC-20, KIP-7)
Updated dropdown menu Select [Injected Provider - MetaMask]
choose edit
edit gas fee
make sure priority fee and fee to 750
If the chainFee shows any gas fee, put the same amount in the GAS FEE value
When the transaction is completed, tochain's explorer shows the result as above