-
Notifications
You must be signed in to change notification settings - Fork 795
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
Establishing a private network #975
Comments
Hi there, did you achieved creating a private network? I'm working on that but I can't get confirmed the blocks. |
See also #1099 -- which is similar, but not the same. |
Hi! Yes I was able to do it eventually. I first tried using docker-compose but it was not very efficient, because of the nature of the containers thus created: a nano-node is not exactly 100% active all time, there might be a few milliseconds where it just stops working to resume right after, however, docker-compose containers die the moment there's nothing running on them, which makes it not very practical. I had the chance of having a few VMs at my disposal, which I used right after, creating a node on each one of them (they were already connected physically, which helped me a lot, and I only had to connect them nano-wise). I configured the config.json file, adding the ip addresses of each node to others' config files, in the key "preconfigured peers". To verify this, I issued an RPC command to each node asking for its online peers, and it gave me all the rest (sometimes it gives only a few or none, but then connects to them). Maybe your nodes do not "see" each other and thus cannot send the money. |
@LotfiKobrosly Glad to hear you got it working. Closing out as complete. |
Is there a way to establish a private network (by changing the config.json file for example) in order to make tests on it? It is to stress test it and verify some of its prowesses offline, research purposes.
Thank you very much!
The text was updated successfully, but these errors were encountered: