zingolib
zingolib copied to clipboard
zingolabs
An API and test-app that exposes zcash functionality for app consumption
I used Zingolib to create a transaction that spent 0.1 TAZ via a UA with 3 receivers. On the _receiving_ wallet, it all looks good. 0.1 TAZ was received exclusively...
Why is zingolib providing the compound UA in the `to_address` field, leaving the `recipient_ua` field empty for a transaction's `outgoing_tx_data`? I expected the `to_address` to always be the literal address...
A simple attempt to add timeouts to the GrpcConnector gets arcane and obtuse compiler errors.
We currently have to create multiple symlinks to the same binaries and have an obsolete error message. The best solution is to packages binaries in a SSOT fashion.
``` { "result": "failure", "latest_block": 2154100, "total_blocks_synced": 0 } thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: UnexpectedCharacter { ch: 'E', line: 1, column: 1 }', zingocli/src/lib.rs:144:41 note:...
`zingocli/regtest/bin` and `integration-tests/regtest/bin` They should be unified, possibly by defining a `regtest` crate.
reffering to this commit: [37868fdabc0edd2498b07e72a896bb7819189479](https://github.com/zingolabs/zingolib/pull/645/commits/37868fdabc0edd2498b07e72a896bb7819189479) running the following command before and after removing sapling change from `total_change_returned` (https://github.com/zingolabs/zingolib/pull/645/commits/37868fdabc0edd2498b07e72a896bb7819189479#diff-fb2a3b45013be109f635e33515041d535dcbaa600df91bfb88468ee8e77d39d9R1166) `cargo nextest run --features deprecations received_sapling` this command runs two new tests...
@juanky201271 has use-cases for these interfaces: - start_mempool_monitor - new - create_from_wallet_base - read_wallet_from_buffer - create_unconnected - init_logging - read_wallet_from_disk @AArnott has used-cases for these interfaces: - read_wallet_from_disk - create_from_wallet_base_async...