Zcash × Brave WalletPersonal project
Search/ Updated
Menu

Type to search. Use ↑ ↓ and Enter to open a result.

fix: reject malformed Zcash unified addresses before choosing a receiver

Open Bug Addresses, accounts & memos

Lead item brave-browser#58752 · opened by iAnonymous3000 · last source update

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).

Issue state

Open

Open.

Implementation

No pull request is linked by closing keywords, GitHub’s closing references, a brave_<issue> branch name or the issue timeline.

Release notes

No platform changelog lists this item.

Validation

QA required (QA/Yes).

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: unassigned

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.

PlatformReleaseBetaNightly
DesktopUnknown 1.97.59no merged PR is linked, so presence in this build is unknownUnknown 1.98.47no merged PR is linked, so presence in this build is unknownUnknown 1.100.5no merged PR is linked, so presence in this build is unknown
AndroidUnknown 1.97.57no merged PR is linked, so presence in this build is unknownUnknown 1.98.52no merged PR is linked, so presence in this build is unknownUnknown 1.100.5no merged PR is linked, so presence in this build is unknown
iOSUnknown 1.96.62no merged PR is linked, so presence in this build is unknownUnknown 1.99.44no merged PR is linked, so presence in this build is unknownUnknown 1.100.7no merged PR is linked, so presence in this build is unknown

Members and their history

Issue

brave-browser#58752 fix: reject malformed Zcash unified addresses before choosing a receiver

State: open · created · updated · discovered via label:feature/web3/wallet/zcash, search:zcash · matched label:feature/web3/wallet/zcash, title:zcash, title:unified addresses, body:unified addresses

bug OS/macOS priority/P3 QA/Yes release-notes/include feature/web3/wallet OS/Desktop feature/web3/wallet/core feature/web3/wallet/zcash

On macOS Nightly 1.97.1, unified addresses with duplicate or out-of-order receivers reach the migration restriction instead of a malformed-address error, while an address with an invalid shielded receiver is accepted as a transparent recipient. Validate the entire unified address before choosing a receiver; the migration restriction still blocks the duplicate and out-of-order cases, and no transaction was sent. cc @kdenhartog

Timeline (5 of 9 events)
  1. 2026-09-05 03:09 Label added OS/macOS by iAnonymous3000
  2. 2026-09-05 03:09 Label added priority/P3 by iAnonymous3000
  3. 2026-09-05 03:09 Label added QA/Yes by iAnonymous3000
  4. 2026-09-05 03:09 Label added release-notes/include by iAnonymous3000
  5. 2026-09-05 03:09 Label added OS/Desktop by iAnonymous3000

Recorded changes

  1. New issue

    New bug report: fix: reject malformed Zcash unified addresses before choosing a receiver

    Opened in brave-browser#58752. This is a report or request, not a confirmed change to Brave Wallet.

    brave-browser#58752
    Evidence
    • created 2026-09-05T03:09:29Z

    Source time: · Detected: · Backfilled from source history

    2026-09-05T03:09:29Z