From b22c06560b524d82933a45519a982b4bf5852e48 Mon Sep 17 00:00:00 2001 From: Harry Kalodner Date: Tue, 11 Feb 2020 16:01:07 -0500 Subject: [PATCH 1/2] Update Rinkeby.md --- docs/Rinkeby.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/docs/Rinkeby.md b/docs/Rinkeby.md index 14c4f7bb07..5fe2eb4c1e 100644 --- a/docs/Rinkeby.md +++ b/docs/Rinkeby.md @@ -12,17 +12,18 @@ The deployment tool will assist you in configuring and launching your Rollup Cha ## Initializing the validators +Run the following command to initialize a set of validators for a given Rollup contract. The `contract_path` should be to the same file you submitted to the deployment tool, the `rollup_address` should be the address output by the tool after a successful deployment, and the `eth_url` should be a RPC or WebSocket connection to an Ethereum node. + +You can select to have one or more validators run on your machine for testing purposes. + ```bash -./scripts/initialize_validators.py [contract_path] [validator_count] +./scripts/initialize_validators.py [contract_path] [validator_count] [rollup_address] [eth_url] ``` -This command will initialize your rollup chain and create a `validator-states` folder with configuration -information for `validator_count` validators prepared to validator it. - -Note that this command executes the `setup_rollup.py` script and if you are not in the root of the `arbitrum` +Note that this command executes the `initialize_validators.py` script and if you are not in the root of the `arbitrum` directory, you may need to use a different path. -Running the `setup_rollup` command will perform two main tasks 1) Launch an Arbitrum Rollup chain on the local testnet 2) Create a `validator-states` folder. This folder contains pre-seeded wallets for the created validators. It serves as a lightweight simulation of an enviroment where the validators are running on multiple machines. +Running the `initialize_validators` command will create a `validator-states` folder with `validator_count` subfolders, each configured with a validator for the given Rollup contract.. It serves as a lightweight simulation of an enviroment where the validators are running on multiple machines. ## Deploying your validators From 6d4ae20d6dbc5dbc2bd140b88bfc4b10427c9dc7 Mon Sep 17 00:00:00 2001 From: Ed Felten Date: Tue, 11 Feb 2020 16:02:46 -0500 Subject: [PATCH 2/2] Typo fix --- docs/Rinkeby.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Rinkeby.md b/docs/Rinkeby.md index 5fe2eb4c1e..05abc07e7c 100644 --- a/docs/Rinkeby.md +++ b/docs/Rinkeby.md @@ -23,7 +23,7 @@ You can select to have one or more validators run on your machine for testing pu Note that this command executes the `initialize_validators.py` script and if you are not in the root of the `arbitrum` directory, you may need to use a different path. -Running the `initialize_validators` command will create a `validator-states` folder with `validator_count` subfolders, each configured with a validator for the given Rollup contract.. It serves as a lightweight simulation of an enviroment where the validators are running on multiple machines. +Running the `initialize_validators` command will create a `validator-states` folder with `validator_count` subfolders, each configured with a validator for the given Rollup contract. It serves as a lightweight simulation of an enviroment where the validators are running on multiple machines. ## Deploying your validators