Kris Nuttycombe
Kris Nuttycombe
Trezor wallets support the SLIP 39 standard for k-of-n seed phrase backup. We should make it possible for wallets based on `zcash_client_backend` to restore based upon SLIP 39 seed phrase...
This includes support for storing and using in perpetuity legacy transparent keys derived from system randomness. Existing exchange users have dedicated deposit addresses that they may have stored in other...
At present, for some insertion patterns, `Reference` nodes may be left behind within shards after they are no longer needed. This is particularly the case when a frontier is inserted...
Ideally the errors here would all be panics, as construction of such a node represents a programming error; however, it is preferable to return extra contextual information about the circumstance...
https://github.com/Electric-Coin-Company/zcash-swift-wallet-sdk/blob/main/Sources/ZcashLightClientKit/Rust/ZcashRustBackend.swift#L1004 This line is incorrect; https://github.com/Electric-Coin-Company/zcash-light-client-ffi/blob/feature/transparent_gap_limit_handling/rust/src/lib.rs#L2183 will intentionally return a null pointer when there are no funds available for shielding.
At present, there's no way to enter a birthday height, which means that existing funds controlled by the Keystone device will not be detected if re-enrolling a device after deleting...
### Describe the issue When entering a seed phrase after performing a wallet reset, the following error is displayed:  ### Can you reliably reproduce the issue? #### If so,...
At present, there's no way to enter a birthday height, which means that existing funds controlled by the Keystone device will not be detected if re-enrolling a device after deleting...
### What happened? I expected to see this happen: RPC results for the `getinfo` RPC method should use the same type for returned fields. Instead, this happened: ``` ~/work/zcash/release on...