https://github.com/layr-labs/eigenda-orbit-setup-script

https://github.com/layr-labs/eigenda-orbit-setup-script

Last synced: 2 months ago
JSON representation

• Host: GitHub
• URL: https://github.com/layr-labs/eigenda-orbit-setup-script
• Owner: Layr-Labs
• Created: 2024-08-15T16:24:46.000Z (5 months ago)
• Default Branch: main
• Last Pushed: 2024-10-11T05:29:20.000Z (3 months ago)
• Last Synced: 2024-10-18T23:28:25.532Z (3 months ago)
• Language: TypeScript
• Size: 1.73 MB
• Stars: 0
• Watchers: 3
• Forks: 2
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# orbit-setup-script

These scripts will help you fund newly generated batch-poster and validator addresses, configure an Orbit chain, and deploy bridge contracts on both L2 and L3 chains.

## Instructions

Once you’ve downloaded both config files from the [Orbit Deployment UI](https://orbit.arbitrum.io/), please follow the steps below to complete local deployment of your Orbit chain. For more details and step-by-step instructions, check out the [documentation](https://developer.arbitrum.io/launch-orbit-chain/orbit-quickstart).

1. Clone the https://github.com/OffchainLabs/orbit-setup-script repository, and run `yarn install`. Then, move both the `nodeConfig.json` and `orbitSetupScriptConfig.json` files into the `config` directory within the cloned repository

2. Launch Docker, and in the base directory, run `docker-compose up -d`. This will launch the node with a public RPC reachable at http://localhost:8449/  and a corresponding BlockScout explorer instance, viewable at http://localhost/

3. Then, add the private key for the wallet you used to deploy the rollup contracts earlier in the following command, and run it: `PRIVATE_KEY="YourPrivateKey" PARENT_CHAIN_RPC_URL="" ORBIT_RPC_URL="http://localhost:8449" yarn run setup`

4. The Orbit chain is now up. You can find all information about the newly deployed chain in the `outputInfo.json` file which is created in the main directory of script folder

5. Optionally, to track logs, run the following command within the base directory: `docker-compose logs -f nitro`