You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During a spam attack or any problem with a Nano node it may lack behind in cemented blocks. That will cause problems for the wallet for example pending not showing up as they should. By displaying the cemented block count somewhere could be very useful in that scenario for troubleshooting because you can compare to a site like nanocrawler.cc or nanoticker.info to compare with other nodes. This is not for the normal user so it should be hidden by default or maybe only visible in the console log.
During a spam attack or any problem with a Nano node it may lack behind in cemented blocks. That will cause problems for the wallet for example pending not showing up as they should. By displaying the cemented block count somewhere could be very useful in that scenario for troubleshooting because you can compare to a site like nanocrawler.cc or nanoticker.info to compare with other nodes. This is not for the normal user so it should be hidden by default or maybe only visible in the console log.
It should update on each refresh calling https://docs.nano.org/commands/rpc-protocol/#block_count
And check for "cemented". I think it will require the server docker container to be updated to allow block_count command.
The text was updated successfully, but these errors were encountered: