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

fix: solana token sends to pda addresses and receive qr fiat amounts (#3799)

Public commit record

What the developer wrote

Authored by David Adegoke

70/100 · Adequate
fix: solana token sends to pda addresses and receive qr fiat amounts (#3799)
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
The short version

What changed, and why it matters

This commit fixes two separate bugs in Cake Wallet. First, it improves Solana token sends to addresses that are Program Derived Addresses (PDAs) — special address types used by smart contracts. Previously, sending tokens to such addresses could fail or create associated token accounts incorrectly. The fix checks whether the destination is a PDA, verifies it is not itself a token account, and then allows the off-curve owner when deriving the recipient's associated token account. Second, it fixes a UI bug where fiat-to-crypto conversion in QR code receive amounts could show too many decimal places for tokens with fewer decimals than 8, by capping the displayed precision to the cryptocurrency's actual decimal count. It also corrects a typo in an error message ('receipient' to 'recipient').

Recommended action

Review the Solana token send path for additional edge cases with off-curve recipients, and verify that the new account-info RPC call handles network failures and null responses safely. Consider whether the fiat-to-crypto QR fix should also apply to other amount-formatting locations.

Security signals we found

01

Off-curve Solana address handling added for token sends

02

Validation that off-curve destination is not itself a token account

03

allowOwnerOffCurve flag enabled for PDA owners in associated token account derivation

04

Precision cap added to fiat-to-crypto QR amount conversion

Risk score

Why this scored 41/100

Our methodology →
Potential impact 12/30
Exploitability 8/25
Stealth signal 5/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.