-
Notifications
You must be signed in to change notification settings - Fork 135
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(bridges): add bridge explorer content
- Loading branch information
1 parent
28f8532
commit 09f8f56
Showing
8 changed files
with
93 additions
and
6 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,86 @@ | ||
--- | ||
title: Bridge Explorer | ||
description: Bridge Explorer for Omnibridge and xDAI bridge | ||
keywords: [bridge explorer, ethereum, gnosis] | ||
--- | ||
|
||
# Bridge Explorer | ||
|
||
:::info | ||
https://bridge-explorer.gnosischain.com/ | ||
::: | ||
|
||
Bridge explorer allows user to check bridge transactions of xDAI bridge and Omnibridge, bridges configurations, and validators status. Users may also claim their bridge transactions in bridge explorer. | ||
|
||
## Transactions | ||
|
||
### How to search for your transation? | ||
|
||
1. Select **xDAI** for [xDAI bridge](./tokenbridge/xdai-bridge.md) transaction or **Omnibridge** for [Omnibridge](./tokenbridge/omnibridge.md) transaction. | ||
2. Search the transaction by inserting the transaction hash or initiator/receiver address. | ||
3. You can use different filter options to filter out the unrelevant transactions. | ||
4. Click on the transaction item to check the details of the transaction. | ||
|
||
![Search Transaction](../../static/img/bridges/bridge-explorer/search-tx.png) | ||
|
||
### What does different filters mean? | ||
|
||
**Status** | ||
|
||
1. Initiated: Transaction is initiated from the source chain. | ||
2. Collecting: Signatures from validators are being collecting for the transaction. | ||
3. Unclaimed: Transaction has collected enough signatures, but has not yet been claimed on Ethereum. | ||
4. Completed: Transaction has been bridged successfully. | ||
5. Error: Transaction is not bridged successfully. | ||
|
||
**Direction** | ||
|
||
1. Gnosis > Mainnet: The transaction is initiated from Gnosis Chain, and bridged to Ethereum mainnet, user need to claim the transaction on Ethereum mainnet. | ||
2. Mainnet > Gnosis: The transaction is initiated from Ethereum mainnet, and bridged to Gnossi Chain. | ||
|
||
**Signed by** | ||
|
||
- The transaction is signed by which validator (validator calls `submitSignatures` to sign the transaction). | ||
|
||
**Executed by** | ||
|
||
- The transaction is executed by which validator (validator calls `executeAffirmation` to execute the transaction). | ||
|
||
### How to claim your transaction | ||
|
||
1. Click **Connect** button on top right corner and connect your wallet. | ||
2. Search for your transaction | ||
3. Click **Claim** button to claim your transaction. | ||
|
||
![claim tx](../../static/img/bridges/bridge-explorer/claim-tx.png) | ||
|
||
## Bridges | ||
|
||
### Daily bridge limits | ||
|
||
This section shows insight of bridge limit and is reset every `Daily limit reset` hours. | ||
|
||
1. **Daily Limit** | ||
- Ethereum -> Gnosis Chain: Maximum amount of DAI/token that users can bridge from Ethereum to Gnosis in a day | ||
- Gnosis Chain -> Ethereum: Maximum amount of XDAI/token that users can bridge from Gnosis to Ethereum in a day. | ||
2. **Execution Daily Limit** | ||
- Ethereum -> Gnosis Chain: Maximum amount of DAI/token that bridge validators can execute and bridge from Gnosis to Ethereum in a day. | ||
- Gnosis Chain -> Ethereum: Maximum amount of XDAI/token that bridge validators can execute and bridge from Ethereum to Gnosis in a day. | ||
3. **Min. per transaction**: Minimum amount of token that users can bridge in a single transaction. | ||
4. **Max. per transaction**: Maximum amount of DAI that users can bridge in a single transaction. | ||
5. **Execution max. per transaction**: Maximum amount of token that validators can execute in a single transaction. | ||
6. **Daily limit reset**: In how many hours will the daily limit get reset to zero. | ||
7. **Token address**: Token address of corresponding token, native token(xDAI) don't have an address. | ||
|
||
![](../../static/img/bridges/bridge-explorer/bridge-info.png) | ||
|
||
### Configuration | ||
|
||
This section shows the address of key contracts. | ||
![](../../static/img/bridges/bridge-explorer/bridge-configuration.png) | ||
|
||
## Validators | ||
|
||
This section shows the insight of current bridges validators, including last seen ago, total signed and executed transactions in 24 hours, balance of validators and their addresses. | ||
|
||
![](../../static/img//bridges/bridge-explorer/validator-status.png) |
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
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.