From f956a9ff79a1b85e6862d1837e627af72a72f3df Mon Sep 17 00:00:00 2001 From: GigaHierz <55887077+GigaHierz@users.noreply.github.com> Date: Thu, 22 Aug 2024 21:42:49 +0100 Subject: [PATCH] Update withdrawing-celo-from-dango-to-holesky-using-viem.mdx (#1439) - intro sentence - links to the viem OP Stack library - explanation of the `dango.js` file --- ...thdrawing-celo-from-dango-to-holesky-using-viem.mdx | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/cel2/bridging/withdrawing-celo-from-dango-to-holesky-using-viem.mdx b/docs/cel2/bridging/withdrawing-celo-from-dango-to-holesky-using-viem.mdx index 289548a796..6f1be61db1 100644 --- a/docs/cel2/bridging/withdrawing-celo-from-dango-to-holesky-using-viem.mdx +++ b/docs/cel2/bridging/withdrawing-celo-from-dango-to-holesky-using-viem.mdx @@ -5,11 +5,15 @@ title: Withdrawing Celo from Dango to Holesky using Viem import Tabs from "@theme/Tabs"; import TabItem from "@theme/TabItem"; +In this tutorial, you will learn how to programmatically withdraw CELO from Dango to Holskey using the [viem OP Stack](https://viem.sh/op-stack). + Withdrawals require the user to submit three transactions: -1. Withdrawal initiating transaction, which the user submits on L2. -2. Withdrawal proving transaction, which the user submits on L1 to prove that the withdrawal is legitimate. -3. Withdrawal finalizing transaction, which the user submits on L1 after the fault challenge period has passed, to actually run the transaction on L1. +1. [Withdrawal initiating a transaction](https://viem.sh/op-stack/actions/initiateWithdrawal), which the user submits on L2. +2. [Withdrawal proving transaction](https://viem.sh/op-stack/actions/proveWithdrawal), which the user submits on L1 to prove that the withdrawal is legitimate. +3. [Withdrawal finalizing transaction](https://viem.sh/op-stack/actions/finalizeWithdrawal), which the user submits on L1 after the fault challenge period has passed, to actually run the transaction on L1. + +As you can see, we’ve created a `dango.js` file that contains all the necessary data for interacting with the test network. Since Dango will be a short-lived testnet, chain data won’t be available through viem or wagmi, so this file ensures you have everything you need directly at hand.