-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add three-node devnet-local
configuration
#940
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I appreciate the atomicity of this PR! I think I caught a few minor port mismatches but otherwise it looks okay to my eyes.
re: having issues with signing messages with this setup using the test-cli - just to confirm i was able to successfully register and sign using the test-cli. I just needed to add the line:
to So this is great! Although that doesn't explain why you had issues with accounts not being funded. (i tried with |
@ameba23 I could've sworn I added that to the I suspect my original problem stemmed from using the wrong port of Charlie in the config. For the record, here's the error I was running into during signing:
As for the the accounts not being funded, are you not getting any warnings about that in the TSS logs at startup? |
) I forgot to do this in #940.
This adds a third node to our
devnet-local
chainspec and adds that to our DockerCompose setup.
While the containers spin up correctly, I've ran into some issues around TSS accounts not
being funded properly and with signing not working on the test CLI. Since these issues
aren't exactly related to the Docker stuff I'm gonna dig into those in some different
PRs.
Closes #892.