AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 42 Monero

fix: zcash address for exchange (#3491)

Public commit record

What the developer wrote

Authored by cyan

88/100 · Strong
fix: zcash address for exchange (#3491)

* fix: zcash address for exchange

* fix: honour the restore height the user entered

- Make Zcash rescan work in both directions by resetting sync from the new birth height
- Keep the entered height when restoring a wallet from keys
- Tolerate grouping separators in typed restore heights

---------

Co-authored-by: Vik Sharma <vik@cakewallet.com>
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit fixes two user-facing bugs in Cake Wallet's Zcash handling. First, it ensures the correct transparent Zcash address is used when sending funds to an exchange, which could previously lead to deposits going to the wrong address type. Second, it makes wallet restore respect the block height the user typed in, and allows that height to contain grouping separators like commas. The changes are bug fixes rather than a disclosed security vulnerability, but the wrong-address issue has clear financial-impact potential.

Recommended action

Treat as a routine but important bug-fix release. Verify that exchange flows with Zcash now produce a transparent receive address and that key-based restores use the user-supplied height. No emergency response is warranted absent additional disclosure.

Security signals we found

01

Financial-impact bug fix: exchange deposits could be directed to an incorrect Zcash address type before this patch

02

New address selection path in exchange_view_model.dart relying on walletInfo address labels

03

Restore-height now honored for key-based restores and tolerant of formatting separators

04

Rescan logic now validates on-disk birth height before proceeding

05

No explicit security disclosure, CVE, or researcher attribution in commit or supplied references

Risk score

Why this scored 42/100

Our methodology →
Potential impact 12/30
Exploitability 8/25
Stealth signal 6/15
Affected reach 7/15
Confidence 6/10
Evidence quality 3/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.