The cli app's "command line" currently might say something like (test) Block:1896036 (type 'help') >> without noting that lightwalletd's cache block height is less than that, although when the cli begins, it will make a message like Server's latest block(316583) is behind ours(1897022). I think this last type of message should be repeated on the "command line" within the app.
Also, currently, this error message is issued in the cli when a wallet has TAZ and cannot send due to an incomplete cache in lightwalletd:
"error": "Insufficient verified funds. Have 0 zats, need 1163 zats. NOTE: funds need at least 1 confirmations before they can be spent."
This message could be possibly improved to point to lightwalletd's caching as the block to spending, or even offer live statistics on this process.
even when the sync seems to be in progress. The sync command offers the helpful:
Server's latest block(803573) is behind ours(1897022), just like when the application is started.
The cli app's "command line" currently might say something like
(test) Block:1896036 (type 'help') >>
without noting thatlightwalletd
's cache block height is less than that, although when the cli begins, it will make a message likeServer's latest block(316583) is behind ours(1897022)
. I think this last type of message should be repeated on the "command line" within the app.Also, currently, this error message is issued in the cli when a wallet has TAZ and cannot send due to an incomplete cache in
lightwalletd
:"error": "Insufficient verified funds. Have 0 zats, need 1163 zats. NOTE: funds need at least 1 confirmations before they can be spent."
This message could be possibly improved to point tolightwalletd
's caching as the block to spending, or even offer live statistics on this process.Finally, locally, the app's
syncstatus
returns:even when the sync seems to be in progress. The
sync
command offers the helpful:Server's latest block(803573) is behind ours(1897022)
, just like when the application is started.From working with #50