Feature: User Feedback for not synced nodes and DBs

One of the main reasons specter doesn't show the correct amounts is a not-synced node. For Spectrum, this might also be the case but there is another reason on top: Spectrum just booted up and connected to the electrum server but have not yet sunscribed to all the scripthashes it needs to. A scripthash is basically an address and this looks like this in the log:

[2023-01-23 12:07:39,618] INFO in spectrum: Now subscribed to 2900 scripthashes
[2023-01-23 12:07:44,015] INFO in spectrum: Now subscribed to 3000 scripthashes
[2023-01-23 12:07:49,189] INFO in spectrum: Now subscribed to 3100 scripthashes
[2023-01-23 12:07:53,949] INFO in spectrum: Now subscribed to 3200 scripthashes
...

Potentially, this could be shown as a percentage in the logs as the potential scripthashes are all in the DB. Simplified code from spectrum.py sync-method:

        for sc in Script.query.all():
            # ignore external scripts (labeled recepients)
            if sc.index is None:
                continue
            subscription_logging_counter += 1
            if subscription_logging_counter % 100 == 0:
                logger.info(
                    f"Now subscribed to {subscription_logging_counter} scripthashes"
                )
            res = self.sock.call("blockchain.scripthash.subscribe", [sc.scripthash])
            if res != sc.state:
                self.sync_script(sc, res)

So unless this loop is finished, specter might be outdated. This should clearly be reflexted in the UI. The current way of showing that looks like this: If you click on the node, you get some details of that node which currently looks like this: This is not optimal. I think it could be shown how much blocks are still too sync but both of the screenshots don't show that.

Anyway, this is about spectrum. Here, we don't have the warning, but you can only see the blockcount of the electrum-server:

So in order to give better feedback:

We need a warning if the underlying timechain is not in sync OR spectrum has not yet finished subscribing to all Scripthashes
Also some better statistics on that page would be good. E.g. Number of (synced-) scripthashes, wallets, Utxos, Txs and Descriptors

So how should that be implemented? I would suggest the following:

Change the loop above to calculate percentages on top of absolute numbers
The warning-sign is based on the result of initialblockdownload
This is not properly implemented in [spectrum)(https://github.com/cryptoadvance/spectrum/blob/master/src/cryptoadvance/spectrum/spectrum.py#L383). I hope that electrum has a way to figure it out. Can't imagine that this is not obtainable via electrum.
As the effect on a spectrum not being DB-synced is the exact same than a Core being in initialblockdownload=True, i'd suggest that we implement it so that spectrum is not giving back false until the DB-sync is completed as well.
However, it'd be beneficial to also know the exact sync status. For that, i'd suggest to create an own non-core-rpi-call getscripthashsyncinfo which returns the status (which can be set as an attribute on the spectrum-object while syncing and the rpc-call reads it from there).
This change might be a good opportunity to also refactor all the rpc-calls in three files (spectrum.py is way too long), like: core_rpc.py, wallet_rpc.py and spectrum_rpc.py (with getscripthashsyncinfo as the currently only call in there)
If this is done, it should be easy to call that info somewhere in the spectrum_info.jinja.

cryptoadvance / spectrum

Feature: User Feedback for not synced nodes and DBs #38