librustzcash
librustzcash copied to clipboard
zcash
Rust-language assets for Zcash
error[E0432]: unresolved imports `zcash_primitives::constants::CRH_IVK_PERSONALIZATION`, `zcash_primitives::constants::PROOF_GENERATION_KEY_GENERATOR`, `zcash_primitives::constants::SPENDING_KEY_GENERATOR` --> src/rust/src/sapling/spec.rs:9:17 | 9 | ...::{CRH_IVK_PERSONALIZATION, PROOF_GENERATION_KEY_GENERATOR, SPENDING_KEY_GENERATOR}, | ^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^ no `SPENDING_KEY_GENERATOR` in `constants` | | | | | no `PROOF_GENERATION_KEY_GENERATOR` in...
Upgrading bip0039 to v0.12 in zcash_primitives resolves Zebra's ability to build with Arti (Tor) support. Patch versions will need to be released of the following crates to simplify integration with...
At present, the transparent UTXO set of the wallet is populated by querying for unspent TXOs associated with a set of addresses, and adding those to the wallet's UTXO set,...
At present, we only track what is in the UTXO set at the time that UTXO information is requested from the light wallet server. This is sufficient for shielding funds,...
As part of enabling wallets to track multiple candidate chain tips (instead of implementing rewind logic for reorgs), it is necessary to track multiple alternative evolutions of the commitment trees...
Both `zcashd` and `zcash_client_*` build their state around a canonical chain tip. When a reorg happens, that state is rewound to undo the effects of the old chain, and then...
zcash_primitives: Rework the transparent bundle builder to be more like the shielded bundle builders
The main pattern is the same: construct a `Builder`, add spends and outputs, build a `Bundle`, and apply signatures. However, there are some annoying API differences that cause problems at...
_If_ we decide to support drop-in RPC methods, then we will need to implement those APIs for the wallet service.
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...