update librustzcash #1
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zcash_client_sqlite: Migrate from `schemer` to `schemerz`
Update the `rusqlite` and `arti-client` crates
Make transparent tests generic over backend implementation and move to `zcash_client_backend` crate
Fix/rewind checkpoint id selection
Bump MSRV to 1.77
… instead of a tuple.
…allet metadata. In the process this modifies input selection to take the change strategy as an explicit argument, rather than being wrapped as part of the input selector.
Co-authored-by: Jack Grigg <[email protected]> Co-authored-by: Daira-Emma Hopwood <[email protected]>
…_sqlite-0.12.2-merge
zcash_keys: Enable `no_std` usage.
PCZT improvements
Bumps [codecov/codecov-action](https://github.com/codecov/codecov-action) from 5.1.1 to 5.1.2. - [Release notes](https://github.com/codecov/codecov-action/releases) - [Changelog](https://github.com/codecov/codecov-action/blob/main/CHANGELOG.md) - [Commits](codecov/codecov-action@v5.1.1...v5.1.2) --- updated-dependencies: - dependency-name: codecov/codecov-action dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
pczt: Add a Redactor role
Add CI workflow to check no_std builds for `pczt` and `zcash_keys`
…/codecov-action-5.1.2 build(deps): bump codecov/codecov-action from 5.1.1 to 5.1.2
…ates. This commit temporarily removes the reexported types to simplify the removal process; the reexports will be reintroduced with deprecation annotations in the subsequent commit.
Due to limitations described in rust-lang/rust#30827, we can't just deprecate the `pub use` stanzas; instead, we have to replace reexports with new (deprecated) modules and public types which then internally reexport the module internals or alias the reexported types, respectively.
Co-authored-by: Jack Grigg <[email protected]>
Deprecate reexports of types that have been moved to other crates.
Updates to Protobuf generation dependencies
… `NetworkConstants` trait.
…he `transparent-inputs` feature flag. This variant should not have been a part of the public API unless `tranpsarent-inputs` was enabled, as it's necessary for the wallet to be able to spend a transparent input in order for a ZIP 320 transaction to be properly constructed and authorized. In addition, this simplifies the `Recipient` API by removing its type parameters in favor of concrete types, made possible by using a separate type for the build process.
…gration. This test is not specific to the migration; it's a more general test of ephemeral address rotation behavior and should evolve with the evolution of address rotation and gap limit handling, not be tied to the behavior of methods at the time that this migration was created.
This permits `UnifiedAddressRequest` values an additional dimension of flexibility, permitting generation of unified addresses having receivers for all recever types for which a key item exists and a diversifier index is valid.
This removes a `fix_bad_change_flagging` migration test duplicated from `zcash_client_backend::data_api::testing::pool::shiled_transparent`. It is impractical to maintain backwards compatibility to earlier database states for the entire test harness, which is more or less what retaining this test would require, and the desired outcome is already demonstrated by the `shield_transparent` test; demonstrating the fix directly is unnecessary.
…handling-prep Preparatory refactoring for #1673
The bug was fixed in zcash/lightwalletd@b805382, and the workaround doesn't work with backed by zebrad.
zcash_client_backend: Remove lightwalletd workaround
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.