zingolib
zingolib copied to clipboard
zingolabs
An API and test-app that exposes zcash functionality for app consumption
Feature request: Equivalent calls to fetch specific operation and transaction information. The "list" call seems to return ALL transactions. z_getoperationstatus, gettransaction, z_viewtransaction
Feature Request: Equivalent of **z_sendmany** available in **zcash-cli** for Unified addresses?
Feature Request: Equivalent of **z_getbalanceforviewingkey** available in **zcash-cli** for Unified addresses?
in zingocli/src/lib.rs ````Rust // At startup, run a sync. if filled_template.sync { let update = commands::do_user_command("sync", &vec![], lightclient.as_ref()); println!("{}", update); } ```` It seems to me that start syncing before...
Given that we've been almost exclusively using the zingo-cli integration tests to test wallet behavior, it would be worth taking a look at all the lightclient tests and porting them...
Avoiding usage of internal address space could lead to incomplete funds discovery when migrating from foreign wallet to Zingo wallet by passing a seed phrase (opposite direction should be fine)....
When running zingo-cli in non-interactive mode it responds human readable messages. It would be good to have an output formatter that can let developers create and then choose different formats...
When an existing wallet is being recovered with a seed phrase, we have don't know how many transparent addresses it was using. It is recommended to assume at least 20...
To calculate a transaction fee, we need to determine the value of any transparent outputs spent in the transaction, and the transaction's `fee_paid` function should handle the rest. This will...