While "last_error": null might suggest there is no problem, I think a more useful message would include a simple assertion of if a sync has been achieved from the application's perspective, such as "Zingo cli has been synced to the blockchain successfully!" or "Zingo cli is not successfully synced!".
This would likely involve some logic to read and interpret the JSON that is now offered to the end user.
Currently, running
syncstatus
in thecli
results with a JSON output, an example of which would be:While
"last_error": null
might suggest there is no problem, I think a more useful message would include a simple assertion of if a sync has been achieved from the application's perspective, such as"Zingo cli has been synced to the blockchain successfully!"
or"Zingo cli is not successfully synced!"
.This would likely involve some logic to read and interpret the JSON that is now offered to the end user.