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

TEMP: test multiple val-nodes #2268

Closed
wants to merge 1 commit into from
Closed

TEMP: test multiple val-nodes #2268

wants to merge 1 commit into from

Conversation

tsahee
Copy link
Contributor

@tsahee tsahee commented May 1, 2024

This PR can be used to test a multi-exec docker image

to test: Add this diff to nitro-testnode:

--- a/scripts/config.ts
+++ b/scripts/config.ts
@@ -214,12 +214,12 @@ function writeConfigs(argv: any) {
                     "wait-for-l1-finality": false
                 }
             },
-            "block-validator": {
-                "execution-server": {
-                    "url": argv.validationNodeUrl,
-                    "jwtsecret": valJwtSecret,
-                }
-            }
+            // "block-validator": {
+            //     "execution-server": {
+            //         "url": argv.validationNodeUrl,
+            //         "jwtsecret": valJwtSecret,
+            //     }
+            // }
         },
         "execution": {
             "sequencer": {
@@ -247,7 +247,7 @@ function writeConfigs(argv: any) {
         let simpleConfig = JSON.parse(baseConfJSON)
         simpleConfig.node.staker.enable = true
         simpleConfig.node.staker["use-smart-contract-wallet"] = true
-        simpleConfig.node.staker.dangerous["without-block-validator"] = true
+        //simpleConfig.node.staker.dangerous["without-block-validator"] = true
         simpleConfig.node.sequencer = true
         simpleConfig.node.dangerous["no-sequencer-coordinator"] = true
         simpleConfig.node["delayed-sequencer"].enable = true

And start testnode with: ./test-node.bash --init --dev nitro --detach --simple

We have here a separate val-node running "old" machines, and a separate one running "latest", both succeed to validate

@cla-bot cla-bot bot added the s Automatically added by the CLA bot if the creator of a PR is registered as having signed the CLA. label May 1, 2024
@tsahee tsahee force-pushed the multi-exec-test branch from 5ba6ddd to c01d2f8 Compare May 1, 2024 15:27
Base automatically changed from multi-exec-servers to master May 2, 2024 16:51
@tsahee
Copy link
Contributor Author

tsahee commented May 7, 2024

not needed now with the backward-compat docker

@tsahee tsahee closed this May 7, 2024
@tsahee tsahee deleted the multi-exec-test branch May 7, 2024 00:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
s Automatically added by the CLA bot if the creator of a PR is registered as having signed the CLA.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant