-
Notifications
You must be signed in to change notification settings - Fork 241
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
Multiple internal nodes #1165
Multiple internal nodes #1165
Conversation
LGTM but as long as we can't practically test that with e.g. testnet, signet or elements, this is imho not practical to merge. Maybe convert to draft? |
Is it possible to mark as draft after creating the PR? Can't find out how... |
@k9ert added a test for this now |
@@ -137,6 +137,8 @@ def add_node( | |||
def add_internal_node( | |||
self, | |||
name, | |||
network="mainnet", |
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.
Why not "main"
? Looks like we have now main and mainnet that are basically the same.
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.
Changed
Allows setting up multiple internal nodes with different networks.
Currently, this will work only for one node per network, since the port will be already occupied, but the architecture already supports running multiple nodes of the same network on different ports, which is one of the 2 missing pieces we need in order to allow Quicksync option to have a background full sync (the second piece needed is way to migrate wallets between nodes).