Zcash × Brave WalletPersonal project
Search/ Updated
Menu

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

fix: decode extended Zcash address fields with the correct byte order

Open Bug Addresses, accounts & memos

Lead item brave-browser#58754 · 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): none

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#58754 fix: decode extended Zcash address fields with the correct byte order

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

bug priority/P4 QA/Yes release-notes/exclude feature/web3/wallet feature/web3/wallet/core feature/web3/wallet/zcash

Focused tests against the September 4, 2026 master snapshot show that multi-byte Zcash address fields are decoded to the wrong value, such as 256 becoming 1, and unnecessarily long encodings of small values are accepted. Use the specified byte order and require the shortest valid encoding; the long-value failures were reproduced in isolated source tests, and ordinary supported receiver fields are below the affected multi-byte range. cc @kdenhartog

Timeline (3 of 7 events)
  1. 2026-09-05 03:10 Label added priority/P4 by iAnonymous3000
  2. 2026-09-05 03:10 Label added QA/Yes by iAnonymous3000
  3. 2026-09-05 03:10 Label added release-notes/exclude by iAnonymous3000

Recorded changes

  1. New issue

    New bug report: fix: decode extended Zcash address fields with the correct byte order

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

    brave-browser#58754
    Evidence
    • created 2026-09-05T03:10:22Z

    Source time: · Detected: · Backfilled from source history

    2026-09-05T03:10:22Z