# Registration Using Remix

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

```json
KLAYTN : https://public-node-api.klaytnapi.com/v1/cypress
```

* Add Network from the networks dropdown if needed

<img src="/files/Wz6rUUZM2K5BQWKp0ZUR" alt="" data-size="original">

* Open Networks again and select the network you added

## [Remix IDE](https://remix.ethereum.org/)

Remix IDE - an online IDE to develop smart contracts.

* [Docs](https://remix-ide.readthedocs.io/en/latest/index.html)
* Download abi files

{% file src="/files/it2a0uWRVnd4e9C9aIds" %}
Layer 1 means original token platforms (ex. KSP's Layer 1 => KLAYTN)
{% endfile %}

{% file src="/files/sNjbwWMnzxjHOF2Z4Q4D" %}
ft means Fungible Token (ERC-20, KIP-7)
{% endfile %}

* Load abi files into Remix IDE

<img src="/files/aWmBw12BR8HfkEBqSC07" alt="" data-size="original">

* Select ft.abi

<img src="/files/RzSzuTGnYnFJHBt2ZdEo" alt="" data-size="original">

* Approve Token
  * Select Deploy & Run Transaction on left bar
  * Select Injected Web3 for Environment&#x20;
    * 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&#x20;
    * 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](/bridgedocs/token-registration-for-bridging/reference-layer-1-contracts.md)
  * Click transact button

![](/files/VERNwaibgf3FPXlQZAVX)

* Send Transaction using Metamask

![choose edit](/files/xFYXj8mlC9zTGPPBJ88N) ![edit gas fee](/files/WtJzcZX6i7WECJSdQGE4) ![make sure priority fee and fee to 750](/files/f4UyItKLP1RH9IcyXf2r)

* Bridge Token
  * Load the Layer 1 contract referring to the Approve Token step
  * KLAYTN Layer 1 contract : 0x9Abc3F6c11dBd83234D6E6b2c373Dfc1893F648D
  * Get ChainId for toChain (Use MATIC for POLYGON 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 must put chainFee in VALUE. (ether = 10 \*\* 18 wei)
  * Dropdown depositToken, fill params and click transact
    * token : your token address (ex. KSP : 0xc6a2ad8cc6e4a7e08fc37cc5954be07d499e7654)
    * toAddr : address for receive bridged token
    * amount : amount for bridging (ex. 0.04 KSP = 40000000000000000, 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

<div align="left"><img src="/files/Wuh5gsMgr8uxQFmswuII" alt=""></div>

<div align="left"><img src="/files/rUJ5ksZXdyuncInjuEJv" alt=""></div>

![](/files/T9l4HENghzYAdYpZ4MF9)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://orbit-1.gitbook.io/bridgedocs/token-registration-for-bridging/registration-using-remix.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.