01576f10ae
Update audit metadata for zcash_client_sqlite 0.11.2 release.
2024-09-03 12:26:56 -06:00
5e6a8f0250
Release zcash_client_sqlite version 0.11.2
2024-09-03 12:20:12 -06:00
1b8334104d
zcash_client_sqlite: Accept 2-part `major.minor` SQLite versions.
2024-09-03 12:20:12 -06:00
61584f7cc0
zcash_client_sqlite: Verify sqlite version compatibility on wallet init.
2024-09-02 21:21:57 -06:00
c91b34ef87
Support older `sqlite` versions.
...
The `FALSE` constant was introduced in sqlite version 3.23.0,
but Android does not support this version of sqlite until API
level 30; we support back to Android API 27 so we have to use
`0` as the constant for `FALSE` instead.
2024-08-30 11:23:45 -06:00
59582a7734
Update audits for zcash_client_sqlite
2024-08-21 16:49:13 -06:00
3afcfe430b
release zcash_client_sqlite version 0.11.1
2024-08-21 16:30:38 -06:00
876a5a3b00
Merge pull request #1506 from zcash/zcs-fix-migrations
...
zcash_client_sqlite: Fix migration DAG edges
2024-08-21 16:29:25 -06:00
3dba2fa9ae
zcash_client_sqlite: Make `tx_retrieval_queue` depend upon all leaf migrations
2024-08-21 16:01:51 -06:00
b1cb8be244
zcash_client_sqlite: Make migration dependencies easier to track.
2024-08-21 15:50:39 -06:00
e4b3fb27b5
zcash_client_sqlite: Fix clippy complaints.
2024-08-21 14:14:31 -06:00
34402f7bea
zcash_client_sqlite: Adjust migration DAG edges to fix dependency bug
2024-08-21 15:06:00 -05:00
6903fa6543
zcash_client_sqlite: Add test showing tx_retrieval_queue migration bug
2024-08-21 14:58:11 -05:00
7c416d533b
zcash_client_sqlite: Add test for linear migration between db states
2024-08-21 14:27:59 -05:00
40ca428c60
Merge pull request #1505 from zcash/release/zcash_client_sqlite-0.11.0
...
release zcash_client_sqlite version 0.11.0
2024-08-20 10:02:23 -06:00
7c6dba726b
Update audit metadata for `zcash_client_sqlite`
2024-08-20 09:44:34 -06:00
c7a8bed081
release zcash_client_sqlite version 0.11.0
2024-08-20 09:21:40 -06:00
ed66c79ed5
Merge pull request #1504 from zcash/release/zcash_client_backend-0.13.0
...
release zcash_client_backend version 0.13.0
2024-08-20 09:07:13 -06:00
df32629352
Update audit metadata for `zcash_client_backend`
2024-08-20 08:56:25 -06:00
d9fa772665
release zcash_client_backend version 0.13.0
2024-08-20 08:00:05 -06:00
c1532093b4
Merge pull request #1472 from zcash/zcb-tor-grpc
...
zcash_client_backend: Add `tor::Client::connect_to_lightwalletd`
2024-08-20 07:59:22 -06:00
95dacc2ac0
Merge pull request #1503 from zcash/release/zip321-0.1.0
...
release zip321 version 0.1.0
2024-08-19 20:09:32 -06:00
49c623bc15
Record audit of zip321 version 0.1.0
2024-08-19 19:52:17 -06:00
827192ebcb
release zip321 version 0.1.0
2024-08-19 19:37:46 -06:00
c7feeb5956
Merge pull request #1502 from zcash/release/zcash_keys-0.3.0
...
zcash_keys: release version 0.3.0
2024-08-19 19:32:35 -06:00
1acf583738
Record audit for zcash_keys 0.2.0 -> 0.3.0
2024-08-19 19:30:35 -06:00
555900689f
release zcash_keys version 0.3.0
2024-08-19 19:24:07 -06:00
b59c84ffe9
Merge pull request #1497 from zcash/release/zcash_proofs-0.16.0
...
zcash_proofs: Release version 0.16.0
2024-08-19 19:23:54 -06:00
9022bf6aa4
Audit zcash_proofs 0.15.0 -> 0.16.0
2024-08-19 19:22:59 -06:00
97c4a76c2d
release zcash_proofs version 0.16.0
2024-08-19 19:03:28 -06:00
098e46affe
Merge pull request #1492 from zcash/release/zcash_primitives-0.16.0
...
zcash_primitives: Release version 0.16.0
2024-08-19 19:03:08 -06:00
3f8af7fcee
Audit zcash_primitives 0.15.1 -> 0.16.0
2024-08-19 18:59:24 -06:00
68788e4f2e
zcash_primitives release version 0.16.0
2024-08-19 18:44:36 -06:00
6f6af4138a
Merge pull request #1501 from zcash/release/zcash_address-0.4.0
...
zcash_address: release version 0.4.0
2024-08-19 18:44:02 -06:00
e6663e5d0a
Update `cargo vet` for zcash_address-0.4.0 release
2024-08-19 18:40:40 -06:00
0e803a73c9
release zcash_address version 0.4.0
2024-08-19 16:24:03 -06:00
38972e9013
Merge pull request #1500 from zcash/release/zcash_encoding-0.2.1
...
release zcash_encoding version 0.2.1
2024-08-19 16:16:37 -06:00
bd4542b3cf
release zcash_encoding version 0.2.1
2024-08-19 15:08:37 -06:00
abb241cd65
Merge pull request #1499 from nuttycom/release/zcash_protocol-0.2.0
...
zcash_protocol release version 0.2.0
2024-08-19 14:59:05 -06:00
d3ab6fb1ae
zcash_protocol release version 0.2.0
2024-08-19 14:36:11 -06:00
b59d027987
Merge pull request #1496 from nuttycom/fix/transparent_spend_recording
...
zcash_client_sqlite: Track all transparent spends.
2024-08-19 14:26:17 -06:00
5a32d3b9bd
zcash_client_sqlite: Ensure the end heights of `SpendsFromAddress` requests do not exceed the chain tip.
...
`lightwalletd` will return an error in the case that the requested end
height exceeds the chain tip. This should be considered a bug in
lightwalletd, but for now we will work around it in the wallet.
2024-08-19 12:10:14 -06:00
484659dddb
zcash_client_sqlite: Reprocess wallet transactions on upgrade to restore additional transparent history.
2024-08-16 16:55:03 -06:00
c22a2a4c92
zcash_client_sqlite: Move `store_decrypted_tx` to the `wallet` module.
...
This permits this method to be used in a migration.
2024-08-16 16:42:18 -06:00
ff47005024
Merge pull request #1483 from zcash/dependabot/github_actions/EmbarkStudios/cargo-deny-action-2
...
build(deps): bump EmbarkStudios/cargo-deny-action from 1 to 2
2024-08-16 23:42:10 +01:00
4059bfeca2
zcash_client_sqlite: Ensure we will query for status of unmined transactions in `store_decrypted_tx`
2024-08-16 14:24:15 -06:00
3089e3b29d
zcash_client_sqlite: Do not overwrite address on update in `put_sent_output`
2024-08-16 13:07:12 -06:00
7a00ff0c2a
zcash_client_backend: Add `Ord` and `Hash` impls for `TransactionDataRequest`
2024-08-16 11:06:14 -06:00
895d92b66b
zcash_client_sqlite: Ensure we set mined-ness information in `store_decrypted_tx`
2024-08-16 10:49:59 -06:00
54f59a8778
zcash_client_sqlite: Track all transparent spends.
...
Prior to this change, the `mark_transparent_utxo_spent` method assumed
that the UTXO information for outputs belonging to the wallet would be
known to exist before their spends could be detected. However, this is
not true in transparent history recovery: the spends are detected first.
We now cache the information about those spends so that we can then
correctly record the spend when the output being spent is eventually
detected.
At present, data from this spend cache is never deleted. This is because
such deletions could undermine history recovery in some narrow cases
related to chain reorgs.
2024-08-15 16:37:37 -06:00
Kris Nuttycombe
Jack Grigg
Daira-Emma Hopwood