* CompactBlockProcessor: Remove `withDownload` parameter
* backend-lib: Migrate to latest in-progress revision of Rust crates
Includes changes to how accounts are stored and referenced. We now
need to remember and provide the seed fingerprint; for now, given
that we know we only create derived accounts from a single seed, we
search for an account with a matching ZIP 32 account index.
* backend-lib: Add `Backend.isSeedRelevantToWallet`
* Remove nullability of DownloadSuccess param
* Comment update
* Fix Detekt warnings
* backend-lib: Migrate to latest in-progress revision of Rust crates
Includes some renames, and a built-in seed relevancy API that we now
use.
* Separate tree state fetching
- Added continuable retry logic
* Integrate Orchard support
Closes Electric-Coin-Company/zcash-android-wallet-sdk#528.
Closes Electric-Coin-Company/zcash-android-wallet-sdk#761.
* Detekt warnings fix
* Fix unit tests
* Update `TxOutputsView` to use correct column names. (#1425)
* Return an error instead of a panic in the case of data corruption. (#1426)
This removes an `expect` call that risked crashing the app in the case of
database corruption, potentially hiding other bugs.
* Include `orchardSubtreeRootList` in final check
* Revert `orchardSubtreeRootList` check
Explanation comment added
* Changelog update
* Update to zcash_client_sqlite version 0.10.3 (#1428)
---------
Co-authored-by: Honza <rychnovsky.honza@gmail.com>
Co-authored-by: Kris Nuttycombe <kris@electriccoin.co>
The backend now supports proposals that create multiple transactions.
It still does not generate such proposals itself, and we assert this
inside the now-deprecated APIs.
* Migrate to `librustzcash` tag `ecc_sdk-20240130a`
This includes the fix to the empty transaction request serialization
bug, which was preventing shielding from working.
* Release zcash-android-wallet-sdk 2.0.6
* Fix ktlint warnings
* Other CBP minor/formatting changes
---------
Co-authored-by: Honza <rychnovsky.honza@gmail.com>
With the fixes to `v_transactions` and `v_tx_outputs`, there are
several more data fields that may have no data (for rows corresponding
to purely-transparent transactions); their fields are made nullable.