Currently scan_cached_blocks takes a BlockSource and a WalletWrite, and combines their information to scan a given range of blocks. It would be useful to clearly denote the dataflows here, as we have the following conceptual relationship that we would like to embody in the zcashd wallet replacement:
We should ensure that the individual logic necessary for these three components is accessible from zcash_client_backend, by refactoring the internals of scan_cached_blocks to leverage them in this way. This might coincide with the exposition of the BatchRunners type, or it might just mean exposing a wrapper around it that a future Scanner could use.
Currently
scan_cached_blocks
takes aBlockSource
and aWalletWrite
, and combines their information to scan a given range of blocks. It would be useful to clearly denote the dataflows here, as we have the following conceptual relationship that we would like to embody in thezcashd
wallet replacement:We should ensure that the individual logic necessary for these three components is accessible from
zcash_client_backend
, by refactoring the internals ofscan_cached_blocks
to leverage them in this way. This might coincide with the exposition of theBatchRunners
type, or it might just mean exposing a wrapper around it that a future Scanner could use.