|
| 1 | +import { Callout } from 'nextra/components' |
| 2 | + |
1 | 3 | # Deploy Arbitrum Orbit with Avail DA
|
2 | 4 |
|
3 | 5 | ### Prerequisites
|
|
7 | 9 | 3. At least 1 ETH over Arbsepolia Testnet. You can follow [Step 1](https://docs.arbitrum.io/launch-orbit-chain/orbit-quickstart#step-1-acquire-arbitrum-testnet-eth-and-the-native-token-for-orbit-chains-with-custom-gas-tokens) on Arbitrum Orbit Doc for acquiring testnet $ETH
|
8 | 10 | 4. This guide will use [Arbitrum's ArbSepolia](https://docs.arbitrum.io/build-decentralized-apps/public-chains#arbitrum-sepolia) and [Avail's Turing](/docs/networks) testnets.
|
9 | 11 |
|
10 |
| -> This guide is based on [Arbitrum Orbit Quickstart](https://docs.arbitrum.io/launch-orbit-chain/orbit-quickstart) |
| 12 | +<Callout type="info"> |
| 13 | +This guide is based on [Arbitrum Orbit Quickstart](https://docs.arbitrum.io/launch-orbit-chain/orbit-quickstart) |
| 14 | +</Callout> |
11 | 15 |
|
12 |
| -## 1. Download avail nitro node docker image |
| 16 | +## Download avail nitro node docker image |
13 | 17 |
|
14 | 18 | ### Step-1: Download the [avail-nitro-node](https://hub.docker.com/repository/docker/availrishabh/avail-nitro-node-dev/tags) image from docker hub
|
15 | 19 |
|
|
18 | 22 | ```
|
19 | 23 |
|
20 | 24 |
|
21 |
| -## 2. Deploy Rollup Contracts |
| 25 | +## Deploy Rollup Contracts |
22 | 26 |
|
23 | 27 | ### Step-1: Download the [nitro-contract](https://github.com/availproject/nitro-contracts/tree/data-availability-verification-v2.3.1) with Avail DA
|
24 | 28 |
|
|
93 | 97 | | Validators | Your chain's validators are responsible for validating the integrity of transactions and posting assertions of the current state of your Orbit chain to its base chain. Add the address in the list which you want to be added to an allow-list in your chain’s base contract |
|
94 | 98 | | Batch Poster | Your batch poster address is responsible for posting batches of transactions from your Orbit chain to its base contracts on its base chain. Added the address which you want to act as batch-poster for your orbit chain |
|
95 | 99 |
|
96 |
| - > When we say "base contracts" and "base chain", we're referring to your Orbit chain's L2 contracts and the L2 chain that they're deployed to, respectively. We'll use these terms throughout the rest of this guide. |
| 100 | +<Callout type="info"> |
| 101 | +When we say "base contracts" and "base chain", we're referring to your Orbit chain's L2 contracts and the L2 chain that they're deployed to, respectively. We'll use these terms throughout the rest of this guide. |
| 102 | +</Callout> |
97 | 103 |
|
98 | 104 |
|
99 | 105 | ### Step-4: Deploy your chain's base contracts to Arbitrum Sepolia!
|
|
111 | 117 |
|
112 | 118 | Your Orbit chain's base contracts are responsible for facilitating the exchange of information between your chain's node(s) and its base chain's nodes. This includes the batch posting of transactions from your Orbit chain to its base chain, the staking of tokens by your Orbit chain's validators the challenge mechanism, bridging mechanisms, and more.
|
113 | 119 |
|
114 |
| -## 3. Spin up the chain using orbit-setup-script |
| 120 | +## Spin up the chain using orbit-setup-script |
115 | 121 |
|
116 | 122 | ### Step-1: Download [orbit-setup-script](https://github.com/OffchainLabs/orbit-setup-script.git)
|
117 | 123 |
|
@@ -198,18 +204,28 @@ Your Orbit chain's base contracts are responsible for facilitating the exchange
|
198 | 204 | }
|
199 | 205 |
|
200 | 206 | ```
|
201 |
| - Update these detailes based on your chain's configuration and base contract addresses |
202 |
| - - chain.chain-id |
203 |
| - - chain.chain-name |
204 |
| - - chain.InitialChainOwner |
205 |
| - - chain.chainId |
206 |
| - - chain.rollup |
207 |
| - - chain.name |
208 |
| - - node.batch-poster.parent-chain-wallet.private-key |
209 |
| - - node.staker.parent-chain-wallet.private-key |
210 |
| - - node.avail.seed |
211 |
| - - node.avail.app-id |
212 |
| - - node.avail.arbSepolia-rpc |
| 207 | +
|
| 208 | +<Callout type="info"> |
| 209 | + Make sure to update these params based on your chain's configuration and base contract addresses |
| 210 | +
|
| 211 | + <details className="border p-3 rounded-md bg-[#EFF6FF] border-[#] hover:!bg-[#EFF6FF]"> |
| 212 | + <summary> |
| 213 | + List of params to be configured |
| 214 | + </summary> |
| 215 | + - `chain.chain-id` |
| 216 | + - `chain.chain-name` |
| 217 | + - `chain.InitialChainOwner` |
| 218 | + - `chain.chainId` |
| 219 | + - `chain.rollup` |
| 220 | + - `chain.name` |
| 221 | + - `node.batch-poster.parent-chain-wallet.private-key` |
| 222 | + - `node.staker.parent-chain-wallet.private-key` |
| 223 | + - `node.avail.seed` |
| 224 | + - `node.avail.app-id` |
| 225 | + - `node.avail.arbSepolia-rpc` |
| 226 | +
|
| 227 | + </details> |
| 228 | +</Callout> |
213 | 229 |
|
214 | 230 | ### Step-3: Update `docker-compose` file of `orbit-setup-script`
|
215 | 231 |
|
|
0 commit comments