I would like to know what helps the network the most and/or what doesn't make any difference:
- nis running
- ncc running
- wallet opened
- node booted (and it says "booting NIS" in the headline…?)
- harvesting
- port opened
Can somebody clear that up for me?
I would like to know what helps the network the most and/or what doesn't make any difference:
- nis running
- ncc running
- wallet opened
- node booted (and it says "booting NIS" in the headline...?)
- harvesting
- port opened
Can somebody clear that up for me?
To support the network you need to have NIS running, booted and port opened.
Why you need to have NIS running should be obvious :)
NIS can't be part of the network without being booted. A NIS that isn't booted might as well run on a device that isn't connected to the Internet.
The port needs to be open so the rest of the network can connect with you. If the port is closed you will be able to get all information from the network but the network won't be able to connect to you which means your node appears inactive to the network. I think you yould still harvest since that is something that is actively pushed but noone could pull from you.
Harvesting is necessary to produce blocks. Why that is important i think is also obvious :)
Ok, but to boot NIS, I have to run NCC, open the wallet and boot the node (actually NIS!?) via the popup dialog. After I did that, can I close the wallet and close NCC?
Ok, but to boot NIS, I have to run NCC, open the wallet and boot the node (actually NIS!?) via the popup dialog. After I did that, can I close the wallet and close NCC?
Yes. And you can configure NIS to auto-boot so you don't need NCC everytime you restart NIS.
Ok, but to boot NIS, I have to run NCC, open the wallet and boot the node (actually NIS!?) via the popup dialog. After I did that, can I close the wallet and close NCC?
Yes. And you can configure NIS to auto-boot so you don't need NCC everytime you restart NIS.
Via web interface -> settings -> auto-boot?
There is a checkbox:
[] Auto boot when a wallet is opened
How can I set it up to auto-boot without NCC/opening a wallet?
Ok, but to boot NIS, I have to run NCC, open the wallet and boot the node (actually NIS!?) via the popup dialog. After I did that, can I close the wallet and close NCC?
Yes. And you can configure NIS to auto-boot so you don't need NCC everytime you restart NIS.
Via web interface -> settings -> auto-boot?
There is a checkbox:[] Auto boot when a wallet is opened
How can I set it up to auto-boot without NCC/opening a wallet?
I think that text is simply misleading. AFAIK once you've set it to autoboot it will auto-boot without ncc every running. Maybe the text was supposed to say once a wallet is created or something like that.
Ok, but to boot NIS, I have to run NCC, open the wallet and boot the node (actually NIS!?) via the popup dialog. After I did that, can I close the wallet and close NCC?
Yes. And you can configure NIS to auto-boot so you don't need NCC everytime you restart NIS.
Via web interface -> settings -> auto-boot?
There is a checkbox:[] Auto boot when a wallet is opened
How can I set it up to auto-boot without NCC/opening a wallet?
I think that text is simply misleading. AFAIK once you've set it to autoboot it will auto-boot without ncc every running. Maybe the text was supposed to say once a wallet is created or something like that.
Even if this is true (can a dev confirm?) a "auto-harvest" option would be needed, too.
Auto-booting without NCC is only possible when running the standalone version.
Auto-harvest is not yet implemented.
Auto-booting without NCC is only possible when running the standalone version.
...
Rly ? Should probably be changed if possible, or added as entrie in the tray menu
I think patmast3r is right.
And two more questions:
- What is the best way to check if NIS is booted if NCC is not opened (and is not wanted to be started)?
- What actually happens when booting NIS (or should I say booting node?)?
Auto-booting without NCC is only possible when running the standalone version.
...
Rly ? Should probably be changed if possible, or added as entrie in the tray menu
With what private key could NIS be booted without NCC?
With what private key is NIS booting without NCC while running the standalone version?
And two more questions:
- What is the best way to check if NIS is booted if NCC is not opened (and is not wanted to be started)?
- What actually happens when booting NIS (or should I say booting node?)?
1) Not sure how you want to check it.
Manually? --> look at monitor icon.
Automatically via a script? check the status of both via http://127.0.0.1:8989/ncc/api/status for NCC and http://127.0.0.1:7890/status for NIS.
Possible return codes:
/**
* Unknown status.
*/
UNKNOWN(0),
/**
* NIS/NCC is stopped.
*/
STOPPED(1),
/**
* NIS/NCC is starting.
*/
STARTING(2),
/**
* NIS/NCC is running.
*/
RUNNING(3),
/**
* Local node is booting (implies RUNNING).
*/
BOOTING(4),
/**
* Local node is booted (implies RUNNING).
*/
BOOTED(5),
/**
* NIS local node is synchronized (implies RUNNING and BOOTED)
*/
SYNCHRONIZED(6);
2) During boot the internal network objects are created and the network is scanned for active nodes. Since the timeout is 60 seconds this can (and usually will) take 60 seconds.
With what private key is NIS booting without NCC while running the standalone version?
With the one specified in config.properties, entry nis.bootKey.
Thank you for explaning how to check the NIS status.
@auto-boot:
Ok, so you don't really want to implement an auto-boot for "normal" users which use the NEM monitor but only for the more experienced users who run the standalone version?
That is probably reasonable because storing a private key unencrypted is pretty dangerous.
Thank you for explaning how to check the NIS status.
@auto-boot:
Ok, so you don't really want to implement an auto-boot for "normal" users which use the NEM monitor but only for the more experienced users who run the standalone version?
That is probably reasonable because storing a private key unencrypted is pretty dangerous.
We expect "normal" users to use NCC. And, with default settings, NIS will be automatically booted by logging into a wallet.
Yes, makes sense. Thanks 