diff --git a/docs/about/networks/_category_.json b/docs/about/networks/_category_.json index 0d619415..b45a1b72 100644 --- a/docs/about/networks/_category_.json +++ b/docs/about/networks/_category_.json @@ -2,7 +2,7 @@ "position": 1, "label": "Networks Overview", "collapsible": true, - "collapsed": false, + "collapsed": true, "link": { "type": "generated-index" } diff --git a/docs/about/specs/_category_.json b/docs/about/specs/_category_.json index 2d12e0f6..63a8e74e 100644 --- a/docs/about/specs/_category_.json +++ b/docs/about/specs/_category_.json @@ -1,5 +1,5 @@ { - "position": 2, + "position": 3, "label": "Chain Specifications", "collapsible": true, "collapsed": true, diff --git a/docs/about/networks/tokens/README.md b/docs/about/tokens/README.md similarity index 97% rename from docs/about/networks/tokens/README.md rename to docs/about/tokens/README.md index 0d110b20..c9920cde 100644 --- a/docs/about/networks/tokens/README.md +++ b/docs/about/tokens/README.md @@ -1,5 +1,5 @@ --- -sidebar_position: 2 +sidebar_position: 3 description: Gnosis uses a unique dual-token model, xdai for fees, gno for consensus keywords: [gnosis tokens, gnosis gno, gno token, xdai token, fee token, gno validation] --- diff --git a/docs/about/tokens/_category_.json b/docs/about/tokens/_category_.json new file mode 100644 index 00000000..45ce5958 --- /dev/null +++ b/docs/about/tokens/_category_.json @@ -0,0 +1,9 @@ +{ + "position": 2, + "label": "Token", + "collapsible": true, + "collapsed": true, + "link": { + "type": "generated-index" + } + } \ No newline at end of file diff --git a/docs/about/networks/tokens/gno.md b/docs/about/tokens/gno.md similarity index 100% rename from docs/about/networks/tokens/gno.md rename to docs/about/tokens/gno.md diff --git a/docs/about/networks/tokens/xdai.md b/docs/about/tokens/xdai.md similarity index 96% rename from docs/about/networks/tokens/xdai.md rename to docs/about/tokens/xdai.md index fc278b68..9130d60d 100644 --- a/docs/about/networks/tokens/xdai.md +++ b/docs/about/tokens/xdai.md @@ -12,7 +12,7 @@ xDai tokens are native tokens on Gnosis and also used to pay for execution of sm ### Bridge -Convert DAI from Ethereum to xDai using the [xDai Bridge](/bridges/tokenbridge/xdai-bridge). +Convert DAI from Ethereum to xDai using the [Unified Gnosis Bridge App](/bridges/usebridges). ### Buy xDAI diff --git a/docs/bridges/Bridge Explorer.md b/docs/bridges/Bridge Explorer.md index a3263a4e..d5af7c5c 100644 --- a/docs/bridges/Bridge Explorer.md +++ b/docs/bridges/Bridge Explorer.md @@ -6,10 +6,10 @@ keywords: [gnosis bridge, bridge architecture, omnibridge, xdai bridge] # Bridge Explorer -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. +Bridge explorer allows user to check bridge transactions of Gnosis Bridge, bridges configurations, and validators status. Users may also claim their bridge transactions in bridge explorer. :::info -https://bridge-explorer.gnosischain.com/ +https://bridge-explorer.gnosischain.com/bridge-explorer/latest-transactions ::: @@ -17,12 +17,11 @@ https://bridge-explorer.gnosischain.com/ ### 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. +1. Search the transaction by inserting the transaction hash or initiator/receiver address. +2. You can use different filter options to filter out the unrelevant transactions. +3. Click on the transaction item to check the details of the transaction. -![Search Transaction](../../static/img/bridges/bridge-explorer/search-tx.png) +![Search Transaction](../../static/img/bridges/bridge-explorer/search-new-tx.png) ### What does different filters mean? @@ -37,7 +36,7 @@ https://bridge-explorer.gnosischain.com/ **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. +2. Mainnet > Gnosis: The transaction is initiated from Ethereum mainnet, and bridged to Gnosis Chain. **Signed by** @@ -53,8 +52,12 @@ https://bridge-explorer.gnosischain.com/ 2. Search for your transaction 3. Click **Claim** button to claim your transaction. -![claim tx](../../static/img/bridges/bridge-explorer/claim-tx.png) +![Claim Transaction](../../static/img/bridges/bridge-explorer/claim-new.png) + +You can also claim your transaction from Transaction page. + +![Claim Transaction page](../../static/img/bridges/bridge-explorer/claim-tx-page.png) ### Daily bridge limits @@ -67,23 +70,23 @@ This section shows insight of bridge limit and is reset every `Daily limit reset - 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. +4. **Max. per transaction**: Maximum amount of token 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) +![](../../static/img/bridges/bridge-explorer/bridge-info-new.png) ### Configuration This section shows the address of key contracts. -![](../../static/img/bridges/bridge-explorer/bridge-configuration.png) +![](../../static/img/bridges/bridge-explorer/bridge-configuration-new.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) +![](../../static/img//bridges/bridge-explorer/validator-status-new.png) If you are not coming from Ethereum, you can use one of the following bridges: diff --git a/docs/bridges/Bridges Architecture.md b/docs/bridges/Bridges Architecture.md index e7c04ad3..9ebd9cd1 100644 --- a/docs/bridges/Bridges Architecture.md +++ b/docs/bridges/Bridges Architecture.md @@ -7,37 +7,23 @@ sidebar_position: 4 Gnosis has three main types of bridges: -- **Native Bridges**: built into the chain itself, and mint the [canonical token](./tokenbridge/omnibridge.md#canonical-token-registries) representation of the original asset on Gnosis (e.g. "Canonical Dai", "Canonical ETH") +- **Native Bridges**: built into the chain itself, and mint the xDAI and ERC20 token from Ethereum to Gnosis Chain - **3rd-party Bridges**: these are maintained by 3rd parties and allow users to swap for canonical tokens created by native bridges - **Application-Specific Bridges**: some applications may provide custom bridges that maintain their own canonical token on Gnosis ![Diagrams overview of Bridges](../../static/img/bridges/diagrams/bridge-overview.svg) -## Native Bridges +## Gnosis Chain Bridge -Gnosis has two native bridges: +Gnosis Chain bridge : +- allows to mint the native stablecoin xDAI on gnosis chain by bridging DAI from Ethereum +- allows to bridge ERC2O token from Ethereum to Gnosis Chain -- **xDai Bridge** that is used to mint the native stablecoin by bridging Dai from Ethereum -- **Omnibridge** and underlying **Arbitrary Message Bridge** that are used for bridging tokens and data - -### Bridging Dai - -See the [xDai Bridge](/bridges/tokenbridge/xdai-bridge). ### Bridging Data See the [Arbitrary Message Passing Bridge](/bridges/tokenbridge/amb-bridge) or AMB Bridge for short. -### Bridging Tokens - -See the [Omnibridge](/bridges/tokenbridge/omnibridge), which is built on top of the [Arbitrary Message Passing Bridge](/bridges/tokenbridge/amb-bridge). - -## Canonical Bridged Tokens - -Tokens that are bridged using [Omnibridge](/bridges/tokenbridge/omnibridge) are regarded as canonical representations of the origin token on Gnosis Chain. - -- [Canonical Bridged Tokens](https://gnosis.blockscout.com/tokens?tab=bridged) -- Select the origin chain by using **Filter** option. ## Roadmap diff --git a/docs/bridges/Build with Bridges/using-omnibridge/README.md b/docs/bridges/Build with Bridges/using-omnibridge/README.md index 0d23e2ae..85264ca5 100644 --- a/docs/bridges/Build with Bridges/using-omnibridge/README.md +++ b/docs/bridges/Build with Bridges/using-omnibridge/README.md @@ -7,28 +7,28 @@ keywords: [omnibridge, token bridge, gnosis, bsc, ethereum] # OmniBridge :::info -The OmniBridge and the OmniBridge UI are experimental software in Beta which you use at your own risk. The OmniBridge UI can be accessed here: https://omni.gnosischain.com/bridge +The Legacy OmniBridge and the legacy OmniBridge UI are now deprecated but still available, use it at your own risk. The OmniBridge UI can be accessed here: https://omni.legacy.gnosischain.com/bridge ::: The Omnibridge can be used to bridge ERC-20 tokens between Ethereum and Gnosis. The first time a token is bridged, a new ERC677 token contract is deployed on GC with an additional suffix to differentiate the token. It will say "token name on xDai", as this was the original chain name prior to re-branding. If a token has been bridged previously, the previously deployed contract is used. The requested token amount is minted and sent to the account initiating the transfer (or an alternative receiver account specified by the sender). -- [Tokenbridge Docs: Using the Omnibridge UI](https://docs.tokenbridge.net/eth-xdai-amb-bridge/multi-token-extension/ui-to-transfer-tokens) +- [Tokenbridge Docs](https://docs.tokenbridge.net/eth-xdai-amb-bridge/multi-token-extension/ui-to-transfer-tokens) ## Transfer any ERC-20 token from Ethereum to Gnosis -It is possible to use the OmniBridge UI to transfer any ERC20 from Ethereum to xDai. Any user can initiate this initial transfer. Once the token exists on Gnosis, it can be transferred back and forth using the same UI. +It is possible to use the [Gnosis Bridge](https://bridge.gnosischain.com) to transfer any ERC20 from Ethereum to xDai. Any user can initiate this initial transfer. Once the token exists on Gnosis, it can be transferred back and forth using the same UI. ### Token Transfer In this example, we transfer the Basic Attention Token (BAT) from Ethereum to xDai. When this process was started, this token does not yet exist on Gnosis. It takes less than 5 minutes and some ETH for gas fees. -1. Go the the [OmniBridge UI](https://omni.gnosischain.com/bridge) +1. Go the the [Legacy OmniBridge UI](https://omni.legacy.gnosischain.com/bridge) - Connect your wallet to the Ethereum Mainnet - Select the token you want to transfer (here we select BAT) and enter the amount - Click Unlock and approve the account interaction. :::note -These screenshots were taken back when Basic Attention Token (BAT) was first bridged. The steps are the same, but note that the url is old and is now https://omni.gnosischain.com/bridge +These screenshots were taken back when Basic Attention Token (BAT) was first bridged. The steps are the same, but note that the url is old and is now https://omni.legacy.gnosischain.com/bridge ::: ![](/img/bridges/omni-tokentransfer1.jpg) 2. Confirm the transaction to approve ![](/img/bridges/omni-tokentransfer2.jpg) 3. Once transaction approval is complete, you can now Transfer BAT to BAT on xDai. Click Transfer. @@ -67,7 +67,7 @@ When switching between networks within the same bridge, press the arrows icon in ## Transfer Tokens without the UI The instructions below use the Etherscan UI and the Blockscout UI to demonstrate the token transfer process. -There is an [OMNIBRIDGE UI](https://omni.gnosischain.com/bridge) also available which calls the methods of the multi-token mediators contracts described below. +There is [Legacy OMNIBRIDGE UI](https://omni.legacy.gnosischain.com/bridge) also available which calls the methods of the multi-token mediators contracts described below. ### General Case: ERC-20 Token Transfer diff --git a/docs/bridges/Build with Bridges/using-xdai-bridge/README.md b/docs/bridges/Build with Bridges/using-xdai-bridge/README.md index 4f3ccecd..5c3b7ac1 100644 --- a/docs/bridges/Build with Bridges/using-xdai-bridge/README.md +++ b/docs/bridges/Build with Bridges/using-xdai-bridge/README.md @@ -12,7 +12,8 @@ keywords: [xdai bridge, token bridge, ethereum, gnosis, gnosis bridge] You will need some Dai to transfer AND some ETH for gas (transaction fees). [Bridge minimum/maximum amounts](../../tokenbridge/xdai-bridge.md#fees--daily-limits) are set by the [bridge governors](../../tokenbridge/xdai-bridge.md#bridge-governance). Bridge may take some time to update chain stats, try refreshing or waiting a minute if you receive any errors. You can also select a [different RPC](#custom-rpc) in the Settings dropdown. ::: -1. Go to the [xDai Bridge UI](https://bridge.gnosischain.com/) and connect your wallet to the Ethereum Mainnet. Once connected, you will see your address populated in the header, and your DAI and xDai balance displayed on the page. If you change the dropdown on the page (ETH Mainnet) but not in MetaMask, the interface will update but your wallet will not auto-connect to the chain. _Switching chains in MetaMask_ however will automatically update the interface. + +1. Go to the [Legacy xDai Bridge UI](https://bridge.legacy.gnosischain.com/) and connect your wallet to the Ethereum Mainnet. Once connected, you will see your address populated in the header, and your DAI and xDai balance displayed on the page. If you change the dropdown on the page (ETH Mainnet) but not in MetaMask, the interface will update but your wallet will not auto-connect to the chain. _Switching chains in MetaMask_ however will automatically update the interface. 2. Enter the amount of Dai you would like to transfer to Gnosis, and click the Transfer button. 3. The web3 wallet window will open with transaction details. The default gas price is fine, if you would like a faster transaction you can increase. Click Submit or Confirm (depending on wallet) to initiate the transaction. 4. Wait for the transaction confirmation (this can take some time if the network is super congested). The transaction is considered finalized after 8 blocks. To check on a pending transaction, click on the tx in the UI. @@ -30,7 +31,7 @@ It is recommended to use Google Chrome and MetaMask without Ad Blockers to compl You will need a **small additional amount of xDai** to process the first transaction, and an **additional amount of Eth** to process the claim transaction on Ethereum. ::: -1. Go to the [xDai Bridge UI](https://bridge.gnosischain.com/) and connect your wallet to Gnosis Chain. Once connected, you will see your address populated in the header, and your DAI and xDai balance displayed on the page. If you change the dropdown on the page but not in MetaMask, the interface will update but your wallet will not auto-connect to the chain. _Switching chains in MetaMask_ however will automatically update the interface. +1. Go to the [Legacy xDai Bridge UI](https://bridge.legacy.gnosischain.com/) and connect your wallet to Gnosis Chain. Once connected, you will see your address populated in the header, and your DAI and xDai balance displayed on the page. If you change the dropdown on the page but not in MetaMask, the interface will update but your wallet will not auto-connect to the chain. _Switching chains in MetaMask_ however will automatically update the interface. 2. Enter the amount of xDai you would like to transfer to Dai, and click the Request button. Note that there exists a [minimum amount](../../tokenbridge/xdai-bridge.md#fees--daily-limits). 3. Confirm that you will need to perform 2 transactions, and will need xDai and Eth to complete the transfer. Click **Confirm** to process the transaction on Gnosis Chain. 4. Your web3 wallet window will open with transaction details. diff --git a/docs/bridges/README.md b/docs/bridges/README.md index aacf2532..d3608df2 100644 --- a/docs/bridges/README.md +++ b/docs/bridges/README.md @@ -4,19 +4,14 @@ title: Intro to Gnosis Bridges keywords: [gnosis bridges, omnibridge, xdai bridge] --- -Welcome to Gnosis Bridges! 🎉 -Currently, there are two types of bridges offered by Gnosis, [xDai Bridge](https://bridge.gnosischain.com/) and [OmniBridge](https://omni.gnosischain.com/bridge). Let's take a quick look at both of these. +Welcome to Gnosis Bridges! 🎉 + title="What is Gnosis Bridge App?" + subtitle="Gnosis Chain bridge is a single bridge which allows you to bridge ERC20 tokens and xDAI token from Ethereum to Gnosis Chain and vice-versa. The requested token amount is minted and sent to the account initiating the transfer (or an alternative receiver account specified by the sender)." + url="https://bridge.gnosischain.com" - + + diff --git a/docs/bridges/Token Bridge/omnibridge.md b/docs/bridges/Token Bridge/omnibridge.md index ecb53ed4..e1ddfe91 100644 --- a/docs/bridges/Token Bridge/omnibridge.md +++ b/docs/bridges/Token Bridge/omnibridge.md @@ -7,14 +7,14 @@ keywords: [omnibridge, token bridge, token claim] # Omnibridge :::info -Omnibridge can be accessed at [omni.gnosischain.com](https://omni.gnosischain.com/) +Legacy Omnibridge can be accessed at https://omni.legacy.gnosischain.com/bridge ::: ![](/img/bridges/diagrams/token-bridge-01.png) ## Key Information -[Omnibridge](https://omni.gnosischain.com/) is a native token bridge that mints the canonical representations of bridged assets on Gnosis. The Omnibridge is built on top of the [Arbitrary Message Bridge (AMB)](/bridges/tokenbridge/amb-bridge) and thus relies on the same group of [Trusted Bridge Validators](/bridges/tokenbridge/amb-bridge#bridge-validators) and trust model as the AMB. With [Telepathy added as the 8th validator](../governance/decisions.md#add-telepathy-validator-in-the-amb), Omnibridge bridge is now more secure with trustless zero-knowledge light client technology. Check out how Omnibridge works with Telepathy validator [here](amb-bridge.md#how-it-works-with-telepathy-validator). +[Omnibridge](https://omni.legacy.gnosischain.com/bridge) is a native token bridge that mints the canonical representations of bridged assets on Gnosis. The Omnibridge is built on top of the [Arbitrary Message Bridge (AMB)](/bridges/tokenbridge/amb-bridge) and thus relies on the same group of [Trusted Bridge Validators](/bridges/tokenbridge/amb-bridge#bridge-validators) and trust model as the AMB. With [Telepathy added as the 8th validator](../governance/decisions.md#add-telepathy-validator-in-the-amb), Omnibridge bridge is now more secure with trustless zero-knowledge light client technology. Check out how Omnibridge works with Telepathy validator [here](amb-bridge.md#how-it-works-with-telepathy-validator). The Omnibridge currently connects Gnosis to Ethereum. diff --git a/docs/bridges/Token Bridge/xdai-bridge.md b/docs/bridges/Token Bridge/xdai-bridge.md index 19ca81cd..afbf2183 100644 --- a/docs/bridges/Token Bridge/xdai-bridge.md +++ b/docs/bridges/Token Bridge/xdai-bridge.md @@ -8,11 +8,12 @@ keywords: [xdai bridge, bridge, dai, ethereum, gnosis bridge] :::info -The xDai bridge can be found at [bridge.gnosischain.com](https://bridge.gnosischain.com/) +The Legacy xDai bridge can be found at https://bridge.legacy.gnosischain.com/ + ::: -The [xDai bridge](https://bridge.gnosischain.com) is a native Dai bridge from Ethereum that is used to mint and burn [xDai](/concepts/tokens/xdai), the native asset used for gas and transaction fees on Gnosis. +The [Legacy xDai bridge](https://bridge.legacy.gnosischain.com/) is a native Dai bridge from Ethereum that is used to mint and burn [xDai](/concepts/tokens/xdai), the native asset used for gas and transaction fees on Gnosis. ![xDai Bridge Diagram](/img/bridges/diagrams/dai-bridge-01.png) diff --git a/docs/bridges/roadmap.md b/docs/bridges/roadmap.md index 4f8874d0..9bc2bada 100644 --- a/docs/bridges/roadmap.md +++ b/docs/bridges/roadmap.md @@ -14,6 +14,4 @@ Hashi is an EVM Hash Oracle Aggregator designed to enhance cross-chain bridge se ### Telepathy, zkSNARK-enabled Light Client bridge validator Succinct Lab's zkSNARK-enabled Light Client, Telepathy, launched in July 2023, has emerged as a key component of the AMB bridge ecosystem. Utilizing zkSNARKs, Telepathy provides validity proofs, ensuring trustless verification of transaction events across chains. This solution has become one of the most active bridge validators in the AMB network, enhancing security and reliability for cross-chain transactions. -![Hashi Architecture](../../static/img/bridges/diagrams/Hashi-architecture.png) - After successful audits and release, we aim to gradually migrate our canonical bridges to Hashi’s distributed trust model. \ No newline at end of file diff --git a/docs/bridges/usebridges.md b/docs/bridges/usebridges.md new file mode 100644 index 00000000..f1707376 --- /dev/null +++ b/docs/bridges/usebridges.md @@ -0,0 +1,67 @@ +--- +sidebar_position: 2 +title: How to use Gnosis Bridge ? +keywords: [gnosis bridges, omnibridge, xdai bridge] +--- +:::info +To begin using Gnosis Bridge App, you need to go on this following link : https://bridge.gnosischain.com/ +::: + +:::note +You will need xDAI to perform any transactions on Gnosis Chain as it’s the chain’s gas token. You can get xDAI by transferring DAI from Ethereum using the Bridge Explorer +::: + +![xDAI bridge from ethereum](../../static/img/bridges/bridge-xdai-new.png) + +### Follow the below steps to get xDAI into your Ethereum address: +1. Go to the Gnosis Chain Bridge UI and connect your wallet to the Ethereum Mainnet. +2. Once connected, you will see your address populated in the header, and your DAI balance will be displayed on the page. +3. Enter the amount of Dai you would like to transfer to Gnosis, and click the Transfer button. +4. The web3 wallet window will open with transaction details. The default gas price is fine, if you would like a faster transaction you can increase. Click Submit or Confirm (depending on wallet) to initiate the transaction. +5. Wait for the transaction confirmation (this can take some time if the network is super congested). The transaction is considered finalized after 8 blocks. To check on a pending transaction, click on the tx in the UI. + + +### Follow the below steps to get ERC20 token from Ethereum address to Gnosis Chain: + +1. Go the Gnosis Bridge UI +2. Connect your wallet to the Ethereum Mainnet +3. Select the token you want to transfer and enter the amount of token you want. +4. Click Bridge and sign the transaction + +![Bridge erc 20 token to gnosis chain](../../static/img/bridges/bridge-erc20-new.png) + +Transactions from Ethereum to Gnosis Chain are expected to take ~26 mins (130 blocks) because of the verification through the ZK light client + + + +You can view and monitor your transactions by visiting this URL: https://bridge.gnosischain.com/bridge-explorer/latest-transactions + +- To see status of one specific transaction by pasting the transaction hash in the explorer : https://bridge.gnosischain.com/bridge-explorer + +You can also check out all the transactions you have done by checking out the history from "My Transactions" of your connected wallet. + + +![My transactions](../../static/img/bridges/bridge-explorer/transaction-history.png) + +:::note +If you are bridging from Gnosis to Ethereum, you have to claim your funds on Ethereum after the bridge transcation has been validated. You can do this by finding your transaction on the Bridge Explorer and clicking “claim” +::: +![Search Transaction](../../static/img/bridges/bridge-explorer/claim-new.png) + +:::note +Please note that Gnosis bridges have certain limits. You can check these limits by visiting this URL: https://bridge-explorer.gnosischain.com/bridge-explorer/bridges/ +If you are bridging funds that exceed the daily limit, your transaction will be delayed till after the bridge limits reset (every 24h). +::: + +:::info +If you are not coming from Ethereum, you can use one of the following bridges: + +Jumper (provided by Li.Fi) +Bungee +Hop +Connext +::: + +### Need more help? + +Join the Gnosis Chain Discord and if you need to troubleshoot a specific bridge issue, feel free to open a support ticket and tell us more about it. \ No newline at end of file diff --git a/docs/bridges/using-gnosis-bridges/OmniBridge.md b/docs/bridges/using-gnosis-bridges/OmniBridge.md deleted file mode 100644 index 27c3f6e3..00000000 --- a/docs/bridges/using-gnosis-bridges/OmniBridge.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Using OmniBridge -description: Bridge ERC-20 tokens between Ethereum and Gnosis. -keywords: - [amb bridge, arbitrary message bridge, using amb, bridge, gnosis bridge, omnibridge, OmniBridges] ---- - - -## Transfer any ERC-20 token from Ethereum to Gnosis -It is possible to use the OmniBridge UI to transfer any ERC20 from Ethereum to xDai. Any user can initiate this initial transfer. Once the token exists on Gnosis, it can be transferred back and forth using the same UI. - -### Token Transfer -We transfer an ERC20 token from Ethereum to xDai. When this process was started, this token does not yet exist on Gnosis. It takes less than 5 minutes and some ETH for gas fees. - -1. Go the the OmniBridge UI - - Connect your wallet to the Ethereum Mainnet - - Select the token you want to transfer and enter the amount of token you want. - - Click Unlock and approve the account interaction. - -2. Confirm the transaction to approve. -3. Once transaction approval is complete, you can now transfer your selected token from Ethereum to Gnosis Chain. You can now finally transfer and move on next steps. -4. Press Confirm to approve the transfer and pay the gas fees. These may be expensive depending on network congestion. We recommend checking current gas prices. Because of high fees, it also may make sense to bridge over a larger amount of tokens in a single transaction rather than several smaller ones. -5. The bridge transaction will begin to process. While you are waiting for block confirmations, you can click on the ALM monitor link to view progress of your transfer, or you can view the [ALM monitor here](https://alm-bridge-monitor.gnosischain.com/) and look up your transaction by the transaction hash. \ No newline at end of file diff --git a/docs/bridges/using-gnosis-bridges/_category_.json b/docs/bridges/using-gnosis-bridges/_category_.json deleted file mode 100644 index 766e16b5..00000000 --- a/docs/bridges/using-gnosis-bridges/_category_.json +++ /dev/null @@ -1,10 +0,0 @@ -{ - "position": 2, - "label": "How to use Gnosis Bridges", - "collapsible": true, - "collapsed": false, - "link": { - "type": "generated-index", - "title": "Learn how to use xDAI bridge and Omni Bridge" - } - } \ No newline at end of file diff --git a/docs/bridges/using-gnosis-bridges/xDai Bridge.md b/docs/bridges/using-gnosis-bridges/xDai Bridge.md deleted file mode 100644 index 5a60d129..00000000 --- a/docs/bridges/using-gnosis-bridges/xDai Bridge.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Using xDai Bridge -description: Bridge DAI to xDAI and vice versa. -keywords: - [amb bridge, arbitrary message bridge, using amb, bridge, gnosis bridge, omnibridge, OmniBridges] ---- - -:::note -You will need some Dai to transfer and some ETH for gas (transaction fees). Bridge minimum/maximum amounts are set by the bridge governors. Bridge may take some time to update chain stats, try refreshing or waiting a minute if you receive any errors. You can also select a different RPC in the Settings dropdown - -::: - -## Moving Dai from Ethereum to xDai on Gnosis - -1. Go to the xDai Bridge UI and connect your wallet to the Ethereum Mainnet. -2. Once connected, you will see your address populated in the header, and your DAI and xDai balance displayed on the page. -- If you change the dropdown on the page (ETH Mainnet) but not in MetaMask, the interface will update but your wallet will not auto-connect to the chain. Switching chains in MetaMask however will automatically update the interface. -3. Enter the amount of Dai you would like to transfer to Gnosis, and click the Transfer button. -4. The web3 wallet window will open with transaction details. The default gas price is fine, if you would like a faster transaction you can increase. Click Submit or Confirm (depending on wallet) to initiate the transaction. -5. Wait for the transaction confirmation (this can take some time if the network is super congested). The transaction is considered finalized after 8 blocks. To check on a pending transaction, click on the tx in the UI. - -6. Once the initial transfer confirmation is successful, you will see consecutive 'Transfer Pending' notifications with: - - 20 of 20 block confirmations - - Countdown with continue until 1 block confirmation is left. - - Waiting for execution on Gnosis Chain side. - - Transfer Complete. - -7. Click on View on BlockScout to see details about the transaction. If you scroll down you will see the address (your address where the xdai was sent), value (amount sent in wei), and transactionHash, which will match the hash from the initial transaction. - - -## Moving xDai from Gnosis back to Dai on Ethereum - -:::note -It is recommended to use Google Chrome and MetaMask without Ad Blockers to complete this process. -You will need a small additional amount of xDai to process the first transaction, and an additional amount of Eth to process the claim transaction on Ethereum. - -::: - -1. Go to the xDai Bridge UI and connect your wallet to Gnosis Chain. Once connected, you will see your address populated in the header, and your DAI and xDai balance displayed on the page. - -2. If you change the dropdown on the page but not in MetaMask, the interface will update but your wallet will not auto-connect to the chain. Switching chains in MetaMask however will automatically update the interface. - -3. Enter the amount of xDai you would like to transfer to Dai, and click the Request button. Note that there exists a minimum amount. -4. Confirm that you will need to perform 2 transactions, and will need xDai and Eth to complete the transfer. Click Confirm to process the transaction on Gnosis Chain. - - Your web3 wallet window will open with transaction details. - - Wait for 8 block confirmations. You will see several popups with block confirmation info. - - You will see a modal instructing you switch networks in your MetaMask (or other web3 wallet) to the Ethereum Mainnet. - - After you switch networks the Claim button will appear. Press to proceed. -5. Confirm the second claim transaction in MetaMask (you will need some Eth for gas fees). Once processed, the Dai should be available in your wallet. - -:::info -If you are interested in converting Dai to xDai without the UI see how to use xDai Bridge without UI - - -::: \ No newline at end of file diff --git a/docs/technicalguides/account-abstraction/README.md b/docs/technicalguides/account-abstraction/README.md index 5babf42f..92428445 100644 --- a/docs/technicalguides/account-abstraction/README.md +++ b/docs/technicalguides/account-abstraction/README.md @@ -62,7 +62,9 @@ For more information on Gelato , visit the [Gelato documentation](https://docs.g For more details, refer to the [Safe documentation](https://docs.safe.global/). -## Choosing the Right Option +:::info +AA with ZeroDev (coming up soon) +::: +--- -When deciding on an AA solution for your project on Gnosis Chain, consider the specific needs of your application, such as the level of security required, the desired user experience, and the technical capabilities of your team. Each option offers unique features and benefits, so it's important to evaluate them in the context of your project's requirements. diff --git a/docs/tools/Data Indexing/covalent.md b/docs/tools/Data Indexing/covalent.md new file mode 100644 index 00000000..57bb05ec --- /dev/null +++ b/docs/tools/Data Indexing/covalent.md @@ -0,0 +1,121 @@ +# Covalent + +[Covalent](https://www.covalenthq.com/?utm_source=gnosis-chain&utm_medium=partner-docs) is a hosted blockchain data solution providing access to historical and current onchain data for [200+ supported blockchains](https://www.covalenthq.com/docs/networks/?utm_source=gnosis-chain&utm_medium=partner-docs), including Gnosis Chain. + +Covalent maintains a full replica of every supported blockchain, meaning you have access to: + +- Current and historical account balances +- Full transaction histories +- Every contract log event +- All NFTs including assets and metadata + +**Use Covalent if you need:** + +- Wallet, Transactions, NFT, DEX, Staking or core blockchain data (log events, blocks) +- Normalized, aggregated and enhanced multichain data, well beyond what you get from RPC providers +- Enterprise-grade performance + +> **[Sign up to start building on Gnosis Chain](https://www.covalenthq.com/platform/?utm_source=gnosis-chain&utm_medium=partner-docs)** + +# APIs + +The Covalent APIs enables developers to quickly and easily access structured onchain data. This means consistent response schemas regardless of the blockchain. Available APIs and corresponding use cases include: + +### Wallet API + +- **Features:** All token balances (ERC20, 721, 1155, native), token transfers and prices (spot & historical) for a wallet. +- **Use cases:** [Wallets, portfolio trackers](https://goldrush-wallet-portfolio-ui.vercel.app/?utm_source=gnosis-chain&utm_medium=partner-docs), token gating, airdrop snapshots. + +### NFT API + +- **Features:** Media assets, metadata, sales, owners, trait & attribute filters, thumbnails & previews. +- **Use cases:** [NFT galleries & marketplaces](https://goldrush-nft-gallery-ui.vercel.app/?utm_source=gnosis-chain&utm_medium=partner-docs), real world asset (RWA) tracking, token gating. + +### DEX API + +- **Features:** Positions, rewards, pool and token details for major DEX protocols. +- **Use cases:** [Analytics dashboards](https://goldrush-uniswap-dex-dashboard.vercel.app/?utm_source=gnosis-chain&utm_medium=partner-docs), leaderboards, reward calculators. + +### Cross-Chain Activity API + +- **Features:** Single API call to fetch a list of active chains and the latest transaction date on each for an address. +- **Use cases:** [App onboarding](https://goldrush-wallet-portfolio-ui.vercel.app/activity/0xfc43f5f9dd45258b3aff31bdbe6561d97e8b71de/?utm_source=gnosis-chain&utm_medium=partner-docs). + +### Transactions API + +- **Features:** All historical transactions with human-readable log events. Includes gas usage/spend summaries. +- **Use cases:** [Accounting and tax tools](https://bit.ly/crypto-tax-tool), branded in-app [transaction receipts](https://goldrush-dfk-tx-receipt-ui.vercel.app/tx/defi-kingdoms-mainnet/0x4e5c0af28b2cea27d06677fae1f573572e0ff863c43ae42d2959ca67b90c4390/?utm_source=gnosis-chain&utm_medium=partner-docs). + +### Security API + +- **Features:** NFT and ERC20 token allowances, including value-at-risk. +- **Use cases:** Revoke features in wallets, security applications. + +### Blockchain API + +- **Features:** Block details, log events by contract address or topic hash, gas prices. +- **Use cases:** Custom block explorers. + +## Developer Tools + +There are 3 primary developer tools for using the APIs: + +1. [**Unified API**](https://www.covalenthq.com/docs/api/?utm_source=gnosis-chain&utm_medium=partner-docs) - enterprise-grade endpoints to use with any programming language. Switch blockchains with one path parameter. + + ```bash + curl -X GET https://api.covalenthq.com/v1/gnosis-mainnet/address/0x2C6900b24221dE2B4A45c8c89482fFF96FFB7E55/balances_v2/ \ + -H 'Content-Type: application/json' \ + -u YOUR_API_KEY: + ``` + +2. [**Client SDKs**](https://www.covalenthq.com/docs/unified-api/sdk/?utm_source=gnosis-chain&utm_medium=partner-docs) - official client libraries including TypeScript, Go and Python. + ```jsx + npm install @covalenthq/client-sdk + ``` + + + ```jsx + import { CovalentClient } from "@covalenthq/client-sdk"; + + (async () => { + try { + const client = new CovalentClient("YOUR_API_KEY"); + const transactions = client.TransactionService.getAllTransactionsForAddress("gnosis-mainnet", "0x2C6900b24221dE2B4A45c8c89482fFF96FFB7E55"); + + for await (const tx of transactions) { + console.log("tx", tx); + } + } catch (error) { + console.log(error.message); + } + })(); + ``` + +3. [**GoldRush Kit**](https://github.com/covalenthq/goldrush-kit/?utm_source=gnosis-chain&utm_medium=partner-docs) - beautifully designed React components for your dApp frontend + [![GoldRush Component Example](https://www.datocms-assets.com/86369/1711147954-goldrush_wallet_ui_example.png)](https://goldrush-wallet-portfolio-ui.vercel.app/dashboard/balance/0xfc43f5f9dd45258b3aff31bdbe6561d97e8b71de/transfers/eth-mainnet/0xf8c3527cc04340b208c854e985240c02f7b7793f) + +## Get started + +- **[API Key](https://www.covalenthq.com/platform/auth/register/?utm_source=gnosis-chain&utm_medium=partner-docs)** - sign up for free +- [**Docs**](https://www.covalenthq.com/docs/unified-api/?utm_source=gnosis-chain&utm_medium=partner-docs) - comprehensive knowledge base for all things Covalent +- **[Guides](https://www.covalenthq.com/docs/unified-api/guides/?utm_source=gnosis-chain&utm_medium=partner-docs)** - learn how to build for various use cases and expand your onchain knowledge + +  +# Increment +[![example-increment-chart](https://www.datocms-assets.com/86369/1684974544-increment-example-partner-docs.png)](https://www.covalenthq.com/platform/increment/#/?utm_source=gnosis-chain&utm_medium=partner-docs) + +Increment is a novel no-code charting and reporting tool powered by Covalent. *Simply type SQL, get charts.* + +## Use cases +Increment can be used for: + +- [Analyzing Blockchain Networks](https://www.covalenthq.com/docs/increment/data-models/chain-gdp/?utm_source=gnosis-chain&utm_medium=partner-docs) +- [Analyzing DEXs](https://www.covalenthq.com/docs/increment/data-models/swap-land/?utm_source=gnosis-chain&utm_medium=partner-docs) +- [Analyzing NFT Marketplaces](https://www.covalenthq.com/docs/increment/data-models/jpeg-analysis/?utm_source=gnosis-chain&utm_medium=partner-docs) + + +## Get started + +- [Increment](https://www.covalenthq.com/platform/increment/#/?utm_source=gnosis-chain&utm_medium=partner-docs) - login via the Covalent Platform +- [Docs](https://www.covalenthq.com/docs/increment/?utm_source=gnosis-chain&utm_medium=partner-docs) - learn how to use Increment to build dynamic, custom charts +- [Data Models Demo](https://www.covalenthq.com/docs/increment/data-models/model-intro/?utm_source=gnosis-chain&utm_medium=partner-docs) - build analytics in 3 clicks diff --git a/docs/tools/oracles/api3.md b/docs/tools/Oracle Providers/api3.md similarity index 100% rename from docs/tools/oracles/api3.md rename to docs/tools/Oracle Providers/api3.md diff --git a/docs/tools/oracles/chainlink.md b/docs/tools/Oracle Providers/chainlink.md similarity index 100% rename from docs/tools/oracles/chainlink.md rename to docs/tools/Oracle Providers/chainlink.md diff --git a/docs/tools/oracles/gas-price.md b/docs/tools/Oracle Providers/gas-price.md similarity index 100% rename from docs/tools/oracles/gas-price.md rename to docs/tools/Oracle Providers/gas-price.md diff --git a/docs/tools/oracles/supraoracles/README.md b/docs/tools/Oracle Providers/supraoracles/README.md similarity index 100% rename from docs/tools/oracles/supraoracles/README.md rename to docs/tools/Oracle Providers/supraoracles/README.md diff --git a/docs/tools/oracles/supraoracles/vrf.md b/docs/tools/Oracle Providers/supraoracles/vrf.md similarity index 100% rename from docs/tools/oracles/supraoracles/vrf.md rename to docs/tools/Oracle Providers/supraoracles/vrf.md diff --git a/docs/tools/oracles/tellor.md b/docs/tools/Oracle Providers/tellor.md similarity index 100% rename from docs/tools/oracles/tellor.md rename to docs/tools/Oracle Providers/tellor.md diff --git a/docusaurus.config.js b/docusaurus.config.js index 04b3a777..fb629d98 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -268,7 +268,6 @@ const config = { to: "/about/communication", from: "/developers/communication" } - ], }, ], diff --git a/static/img/bridges/bridge-erc20-new.png b/static/img/bridges/bridge-erc20-new.png new file mode 100644 index 00000000..f5bf123f Binary files /dev/null and b/static/img/bridges/bridge-erc20-new.png differ diff --git a/static/img/bridges/bridge-explorer/bridge-configuration-new.png b/static/img/bridges/bridge-explorer/bridge-configuration-new.png new file mode 100644 index 00000000..866bf243 Binary files /dev/null and b/static/img/bridges/bridge-explorer/bridge-configuration-new.png differ diff --git a/static/img/bridges/bridge-explorer/bridge-info-new.png b/static/img/bridges/bridge-explorer/bridge-info-new.png new file mode 100644 index 00000000..d7128d4a Binary files /dev/null and b/static/img/bridges/bridge-explorer/bridge-info-new.png differ diff --git a/static/img/bridges/bridge-explorer/claim-new.png b/static/img/bridges/bridge-explorer/claim-new.png new file mode 100644 index 00000000..8a724df2 Binary files /dev/null and b/static/img/bridges/bridge-explorer/claim-new.png differ diff --git a/static/img/bridges/bridge-explorer/claim-tx-page.png b/static/img/bridges/bridge-explorer/claim-tx-page.png new file mode 100644 index 00000000..292ac980 Binary files /dev/null and b/static/img/bridges/bridge-explorer/claim-tx-page.png differ diff --git a/static/img/bridges/bridge-explorer/search-new-tx.png b/static/img/bridges/bridge-explorer/search-new-tx.png new file mode 100644 index 00000000..d42e1764 Binary files /dev/null and b/static/img/bridges/bridge-explorer/search-new-tx.png differ diff --git a/static/img/bridges/bridge-explorer/transaction-history.png b/static/img/bridges/bridge-explorer/transaction-history.png new file mode 100644 index 00000000..63c9e639 Binary files /dev/null and b/static/img/bridges/bridge-explorer/transaction-history.png differ diff --git a/static/img/bridges/bridge-explorer/validator-status-new.png b/static/img/bridges/bridge-explorer/validator-status-new.png new file mode 100644 index 00000000..6593e8be Binary files /dev/null and b/static/img/bridges/bridge-explorer/validator-status-new.png differ diff --git a/static/img/bridges/bridge-xdai-new.png b/static/img/bridges/bridge-xdai-new.png new file mode 100644 index 00000000..d38984b6 Binary files /dev/null and b/static/img/bridges/bridge-xdai-new.png differ diff --git a/updates/2024/03-27-core-devs-call.md b/updates/2024/03-27-core-devs-call.md new file mode 100644 index 00000000..2a0c70d1 --- /dev/null +++ b/updates/2024/03-27-core-devs-call.md @@ -0,0 +1,93 @@ +--- +title: Core Devs Call - 2024/03/27 +authors: [dapplion, armaganercan, filoozom] +tags: [CoreDevsCall, gnosis] +--- + +# Gnosis Core Devs Call Notes + +Welcome to the Gnosis Core Devs weekly gathering. Every Wednesday, key members from the Gnosis team, contributors, and various team representatives convene to discuss, collaborate, and update one another on the Gnosis ecosystem's progression. + +Participants represent teams: + +Erigon, Gateway, Nethermind, Geth, Gnosis DevOps, Gnosis Core Devs, Gnosis Comms team. + +With a diverse set of voices present, our discussions are rich, multifaceted, and aim to foster innovation within the community. + +Missed the meeting? Catch the [full recording on Gnosis Chain YouTube channel.](https://www.youtube.com/watch?v=PwyrwA0DBDQ) + +March 27, 2024 + +# Client Team Updates +## EL + +* **Nethermind**: + * Planning on releasing half-path + * Still a few weeks away + * Will have around half the speed of geth for serving snap sync + + +* **Erigon**: + * Small release today with fixes for Caplin (2.59.1) + +* **Geth**: + * Was able to go all the way to Dencun + * Will have to rebase now for Dencun support + + +# Chain Infra + +* **Gateway** + * The eth_getLogs service unavailable error happens on the public RPC when the servers are overloaded + * With an API key that doesn’t happen + +# Hive Tests + +* No updates + +# Innovation + +* Shutter + * Managed to fix the threading issue + * The validator is able to run but can’t produce blocks yet because there’s an issue with passing the decryption keys + * Might be the protobuf implementation + * Once this is done, block production should work + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/updates/2024/04-10-core-devs-call.md b/updates/2024/04-10-core-devs-call.md new file mode 100644 index 00000000..8fd06420 --- /dev/null +++ b/updates/2024/04-10-core-devs-call.md @@ -0,0 +1,97 @@ +--- +title: Core Devs Call - 2024/04/10 +authors: [dapplion, armaganercan, filoozom] +tags: [CoreDevsCall, Gnosis Chain] +--- + +# Gnosis Core Devs Call Notes + +Welcome to the Gnosis Core Devs weekly gathering. Every Wednesday, key members from the Gnosis team, contributors, and various team representatives convene to discuss, collaborate, and update one another on the Gnosis ecosystem's progression. + +Participants represent teams: + +Erigon, Gateway, Nethermind, Geth, Gnosis DevOps, Gnosis Core Devs, Gnosis Comms team. + +With a diverse set of voices present, our discussions are rich, multifaceted, and aim to foster innovation within the community. + +Missed the meeting? Catch the [full recording on Gnosis Chain YouTube channel.](https://youtu.be/b6OEAy3mccg) + +April 10, 2024 + +# Client Team Updates +## EL + +* **Nethermind**: + * Nothing new + * Working on Pectra and half-path / snap sync server + +* **Erigon**: + * Working on Pectra and Erigon 3 + +* **Geth**: + * Issue when the first blob was included in a block + * Currently less than 2 weeks behind head + * Then will test snap sync with a new geth node + +# Chain Infra + +* **Gateway** + * No updates + +# Innovation + +* Shutter + * The first Shutter transaction was included! + * Transaction submitted to sequencer contract and included in a block + * However, keypers are mocked for now, so the keys are hard coded + * Because the keypers are still using the BN curve rather than BLS + * Will require some changes from Shutter and then some testing + * No ETA yet + * The libp2p issue hasn’t been resolved yet, so the connection breaks after around half a hour + +* Verkle Tree Integration + * Gnosis Chain has less time per block to do the transition + * What’s the upper bound for time we can take to do the transition? + * One issue is that snap sync is not entirely figured out for the transition yet, so syncing could be a bit more difficult (but at most nodes would have to sync 2 months worth of blocks, which on Gnosis Chain is not that huge of an issue, and it likely doesn’t change anything for Erigon at least) + * Ethereum is targeting 2 weeks, on Gnosis Chain with identical parameters it would take 4x longer, so 2 months (mental math, to be checked) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +