brave-core#23383merged 2024-05-06 into master by cypt4 Re-land zcash keyring support Linked by: GitHub closing reference, “Resolves/Fixes” line in the PR description
brave-core#22870merged 2024-04-30 into master by cypt4 Add Orchard support to Zcash keyring Linked by: GitHub closing reference, “Resolves/Fixes” line in the PR description
brave-core#22396closed without merge into master by cypt4 Orchard keyring Linked by: GitHub closing reference, “Resolves/Fixes” line in the PR description, branch name brave_32303 (weaker evidence; titles share a keyword)
Release notes
No platform changelog lists this item.
Validation
Not QA-tested (QA/No).
No QA pass labels.
QA labels are Brave’s own validation records per OS. They are not independent verification by this tracker.
Target
1.67.x - Release
For closed issues Brave sets the milestone to the earliest version line it believes the change landed in, and renames milestones as branches move from Nightly to Beta to Release. This tracker shows it but relies on build ancestry and release notes for availability.
Platforms (OS labels): Android, Desktop
Owner: cypt4 · PR authors: cypt4
Build presence
Whether a merged pull request in this group is an ancestor of the brave-core tag of each platform’s current build (from versions.brave.com). Code presence is not the same as a feature being exposed on that platform.
Platform
Release
Beta
Nightly
Desktop
Included1.97.59in v1.96.61 (GitHub compare v1.96.61...f5dc515f: behind); later builds of the same history include it (brave-core#23383)
Included1.98.47in v1.96.61 (GitHub compare v1.96.61...f5dc515f: behind); later builds of the same history include it (brave-core#23383)
Included1.100.5in v1.96.61 (GitHub compare v1.96.61...f5dc515f: behind); later builds of the same history include it (brave-core#23383)
Android
Included1.97.57in v1.96.61 (GitHub compare v1.96.61...f5dc515f: behind); later builds of the same history include it (brave-core#23383)
Included1.98.52in v1.96.61 (GitHub compare v1.96.61...f5dc515f: behind); later builds of the same history include it (brave-core#23383)
Included1.100.5in v1.96.61 (GitHub compare v1.96.61...f5dc515f: behind); later builds of the same history include it (brave-core#23383)
iOS
Included1.96.62in v1.96.61 (GitHub compare v1.96.61...f5dc515f: behind); later builds of the same history include it (brave-core#23383)
Included1.99.44in v1.96.61 (GitHub compare v1.96.61...f5dc515f: behind); later builds of the same history include it (brave-core#23383)
Included1.100.7in v1.96.61 (GitHub compare v1.96.61...f5dc515f: behind); later builds of the same history include it (brave-core#23383)
Resolves https://github.com/brave/brave-browser/issues/32303 Submitter Checklist: - [ ] I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them - [ ] There is a ticket for my issue - [ ] Used Github auto-closing keywords in the PR description above - [ ] Wrote a good PR/commit description - [ ] Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the…
Timeline (3 of 7 events)
2024-05-06 16:16 Merged masterby bridiver
2024-05-06 16:16 Closed by bridiver
2024-05-06 16:17 Milestone set 1.67.x - Nightlyby github-actions
Resolves https://github.com/brave/brave-browser/issues/32303 Pr targets brave_36128 until it is merged Adds Orchard key generation to the ZCashKeyring. Orchard keys are generated using Orchard crate. Orchard uses different keys generation strategy described here. ExtendedSpendingKey is a sort of account private key. Using this key we can generate public or internal address then. Also added orchard address support to Unified Addresses . Now we can generate address string…
Based on Orchard crate support https://github.com/brave/brave-core/pull/22097 Resolves https://github.com/brave/brave-browser/issues/32303 Submitter Checklist: - [ ] I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them - [ ] There is a ticket for my issue - [ ] Used Github auto-closing keywords in the PR description above - [ ] Wrote a good PR/commit description - [ ] Squashed any review feedback or…