You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a MockWalletDb, but that literally just implements the WalletRead etc. traits with dummy data. In order to make the zcash_client_sqlite tests portable to other wallet backends, we should write an in-memory wallet backend that has no persistence, and stores all of the wallet state directly in memory. This is also a good way for the ZF engineers to gain experience with the zcash_client_backend traits.
As a first step, let's put together the framework for this, with todo!()s for all of the trait method implementations.
The text was updated successfully, but these errors were encountered:
@nuttycom and myself talked to the ChainSafe team during LCWG call 83 and we agreed they were actually focusing on this already and it would be good for them to complete this with ECC overseeing code style, API, etc. This is on ChainSafe's critical path (as stated by them)
We have a
MockWalletDb
, but that literally just implements theWalletRead
etc. traits with dummy data. In order to make thezcash_client_sqlite
tests portable to other wallet backends, we should write an in-memory wallet backend that has no persistence, and stores all of the wallet state directly in memory. This is also a good way for the ZF engineers to gain experience with thezcash_client_backend
traits.As a first step, let's put together the framework for this, with
todo!()
s for all of the trait method implementations.The text was updated successfully, but these errors were encountered: