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.

Sign up for GitHub

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

chore: 4844 fallback disclaimer && added testnet rollup creators for Arbitrum #39

Merged
merged 3 commits into from
Dec 20, 2024
Merged

chore: 4844 fallback disclaimer && added testnet rollup creators for Arbitrum #39

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d8c066d
chore: 4844 fallback disclaimer && added testnet rollup creators for …
epociask Dec 12, 2024
7a93562
Merge branch 'master' of github.com:Layr-Labs/eigenda-docs into epoci…
epociask Dec 15, 2024
70eacc3
chore: Update tables with mainnet creators
epociask Dec 19, 2024
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
15 changes: 15 additions & 0 deletions docs/integrations-guides/rollup-guides/orbit/deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,21 @@ yarn hardhat run scripts/local-deployment/deployCreator.ts

The script will take a few minutes to complete as it prints out the addresses of the deployed contracts along the way. Lastly, the script will write the deployed contracts to the `CREATOR_DEPLOYMENT_INFO` file you specified. Upon completion, your rollup creator factory is ready to use to deploy new chains.

## How to deploy a Rollup using our Rollup Creators
We support rollup creators using EigenDA contracts on the following networks:

| version | network | address |
|---------|---------|---------|
| v2.1.0 | Ethereum Mainnet | [0xAf5F13b5aB7a5da24f8b2808a032296Ef3476AF6](https://etherscan.io/address/0xAf5F13b5aB7a5da24f8b2808a032296Ef3476AF6#code) |
| v2.1.0 | Ethereum Holesky | [0x4449adCcad953ce8feB2FD50707B17f876bBDEf4](https://holesky.etherscan.io/address/0x4449adCcad953ce8feB2FD50707B17f876bBDEf4#code) |
| v2.1.0 | Arbitrum Mainnet | [0x8c83b9c670E90A4fAbf19E6fCb267caf12644a87](https://arbiscan.io/address/0x8c83b9c670E90A4fAbf19E6fCb267caf12644a87#code) |
| v2.1.0 | Arbitrum Sepolia | [0x4264420318Ba09C29dbbe402b3f16Ee13903a031](https://sepolia.arbiscan.io/address/0x4264420318Ba09C29dbbe402b3f16Ee13903a031#code) |
| v2.1.0 | Base Mainnet | [0xaFa98453F1f3B1Ea7629e67621a29B7Be4AC225A](https://basescan.org/address/0xafa98453f1f3b1ea7629e67621a29b7be4ac225a#code) |


### Deploy using our hosted Rollup Creators
The Orbit [documentation](https://docs.arbitrum.io/launch-orbit-chain/how-tos/orbit-sdk-deploying-rollup-chain) provides a comprehensive overview for how one can trigger new chain deployments using already deployed rollup creators. If you'd like to leverage the orbit-sdk please use our fork [here](https://github.com/Layr-Labs/eigenda-orbit-sdk).

## How to deploy a Rollup on Testnet using our UI

While you can interact with the deployed Rollup creator directly, we recommend using our [orbit chain deployment portal](https://orbit.eigenda.xyz/) to deploy a rollup for a friendlier devx and easy-to-use configs. Currently, the only supported testnets are:
Expand Down
7 changes: 7 additions & 0 deletions docs/integrations-guides/rollup-guides/orbit/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,6 +70,13 @@ To remove a trust assumption on the liveness of EigenDA for the liveness of the
}
```

**NOTE:** 4844 failover is implemented and audited but untested via E2E system tests since there are no existing tests in vanilla Arbitrum that programmatically assert the end-to-end correctness of 4844. Please use at your own risk, if you'd like to disable 4844 in-favor of calldata DA, add the following field to your `dangerous` sub-config via node config:
```
"dangerous": {
"disable-blob-reader": true,
},
```

To learn more about our Arbitrum failover design methodology, please advise the following [spec](https://hackmd.io/@epociask/SJUyIZlZkx).

# Diff Overview
Expand Down