joshs
April 2, 2025, 5:31pm
1
28 Likes
dismad
April 3, 2025, 4:47pm
2
I think its great Brave has an “Orchard only” UA option, and hope more wallets allow this flexibility. Choose “Shielded”.
Some feedback for deposits, its a bit confusing, but here is how
For a quick demo on mobile, check out what we tested last month
7 Likes
I am only able to see a Transparent Address.
Original account name lacks the “Shielded Icon”
Account 2 just added after updating Brave via command line
Shows:
Clicking on the “Shielded Account” only reveals the transparent addy, even If I click on the different “deposit” buttons.
Do I need to deposit via a T-address first, your screenshot indicates no balance, so I am confused… How are you able to see the “details” and other address options?
Thanks! I was using “Brave” I had to go back to “Brave Nightly”
Doing so allowed me to follow the video found here:
master
← brave_44432
opened 10:15AM - 05 Mar 25 UTC
Resolves https://github.com/brave/brave-browser/issues/44432
## Submitter… Checklist:
- [ ] I confirm that no [security/privacy review is needed](https://github.com/brave/brave-browser/wiki/Security-reviews) and no other type of reviews are needed, or that I have [requested](https://github.com/brave/reviews/issues/new/choose) them
- [ ] There is a [ticket](https://github.com/brave/brave-browser/issues) for my issue
- [ ] Used Github [auto-closing keywords](https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue) in the PR description above
- [ ] Wrote a good [PR/commit description](https://google.github.io/eng-practices/review/developer/cl-descriptions.html)
- [ ] Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
- [ ] Added appropriate labels (`QA/Yes` or `QA/No`; `release-notes/include` or `release-notes/exclude`; `OS/...`) to the associated issue
- [ ] Checked the PR locally:
* `npm run test -- brave_browser_tests`, `npm run test -- brave_unit_tests` [wiki](https://github.com/brave/brave-browser/wiki/Tests)
* `npm run presubmit` [wiki](https://github.com/brave/brave-browser/wiki/Presubmit-checks), `npm run gn_check`, `npm run tslint`
- [ ] Ran `git rebase master` (if needed)
## Reviewer Checklist:
- [ ] A security review [is not needed](https://github.com/brave/brave-browser/wiki/Security-reviews), or a link to one is included in the PR description
- [ ] New files have MPL-2.0 license header
- [ ] Adequate test coverage exists to prevent regressions
- [ ] Major classes, functions and non-trivial code blocks are well-commented
- [ ] Changes in component dependencies are properly reflected in `gn`
- [ ] Code follows the [style guide](https://chromium.googlesource.com/chromium/src/+/HEAD/styleguide/c++/c++.md)
- [ ] Test plan is specified in PR before merging
## After-merge Checklist:
- [ ] The associated issue milestone is set to the smallest version that the
changes has landed on
- [ ] All relevant documentation has been updated, for instance:
- [ ] https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
- [ ] https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
- [ ] https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
- [ ] https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
- [ ] https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
- [ ] https://github.com/brave/brave-browser/wiki/QA-Guide
- [ ] https://github.com/brave/brave-browser/wiki/P3A
## Test Plan:
That confirmed a higher release version. Brave was 1.77.95 -vs- Nightly 1.79.23
Brave was a no-go – Brave NIghtly was All Good! and I could then see the shielded address details.
If it works in Brave, then I haven’t figured that out yet…
1 Like
dismad
April 3, 2025, 7:26pm
6
Latest Brave should work, but It may depend on what version you have.
I’m running the latest Xubuntu and Brave v 1.77.95
Same build (1.77.95) |Brave|1.77.95 Chromium: 135.0.7049.52 (Official Build) unknown (64-bit)|
| — | — |
|Revision|9e0bf4d8fff1d4549561cf6f59c2a200a0fb516f|
|OS|Linux|
but I am Fedora 41, and it Is not showing the same stuff,
Cache Clean and restart allowed the option to “Shield” to appear under “Edit”. Brave is now good-to-go - with only 1 shielded address allowed..?..
What exactly is the difference between “Unified” and “Shielded” other than a longer address?
1 Like
dismad
April 3, 2025, 10:04pm
9
The Unified encodes a transparent receiver, so in the case you dont want others seeing that address, you would use the shielded option instead. Plug your Unified into this to see for yourself.
2 Likes
i cannot find the shielded adress to deposit, why is this so hard
dismad
April 4, 2025, 2:00pm
11
You may need to clear the cache as FortifieDEX did.
Also here is how you convert old transparent accounts ( h/t @tokidoki )
1 Like
dismad showed the option box to select the option to convert to shielded account, I had problems seeing that option also…
That is what led me to the GitHub video. It’s a 2 minute video found when you scroll down from the link above.
brave://flags was what I needed to type to be able to search for “zcash” just like the video shows, once I enabled support for shielded - that’s when I - under settings - privacy and security - deleted all history and cookies. Closed everything out and restarted.
That’s when the option box dismad showed appeared for me. Make sure you scroll down also, some of the options were off the bottom of my screen.
It seems it is a common problem. There is an open GitHub request for support for this same problem of seeing the 3 address types. The request was 5 hours old yesterday, with no responses, when I saw it while searching for a solution and found that video.
2 Likes
dismad
April 13, 2025, 8:52pm
13
We have an updated tutorial to share, (h/t @vito @peacemonger )
5 Likes