librustzcash/zcash_client_backend
Kris Nuttycombe 802c01002a zcash_client_backend: Rework scanning key identifiers.
In the process of making the internals of `scan_block_with_runner`
reusable across Sapling and Orchard, it became evident that key
identifier abstraction along the lines of #1175 is needed more
generally. This commit refactors the use of ZIP 32 account identifiers
and key scopes to better separate scanning concerns from ZIP 32 key
derivation. In the process, this removes a fair amount of unnecessary
polymorphism from `zcash_client_backend::wallet::WalletTx` and related
types.
2024-02-29 11:55:25 -07:00
..
examples Use `sapling-crypto` crate directly outside `zcash_primitives` 2023-12-12 19:50:26 +00:00
proptest-regressions ZIP 321 Reference Implementation (#294) 2020-10-15 14:03:40 +01:00
proto zcash_client_backend: Address comments from code review & fix incorrect `data_api::wallet` documentation. 2024-02-14 20:24:12 -07:00
src zcash_client_backend: Rework scanning key identifiers. 2024-02-29 11:55:25 -07:00
CHANGELOG.md zcash_client_backend: Rework scanning key identifiers. 2024-02-29 11:55:25 -07:00
Cargo.toml Merge pull request #1168 from nuttycom/zcash_keys_sapling_feature 2024-02-26 19:16:07 -07:00
LICENSE-APACHE Rename zcash_wallet to zcash_client_backend, set to 2018 edition 2019-06-27 16:02:12 +01:00
LICENSE-MIT Rename zcash_wallet to zcash_client_backend, set to 2018 edition 2019-06-27 16:02:12 +01:00
README.md Remove notices about the BOSL license exception, which are no longer needed. 2024-01-17 23:28:15 +00:00
build.rs Add a protobuf representation for transaction proposals. 2023-11-09 20:02:36 -07:00

README.md

zcash_client_backend

This library contains Rust structs and traits for creating shielded Zcash light clients.

Building

Note that in order to (re)build the GRPC interface, you will need protoc on your $PATH. This is not required unless you make changes to any of the files in ./proto/.

License

Licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.