release zcash_client_sqlite version 0.11.0
This commit is contained in:
parent
ed66c79ed5
commit
c7a8bed081
|
@ -5877,7 +5877,7 @@ dependencies = [
|
||||||
|
|
||||||
[[package]]
|
[[package]]
|
||||||
name = "zcash_client_sqlite"
|
name = "zcash_client_sqlite"
|
||||||
version = "0.10.3"
|
version = "0.11.0"
|
||||||
dependencies = [
|
dependencies = [
|
||||||
"assert_matches",
|
"assert_matches",
|
||||||
"bip32",
|
"bip32",
|
||||||
|
|
|
@ -6,29 +6,31 @@ and this library adheres to Rust's notion of
|
||||||
[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
||||||
|
|
||||||
## [Unreleased]
|
## [Unreleased]
|
||||||
### Notable changes
|
|
||||||
`zcash_client_sqlite` now supports TEX (transparent-source-only) addresses as specified
|
|
||||||
in ZIP 320. Sending to one or more TEX addresses will automatically create a multi-step
|
|
||||||
proposal that uses two transactions.
|
|
||||||
|
|
||||||
In order to take advantage of this support, client wallets will need to be able to send
|
## [0.11.0] - 2024-08-20
|
||||||
multiple transactions created from `zcash_client_backend::data_api::wallet::create_proposed_transactions`.
|
|
||||||
This API was added in `zcash_client_backend` 0.11.0 but previously could only return a
|
|
||||||
single transaction.
|
|
||||||
|
|
||||||
**Note:** This feature changes the use of transparent addresses in ways that are relevant
|
`zcash_client_sqlite` now provides capabilities for the management of ephemeral
|
||||||
to security and access to funds, and that may interact with other wallet behaviour. In
|
transparent addresses in support of the creation of ZIP 320 transaction pairs.
|
||||||
particular it exposes new ephemeral transparent addresses belonging to the wallet, which
|
|
||||||
need to be scanned in order to recover funds if the first transaction of the proposal is
|
In addition, `zcash_client_sqlite` now provides improved tracking of transparent
|
||||||
mined but the second is not, or if someone (e.g. the TEX-address recipient) sends back
|
wallet history in support of the API changes in `zcash_client_backend 0.13`,
|
||||||
funds to those addresses. See [ZIP 320](https://zips.z.cash/zip-0320) for details.
|
and the `v_transactions` view has been modified to provide additional metadata
|
||||||
|
about the relationship of each transaction to the wallet, in particular whether
|
||||||
|
or not the transaction represents a wallet-internal shielding operation.
|
||||||
|
|
||||||
### Changed
|
### Changed
|
||||||
|
- MSRV is now 1.70.0.
|
||||||
|
- Updated dependencies:
|
||||||
|
- `zcash_address 0.4`
|
||||||
|
- `zcash_client_backend 0.13`
|
||||||
|
- `zcash_encoding 0.2.1`
|
||||||
|
- `zcash_keys 0.3`
|
||||||
|
- `zcash_primitives 0.16`
|
||||||
|
- `zcash_protocol 0.2`
|
||||||
- `zcash_client_sqlite::error::SqliteClientError` has a new `ReachedGapLimit` and
|
- `zcash_client_sqlite::error::SqliteClientError` has a new `ReachedGapLimit` and
|
||||||
`EphemeralAddressReuse` variants when the "transparent-inputs" feature is enabled.
|
`EphemeralAddressReuse` variants when the "transparent-inputs" feature is enabled.
|
||||||
- The result of the `v_tx_outputs` SQL query could now include transparent outputs
|
- The result of the `v_tx_outputs` SQL query could now include transparent outputs
|
||||||
with unknown height.
|
with unknown height.
|
||||||
- MSRV is now 1.70.0.
|
|
||||||
- `zcash_client_sqlite::error::SqliteClientError` has changed variants:
|
- `zcash_client_sqlite::error::SqliteClientError` has changed variants:
|
||||||
- Removed `HdwalletError`.
|
- Removed `HdwalletError`.
|
||||||
- Added `AccountCollision`.
|
- Added `AccountCollision`.
|
||||||
|
|
|
@ -1,7 +1,7 @@
|
||||||
[package]
|
[package]
|
||||||
name = "zcash_client_sqlite"
|
name = "zcash_client_sqlite"
|
||||||
description = "An SQLite-based Zcash light client"
|
description = "An SQLite-based Zcash light client"
|
||||||
version = "0.10.3"
|
version = "0.11.0"
|
||||||
authors = [
|
authors = [
|
||||||
"Jack Grigg <jack@z.cash>",
|
"Jack Grigg <jack@z.cash>",
|
||||||
"Kris Nuttycombe <kris@electriccoin.co>"
|
"Kris Nuttycombe <kris@electriccoin.co>"
|
||||||
|
|
Loading…
Reference in New Issue