but yeah..its testnet, and network currently on the testnet is unstable
(there are reasons, bootstrap nodes being overloaded, faulty workarounds causing further commotion, forks, etc)
its because your local node running with Daedalus gets stuck (stops receiving updates) while the blockchain continues further. Usually closing and starting makes you bootstrap to newer state again
If you mean on the loading screen for Daedalus? This would be because of an issue with connecting to the node.
While you're trying to connect, but not successfully syncing, more blocks are being created on the blockchain and therefore you have more blocks to sync with, so the percentage of completed sync goes down.
but yeah..its testnet, and network currently on the testnet is unstable (there are reasons, bootstrap nodes being overloaded, faulty workarounds causing further commotion, forks, etc)
its because your local node running with Daedalus gets stuck (stops receiving updates) while the blockchain continues further. Usually closing and starting makes you bootstrap to newer state again
If you mean on the loading screen for Daedalus? This would be because of an issue with connecting to the node. While you're trying to connect, but not successfully syncing, more blocks are being created on the blockchain and therefore you have more blocks to sync with, so the percentage of completed sync goes down.