Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft Orbit Keyset and Config #684

Closed
wants to merge 1 commit into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added arbitrum-docs/assets/Arbitrum_bridge_orbit .png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
Deploying an Orbit Chain on Mainnet has many risks. These instructions will do its best at guiding you through the process, however there are additional risks.

These instructions serve as a resource and do not gurantee secure deployment.

After deploying an Orbit Testnet chain, you can deploy an Orbit Mainnet Chain now as Contracts have been audited on mainnet and are production ready

This tutorial shows you to do the following on Mainnet:
Create an Orbit Mainnet Chain
Prerequisites
- Public RPC
PLACEHOLDER for guidance for running backend (minimal helm chart guidance, etc.)
PLACEHOLDER FOR guidance for validators and members of the Data Availability Committee (DAC) to run required infrastructure and reasonable support in connection with the same


We've listed below a few options for infrastructure to get ready for mainnet

Block Explorer Options

RPC Infrastructure Providers

Fast Bridging Provider

Rollup as a Service Providers

Data Availability Layers

Subgraph Providrs
Loading