From 7b84e5e95dd7b972074694ba703e12ee02ee214d Mon Sep 17 00:00:00 2001 From: Joshua Colvin Date: Thu, 25 Aug 2022 11:39:09 -0700 Subject: [PATCH] Add `--node.chain-id` option to relay --- docs/Running_Node.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/Running_Node.md b/docs/Running_Node.md index fa68fafa1f..b945e112be 100644 --- a/docs/Running_Node.md +++ b/docs/Running_Node.md @@ -28,11 +28,11 @@ Note: If you’re interested in accessing the Arbitrum network but you don’t w - When running docker image, an external volume should be mounted to persist the database across restarts. The mount point should be `/home/user/.arbitrum/mainnet` or `/home/user/.arbitrum/rinkeby` depending on what chain you are connecting to. - Here is an example of how to run arb-node for mainnet: ``` - docker run --rm -it -v /some/local/dir/arbitrum-mainnet/:/home/user/.arbitrum/mainnet -p 0.0.0.0:8547:8547 -p 0.0.0.0:8548:8548 offchainlabs/arb-node:v1.4.3-3485354 --l1.url https://l1-node:8545 + docker run --rm -it -v /some/local/dir/arbitrum-mainnet/:/home/user/.arbitrum/mainnet -p 0.0.0.0:8547:8547 -p 0.0.0.0:8548:8548 offchainlabs/arb-node:v1.4.3-3485354 --l1.url=https://l1-node:8545 ``` - Here is an example of how to run arb-node for rinkeby (only good for archive requests on pre-Nitro blocks, so probably want to enable archive as well): ``` - docker run --rm -it -v /some/local/dir/arbitrum-rinkeby/:/home/user/.arbitrum/rinkeby -p 0.0.0.0:8547:8547 -p 0.0.0.0:8548:8548 offchainlabs/arb-node:v1.4.3-3485354 --l1.url https://l1-rinkeby-node:8545 + docker run --rm -it -v /some/local/dir/arbitrum-rinkeby/:/home/user/.arbitrum/rinkeby -p 0.0.0.0:8547:8547 -p 0.0.0.0:8548:8548 offchainlabs/arb-node:v1.4.3-3485354 --l1.url=https://l1-rinkeby-node:8545 ``` ### Note on permissions @@ -80,9 +80,9 @@ Note: If you’re interested in accessing the Arbitrum network but you don’t w - Note that rinkeby testnet has been upgraded to Nitro, so rinkeby feed messages cannot be parsed by the classic node and classic relay is not required. - Here is an example of how to run arb-relay for mainnet: ``` - docker run --rm -it -v /some/local/dir/arbitrum-mainnet/:/home/user/.arbitrum/mainnet -p 0.0.0.0:9642:9642 --entrypoint /home/user/go/bin/arb-relay offchainlabs/arb-node:v1.4.3-3485354 --feed.input.url wss://arb1.arbitrum.io/feed + docker run --rm -it -v /some/local/dir/arbitrum-mainnet/:/home/user/.arbitrum/mainnet -p 0.0.0.0:9642:9642 --entrypoint /home/user/go/bin/arb-relay offchainlabs/arb-node:v1.4.3-3485354 --feed.input.url=wss://arb1.arbitrum.io/feed --node.chain-id=42161 ``` - Here is an example of how to run arb-node for mainnet with custom relay: ``` - docker run --rm -it -v /some/local/dir/arbitrum-mainnet/:/home/user/.arbitrum/mainnet -p 0.0.0.0:8547:8547 -p 0.0.0.0:8548:8548 offchainlabs/arb-node:v1.4.3-3485354 --l1.url https://l1-node:8545 --feed.input.url ws://local-relay-address:9642 + docker run --rm -it -v /some/local/dir/arbitrum-mainnet/:/home/user/.arbitrum/mainnet -p 0.0.0.0:8547:8547 -p 0.0.0.0:8548:8548 offchainlabs/arb-node:v1.4.3-3485354 --l1.url=https://l1-node:8545 --feed.input.url=ws://local-relay-address:9642 ```