From b5ab1b12d2e815a0e39da486cd21bc35efe5f5a3 Mon Sep 17 00:00:00 2001 From: Jason-Wanxt Date: Wed, 5 Jun 2024 12:03:56 +0800 Subject: [PATCH 1/3] update refer link to das docs --- .../data-availability-committees/01-get-started.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arbitrum-docs/run-arbitrum-node/data-availability-committees/01-get-started.md b/arbitrum-docs/run-arbitrum-node/data-availability-committees/01-get-started.md index 94cc6c771..b37d114b5 100644 --- a/arbitrum-docs/run-arbitrum-node/data-availability-committees/01-get-started.md +++ b/arbitrum-docs/run-arbitrum-node/data-availability-committees/01-get-started.md @@ -45,9 +45,9 @@ Here's a basic checklist of actions to complete for chain owners: - URL of the RPC endpoint - URL(s) of the REST(s) endpoint - Ensure that at least one DAS is running as an [archive DAS](/run-arbitrum-node/data-availability-committees/02-deploy-das.md#archive-da-servers) -- Generate the keyset and keyset hash with all the information from the servers (guide coming soon) +- Generate the keyset and keyset hash with all the information from the servers (see [Keyset generation](/launch-orbit-chain/concepts/anytrust-orbit-chain-keyset-generation)) - Craft the new configuration for the batch poster (guide coming soon) -- Craft the new configuration for your chain's nodes (guide coming soon) +- Craft the new configuration for your chain's nodes (see [run a full orbit node](https://docs.arbitrum.io/node-running/how-tos/running-an-orbit-node#3-anytrust-chains)) - Update the SequencerInbox contract (guide coming soon) ## Ask for help From 6f4dd6af76228314f027df39ffd30562e518a21d Mon Sep 17 00:00:00 2001 From: Jason-Wanxt Date: Wed, 5 Jun 2024 12:20:03 +0800 Subject: [PATCH 2/3] add orbit sdk refer to keyset docs --- .../concepts/anytrust-orbit-chain-keyset-generation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arbitrum-docs/launch-orbit-chain/concepts/anytrust-orbit-chain-keyset-generation.md b/arbitrum-docs/launch-orbit-chain/concepts/anytrust-orbit-chain-keyset-generation.md index 1fa741d82..bbfac3f96 100644 --- a/arbitrum-docs/launch-orbit-chain/concepts/anytrust-orbit-chain-keyset-generation.md +++ b/arbitrum-docs/launch-orbit-chain/concepts/anytrust-orbit-chain-keyset-generation.md @@ -89,7 +89,7 @@ KeysetHash: 0x4d795e20d33eea0b070600e4e100c512a750562bf03c300c99444bd5af92d9b0 Upon successfully generating the Keyset, it is essential to establish it within the parent chain. This step ensures that the parent chain is accurately informed of the Committee members' keyset. -The Keyset can be configured by invoking the [setValidKeyset](https://github.com/OffchainLabs/nitro-contracts/blob/acb0ef919cce9f41da531f8dab1b0b31d9860dcb/src/bridge/SequencerInbox.sol#L466) method within the SequencerInbox contract. +The Keyset can be configured by invoking the [setValidKeyset](https://github.com/OffchainLabs/nitro-contracts/blob/acb0ef919cce9f41da531f8dab1b0b31d9860dcb/src/bridge/SequencerInbox.sol#L466) method within the SequencerInbox contract, you can also use orbit sdk to set it, see [set-valid-keyset example](https://github.com/OffchainLabs/arbitrum-orbit-sdk/tree/main/examples/set-valid-keyset). **Note:** Only rollup owner(s) can call this method to set the new valid keyset. From fb8b776e62cfc317fe7208ef3effb44db0b26f52 Mon Sep 17 00:00:00 2001 From: Jason-Wanxt Date: Wed, 5 Jun 2024 12:25:39 +0800 Subject: [PATCH 3/3] reset --- .../data-availability-committees/01-get-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arbitrum-docs/run-arbitrum-node/data-availability-committees/01-get-started.md b/arbitrum-docs/run-arbitrum-node/data-availability-committees/01-get-started.md index b37d114b5..2e9a2ec3f 100644 --- a/arbitrum-docs/run-arbitrum-node/data-availability-committees/01-get-started.md +++ b/arbitrum-docs/run-arbitrum-node/data-availability-committees/01-get-started.md @@ -47,7 +47,7 @@ Here's a basic checklist of actions to complete for chain owners: - Ensure that at least one DAS is running as an [archive DAS](/run-arbitrum-node/data-availability-committees/02-deploy-das.md#archive-da-servers) - Generate the keyset and keyset hash with all the information from the servers (see [Keyset generation](/launch-orbit-chain/concepts/anytrust-orbit-chain-keyset-generation)) - Craft the new configuration for the batch poster (guide coming soon) -- Craft the new configuration for your chain's nodes (see [run a full orbit node](https://docs.arbitrum.io/node-running/how-tos/running-an-orbit-node#3-anytrust-chains)) +- Craft the new configuration for your chain's nodes (guide coming soon) - Update the SequencerInbox contract (guide coming soon) ## Ask for help