-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
43 changed files
with
1,364 additions
and
2,357 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
27 changes: 12 additions & 15 deletions
27
i18n/ind/docusaurus-plugin-content-docs/current/about-lisk/bridged-tokens.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,31 +1,28 @@ | ||
--- | ||
id: bridged-tokens | ||
title: Bridged Token Addresses | ||
title: Alamat Token yang di-bridge | ||
sidebar_position: 2 | ||
description: 'A reference page listing all tokens bridged to Lisk.' | ||
keywords: | ||
[ | ||
'Lisk', | ||
'Bridged tokens' | ||
] | ||
slug: /bridged-tokens | ||
description: 'Halaman referensi yang mencantumkan semua token yang di-bridge ke Lisk.' | ||
keywords: ['Lisk', 'token yang di-bridge'] | ||
--- | ||
|
||
# Bridged Token Addresses | ||
# Alamat Token yang di-bridge | ||
|
||
This page summarizes officially reviewed tokens deployed on Lisk and their corresponding L1 addresses. | ||
Halaman ini merangkum token-token yang telah ditinjau secara resmi dan di-deploy di Lisk, beserta alamat L1 yang sesuai. | ||
|
||
The list is based on the [Superchain Token List](https://github.com/ethereum-optimism/ethereum-optimism.github.io). | ||
Daftar ini berdasarkan [Daftar Token Superchain](https://github.com/ethereum-optimism/ethereum-optimism.github.io). | ||
|
||
:::tip | ||
If you want to add a token to the list, please check out the guide [Bridging an L1 token to Lisk](/building-on-lisk/add-token-to-lisk/index.md). | ||
Jika Anda ingin menambahkan token ke daftar ini, silakan lihat panduan [Bridge Token L1 ke Lisk](/building-on-lisk/add-token-to-lisk/index.md). | ||
::: | ||
|
||
## Lisk Mainnet | ||
|
||
| Bridged Tokens Mainnet | Symbol | L1 Token | L2 Token | | ||
| :----------------- | :----- |:----------------- | :----------------- | | ||
| Bridged Token di Mainnet | Simbol | Token L1 | Token L2 | | ||
| :----------------------- | :----- | :------- | :------- | | ||
|
||
## Lisk Sepolia | ||
|
||
| Bridged Tokens Sepolia | Symbol | L1 Token | L2 Token | | ||
| :----------------- | :----- |:----------------- | :----------------- | | ||
| Bridged Token di Sepolia | Simbol | Token L1 | Token L2 | | ||
| :----------------------- | :----- | :------- | :------- | |
104 changes: 52 additions & 52 deletions
104
i18n/ind/docusaurus-plugin-content-docs/current/about-lisk/contracts.mdx
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6 changes: 3 additions & 3 deletions
6
i18n/ind/docusaurus-plugin-content-docs/current/building-on-lisk/_category_.json
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,8 +1,8 @@ | ||
{ | ||
"label": "Building on Lisk", | ||
"label": "Membangun di atas Lisk", | ||
"position": 3, | ||
"link": { | ||
"type": "generated-index", | ||
"description": "Guides for developers wanting to build on Lisk L2." | ||
"description": "Panduan untuk pengembang yang ingin membangun di Lisk L2." | ||
} | ||
} | ||
} |
174 changes: 87 additions & 87 deletions
174
...plugin-content-docs/current/building-on-lisk/add-token-to-lisk/custom-token.mdx
Large diffs are not rendered by default.
Oops, something went wrong.
124 changes: 65 additions & 59 deletions
124
...usaurus-plugin-content-docs/current/building-on-lisk/add-token-to-lisk/index.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,103 +1,109 @@ | ||
--- | ||
title: Introduction | ||
title: Pengenalan | ||
sidebar_position: 1 | ||
slug: /building-on-lisk/add-token-to-lisk | ||
description: 'Guide to adding external ERC-20 contracts deployed on Ethereum to Lisk network.' | ||
description: 'Panduan menambahkan contract ERC-20 eksternal yang telah di-deploy di Ethereum ke jaringan Lisk.' | ||
keywords: | ||
[ | ||
'ERC-20 contract', | ||
'Contract ERC-20', | ||
'Lisk Testnet', | ||
'Sepolia', | ||
'Ethereum', | ||
'Lisk Mainnet', | ||
'Lisk', | ||
'Optimism Superchain token list', | ||
'daftar token Optimism Superchain', | ||
] | ||
--- | ||
|
||
# Bridging an L1 token to Lisk | ||
This page is intended for token issuers who already have an ERC-20 contract deployed on Ethereum and would like to submit their token for bridging between Ethereum and Lisk. | ||
Lisk uses the Superchain Token List as a reference for tokens that have been deployed on Lisk. | ||
In case you want to create a new token on Lisk, please refer to the page [Token development](../token-development/overview.md). | ||
# Bridge Token L1 ke Lisk | ||
|
||
Halaman ini ditujukan untuk penerbit token yang sudah memiliki contract ERC-20 yang di-deploy di Ethereum dan ingin men-submit token mereka untuk bridge antara Ethereum dan Lisk. | ||
Lisk menggunakan Superchain Token List sebagai referensi untuk token-token yang telah di-deploy di Lisk. | ||
Jika Anda ingin membuat token baru di Lisk, silakan merujuk ke halaman [Pengembangan Token](../token-development/overview.md). | ||
|
||
## Superchain Token List | ||
The [Superchain Token List](https://github.com/ethereum-optimism/ethereum-optimism.github.io) exists to help users discover the correct bridged token addresses for any given native token. | ||
|
||
Consider checking this list to make sure that you're not using the wrong bridged representation of a token when bridging a native token. | ||
<!-- TODO: Add reference to Bridges tokens addresses page, once created for Lisk: https://docs.optimism.io/builders/app-developers/bridging/standard-bridge#searching-the-token-list --> | ||
[Superchain Token List](https://github.com/ethereum-optimism/ethereum-optimism.github.io) bertujuan membantu pengguna menemukan alamat yang benar untuk setiap token native yang di-bridge. | ||
|
||
Pastikan untuk memeriksa daftar ini agar Anda tidak menggunakan representasi token yang salah ketika bridge suatu token native. | ||
|
||
<!-- TODO: Tambahkan referensi ke halaman alamat token yang di-bridge setelah halaman tersebut dibuat untuk Lisk.: https://docs.optimism.io/builders/app-developers/bridging/standard-bridge#searching-the-token-list --> | ||
|
||
:::warning | ||
Lisk does not endorse any of the tokens that are listed in the [**ethereum-optimism.github.io**](https://github.com/ethereum-optimism/ethereum-optimism.github.io) repository and relies on the preliminary checks put in place, listed on the repository. | ||
Lisk tidak meng-endorse token apa pun yang tercantum dalam repositori [**ethereum-optimism.github.io**](https://github.com/ethereum-optimism/ethereum-optimism.github.io), dan bergantung pada pemeriksaan awal yang telah ditetapkan serta dicantumkan di repositori tersebut. | ||
::: | ||
|
||
Developers who are creating their own bridged tokens should consider [adding their token to the list](#adding-your-token-to-the-superchain-token-list). | ||
Developer yang membuat token yang di-bridge mereka sendiri sebaiknya mempertimbangkan untuk [menambahkan token mereka ke dalam list](#menambahkan-token-anda-ke-superchain-token-list). | ||
|
||
Token yang ada di Superchain Token List akan otomatis muncul di beberapa tool seperti [Superchain Bridges UI](https://app.optimism.io/bridge). | ||
Namun, token tidak secara otomatis tercantum di [Lisk Bridge UI](https://bridge.lisk.com/bridge/lisk); pencantuman tersebut tidak dijamin dan tidak bersifat otomatis. | ||
Peninjauan untuk Lisk Bridge dilakukan secara manual oleh tim Lisk. | ||
|
||
Tokens on the Superchain Token List will automatically appear on certain tools like the [Superchain Bridges UI](https://app.optimism.io/bridge). | ||
However, tokens are not necessarily listed on the [Lisk Bridge UI](https://bridge.lisk.com/bridge/lisk); their listing is neither guaranteed nor automatic. | ||
Lisk Bridge reviews are conducted manually by the Lisk team. | ||
## Bridge Standar | ||
|
||
## The Standard Bridge | ||
Before a token native to one chain can be bridged to the other chain, a bridged representation of that token must be created on the receiving side. | ||
The [Standard Bridge](https://docs.optimism.io/builders/app-developers/bridging/standard-bridge) allows users to convert tokens that are native to one chain (like Ethereum) into a representation of those tokens on the other chain (like Lisk). | ||
Users can then convert these bridged representations back into their original native tokens at any time. | ||
Sebelum token yang berasal dari satu chain dapat di-bridge ke chain lainnya, representasi token yang di-bridge harus dibuat di sisi penerima. | ||
[Bridge Standar](https://docs.optimism.io/builders/app-developers/bridging/standard-bridge) memungkinkan pengguna untuk mengonversi token yang berasal dari satu chain (seperti Ethereum) menjadi representasi token tersebut di chain lain (seperti Lisk). | ||
Pengguna kemudian dapat mengonversi representasi token yang di-bridge ini kembali ke token native aslinya kapan saja. | ||
|
||
:::tip | ||
This bridging mechanism functions identically in both directions — tokens native to Lisk can be bridged to Ethereum, just like tokens native to Ethereum can be bridged to Lisk. | ||
Mekanisme bridging ini berfungsi secara identik di kedua arah — token yang berasal dari Lisk dapat di-bridge ke Ethereum, sama seperti token yang berasal dari Ethereum dapat di-bridge ke Lisk. | ||
::: | ||
|
||
A bridged representation of a token is an ERC-20 token that implements the `IOptimismMintableERC20`[^1] interface. | ||
A native token may have more than one bridged representation at the same time. | ||
Users must always specify which bridged token they wish to use when using the bridge; see [Superchain Token List](#superchain-token-list). | ||
Different bridged representations of the same native token are considered entirely independent tokens. | ||
Representasi token yang di-bridge adalah token ERC-20 yang mengimplementasikan interface `IOptimismMintableERC20`[^1]. | ||
Token native dapat memiliki lebih dari satu representasi yang di-bridge dalam waktu yang bersamaan. | ||
Pengguna harus selalu menentukan token yang ingin mereka gunakan saat menggunakan bridge; lihat [Superchain Token List](#superchain-token-list). Representasi token yang berbeda untuk token native yang sama dianggap sebagai token yang sepenuhnya independen. | ||
|
||
Bridge Standar adalah smart contract sederhana dengan fungsionalitas untuk memindahkan token ERC-20 antara Lisk dan Ethereum. | ||
|
||
Pada protokol terdiri dari dua contract penting: | ||
|
||
- Contract bridge yang di-deploy di **Ethereum**, disebut [L1StandardBridge](https://etherscan.io/address/0x2658723Bf70c7667De6B25F99fcce13A16D25d08). | ||
- Contract bridge yang di-deploy di **Lisk**, disebut [L2StandardBridge](https://blockscout.lisk.com/address/0x4200000000000000000000000000000000000010). | ||
|
||
The Standard Bridge is a simple smart contract, with the functionality to move ERC-20 tokens between Lisk and Ethereum. | ||
Kedua contract ini berinteraksi satu sama lain melalui sistem `CrossDomainMessenger` untuk mengirim pesan antara Ethereum dan Lisk. | ||
|
||
The protocol consists of two pertinent contracts: | ||
[^1]: | ||
Interface `IOptimismMintableERC20` adalah kumpulan dari [interface ERC-20 standar](https://eips.ethereum.org/EIPS/eip-20) dan mencakup fungsi-fungsi yang memungkinkan bridge untuk memverifikasi deposit/withdrawals serta mint/burn token sesuai kebutuhan. | ||
Semua versi token yang di-bridge harus mengimplementasikan interface ini agar dapat di-bridge menggunakan sistem [Bridge Standar](#bridge-standar). | ||
Token native tidak perlu mengimplementasikan interface ini. | ||
|
||
- A bridge contract deployed to **Ethereum**, called [L1StandardBridge](https://etherscan.io/address/0x2658723Bf70c7667De6B25F99fcce13A16D25d08). | ||
- A bridge contract deployed to **Lisk**, called [L2StandardBridge](https://blockscout.lisk.com/address/0x4200000000000000000000000000000000000010). | ||
## Menambahkan Token Anda ke Superchain Token List | ||
|
||
These two contracts interact with one another via the `CrossDomainMessenger` system for sending messages between Ethereum and Lisk. | ||
Lisk menggunakan [Superchain Token List](https://github.com/ethereum-optimism/ethereum-optimism.github.io/blob/master/optimism.tokenlist.json) sebagai referensi untuk token-token yang telah di-deploy di Lisk. | ||
|
||
[^1]: The `IOptimismMintableERC20` interface is a superset of the [standard ERC-20 interface](https://eips.ethereum.org/EIPS/eip-20) and includes functions that allow the bridge to properly verify deposits/withdrawals and mint/burn tokens as needed. | ||
All bridged versions of tokens must implement this interface in order to be bridged with the [Standard Bridge](#the-standard-bridge) system. | ||
Native tokens do not need to implement this interface. | ||
Untuk menambahkan token Anda ke dalam list, lakukan langkah-langkah berikut. | ||
|
||
### Langkah 1: Deploy Token Anda di Lisk | ||
|
||
## Adding your token to the Superchain Token List | ||
Pilih framework bridging yang Anda inginkan, dan gunakan untuk deploy ERC-20 token Anda di Lisk. | ||
Kami merekomendasikan Anda menggunakan framework yang disediakan oleh contract [bridge standar](#bridge-standar) milik Lisk dan deploy token Anda menggunakan [OptimismMintableERC20Factory](/about-lisk/contracts.mdx#jaringan-lisk-l2). | ||
Deploy token Anda di Lisk dengan cara ini memberikan jaminan tambahan yang akan memperlancar proses persetujuan. | ||
Jika Anda memilih framework bridging lain, interfacenya harus kompatibel dengan bridge standar. Jika tidak, kami mungkin akan kesulitan untuk mendukungnya. | ||
|
||
Lisk uses the [Superchain Token List](https://github.com/ethereum-optimism/ethereum-optimism.github.io/blob/master/optimism.tokenlist.json) as a reference for tokens that have been deployed on Lisk. | ||
Untuk instruksi langkah demi langkah tentang cara deploy token ERC-20 di Lisk, silakan lihat panduan berikut: | ||
|
||
To add your token to the list, perform the following steps. | ||
- [Deploy Token ERC-20 Standar](./standard-token.md) | ||
- [Deploy Token ERC-20 Sendiri](./custom-token.mdx) | ||
|
||
### Step 1: Deploy your token on Lisk | ||
Select your preferred bridging framework and use it to deploy an ERC-20 for your token on Lisk. | ||
We recommend you use the framework provided by Lisk's [standard bridge](#the-standard-bridge) contracts and, furthermore, deploy your token using the [OptimismMintableERC20Factory](/about-lisk/contracts.mdx#lisk-network-l2). | ||
Deploying your token on Lisk in this manner provides us with guarantees that will smooth the approval process. | ||
If you choose a different bridging framework, its interface must be compatible with that of the standard bridge. | ||
Otherwise, it may be difficult for us to support them. | ||
### Langkah 2: Ajukan Detail Token Anda | ||
|
||
For step-by-step instructions on how to deploy ERC-20 tokens on Lisk, check the following guides: | ||
Ikuti instruksi di [repositori GitHub](https://github.com/ethereum-optimism/ethereum-optimism.github.io) dan ajukan Pull Request (PR) yang berisi detail yang diperlukan untuk token Anda. | ||
Khususnya, ikuti petunjuk khusus Lisk yang dijelaskan secara rinci di bagian [Menentukan chain](https://github.com/ethereum-optimism/ethereum-optimism.github.io?tab=readme-ov-file#specifying-chains). | ||
|
||
- [Deploying a Standard ERC-20 token](./standard-token.md) | ||
- [Deploying a Custom ERC-20 token](./custom-token.mdx) | ||
**Penting:** Anda harus menentukan bagian `lisk-sepolia` dan/atau `lisk` di file `data.json` token Anda. | ||
|
||
### Step 2: Submit details of your token | ||
Follow the instructions in the [GitHub repository](https://github.com/ethereum-optimism/ethereum-optimism.github.io) and submit a PR containing the required details for your token. | ||
Especially, follow the Lisk-specific instructions detailed in the section [Specifying chains](https://github.com/ethereum-optimism/ethereum-optimism.github.io?tab=readme-ov-file#specifying-chains). | ||
[PR ini](https://github.com/ethereum-optimism/ethereum-optimism.github.io/pull/899) menunjukkan perubahan yang diperlukan untuk menambahkan token LSK ke Superchain Token Registry. | ||
Perubahan yang perlu Anda ajukan akan menjadi lebih sederhana jika token Anda sudah ditambahkan ke Superchain Token Registry. | ||
Sebagai contoh, [PR ini](https://github.com/ethereum-optimism/ethereum-optimism.github.io/commit/27ab9b2d3388f7feba3a152e0a0748c73d732a68) menunjukkan perubahan yang diperlukan untuk cbETH, yang sudah ada di Superchain Token Registry dan bergantung pada bridge standar Base. | ||
|
||
**Important:** You must specify in your token's `data.json` file a section for `lisk-sepolia` and/or `lisk`. | ||
### Langkah 3: Tunggu Persetujuan Akhir | ||
|
||
[This PR](https://github.com/ethereum-optimism/ethereum-optimism.github.io/pull/899) shows the changes necessary to add the LSK token to the Superchain Token Registry. | ||
The change you need to submit is particularly simple if your token has already been added to the Superchain Token Registry. | ||
For example, [this PR](https://github.com/ethereum-optimism/ethereum-optimism.github.io/commit/27ab9b2d3388f7feba3a152e0a0748c73d732a68) shows the change required for cbETH, which was already on Superchain Token Registry and relies on the Base standard bridge. | ||
Peninjauan secara rutin dilakukan oleh tim Lisk, dan Anda akan menerima balasan dalam waktu 24-72 jam (tergantung apakah PR diajukan pada hari kerja, akhir pekan, atau hari libur). | ||
|
||
### Step 3: Await final approval | ||
Reviews are regularly conducted by the Lisk team and you should receive a reply within 24-72 hours (depending on if the PR is opened on a weekday, weekend or holiday). | ||
## Langkah 4 : Menambahkan Token ke Gelato Bridge | ||
|
||
## Step 4 : Add token to Gelato Bridge | ||
To add your token to the [Gelato Bridge](https://bridge.lisk.com/), reach out to the Lisk team on [Lisk Discord](https://lisk.chat) with the details of the token: | ||
Untuk menambahkan token Anda ke [Gelato Bridge](https://bridge.lisk.com/), hubungi tim Lisk di [Discord Lisk](https://lisk.chat) dengan detail token tersebut: | ||
|
||
- Go to the `#lisk-dev` channel. | ||
- Tag a moderator, ask them to add your token to the Gelato Bridge, and share the link to your PR from [step 2: token details](#step-2-submit-details-of-your-token). | ||
- The Lisk team will then coordinate with Gelato to get the token added to the Gelato Bridge. | ||
- Masuk ke channel `#lisk-dev`. | ||
- Tag seorang moderator, minta mereka untuk menambahkan token Anda ke Gelato Bridge, dan bagikan tautan PR Anda dari [langkah 2: detail token](#langkah-2-ajukan-detail-token-anda). | ||
- The Lisk team will then coordinate with Gelato to get the token added to the Gelato Bridge. |
Oops, something went wrong.