This issue is open on GitHub. Fixes sometimes land through pull requests that do not link the issue (for example a later refactor); this tracker follows only explicit links (closing references, “Resolves” lines, brave_<issue> branch names, uplifts and the issue timeline).
IssueOpen
Linked fixMerged
Code in builds9 of 9 current builds
Release notesNot listed
QANo pass recorded
Issue state
Open
Open. GitHub type: Task.
Implementation
brave-core#39114closed without merge into master by cypt4 [ZCash] Present v6 transaction serializer. Linked by: branch name brave_58167_2 (weaker evidence; titles share a keyword)
brave-core#39113closed without merge into master by cypt4 [ZCash] Refactor unshielding to use v6 transaction format. Linked by: branch name brave_58167_1 (weaker evidence; titles share a keyword)
brave-core#39107closed without merge into master by cypt4 [ZCash] Refactor unshielding to use v6 transaction format. Linked by: branch name brave_58167 (weaker evidence; titles share a keyword)
brave-core#39159merged 2026-08-21 into master by cypt4 [ZCash] Refactor unshielding to use v6 transaction format. Linked by: branch name brave_58167_4 (weaker evidence; titles share a keyword)
Release notes
No platform changelog lists this item.
Validation
No QA label.
No QA pass labels.
QA labels are Brave’s own validation records per OS. They are not independent verification by this tracker.
Target
No milestone set.
Platforms (OS labels): 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...9482d341: behind); later builds of the same history include it (brave-core#39159)
Included1.98.47in v1.96.61 (GitHub compare v1.96.61...9482d341: behind); later builds of the same history include it (brave-core#39159)
Included1.100.5in v1.96.61 (GitHub compare v1.96.61...9482d341: behind); later builds of the same history include it (brave-core#39159)
Android
Included1.97.57in v1.96.61 (GitHub compare v1.96.61...9482d341: behind); later builds of the same history include it (brave-core#39159)
Included1.98.52in v1.96.61 (GitHub compare v1.96.61...9482d341: behind); later builds of the same history include it (brave-core#39159)
Included1.100.5in v1.96.61 (GitHub compare v1.96.61...9482d341: behind); later builds of the same history include it (brave-core#39159)
iOS
Included1.96.62in v1.96.61 (GitHub compare v1.96.61...9482d341: behind); later builds of the same history include it (brave-core#39159)
Included1.99.44in v1.96.61 (GitHub compare v1.96.61...9482d341: behind); later builds of the same history include it (brave-core#39159)
Included1.100.7in v1.96.61 (GitHub compare v1.96.61...9482d341: behind); later builds of the same history include it (brave-core#39159)
Members and their history
Issue
brave-browser#58167 [ZCash] Use v6 transaction format for orchard to transparent transactions
State: open · created · updated · discovered via search:zcash · matched title:zcash, title:orchard, body:unshielding
feature/web3/walletOS/Desktop
Description This is required to support unshielding Steps to reproduce - Actual result - Expected result - Reproduces how often Easily reproduced Brave version (brave://version info) - Channel information - [ ] release (stable) - [ ] beta - [ ] nightly Reproducibility - [ ] with Brave Shields disabled - [ ] with Brave Rewards disabled - [ ] in the latest version of Chrome Miscellaneous information _No response_
This is required to support orchard to transparent transactions. This PR wires v6 transactions to the OrchardToTransparent transaction flow creation. Follow up for https://github.com/brave/brave-core/pull/39115 Test plan : Validate orchard to transparent transactions are working. Resolves https://github.com/brave/brave-browser/issues/58264
Merged into brave-core master on 2026-08-21. Only builds cut from master after this merge (Nightly first) can contain it; whether a published build does is checked per build (see build presence on the item). Beta and Release get it only after a branch cut or an uplift.