> For the complete documentation index, see [llms.txt](https://docs.cakewallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cakewallet.com/release-notes/cake-wallet-6.3.md).

# Cake Wallet 6.3

Covers [v6.3.0](https://github.com/cake-tech/cake_wallet/releases/tag/v6.3.0) (July 21, 2026) and [v6.3.2](https://github.com/cake-tech/cake_wallet/releases/tag/v6.3.2) (July 24, 2026).

## Highlights

* Improve how we display recent transactions, limiting it to three on the home screen with the rest of your transactions a tap away.
* Zcash syncing is faster and more stable, and the integration now tracks current network standards.
* Sending to an alias (OpenAlias, ENS, Unstoppable Domains, Yat, Zcash.me and others) resolves more quickly and reliably.
* Swap TRX and USDT on Tron through Chainflip.
* Bitcoin sends now shuffle input order, and payjoin receiving avoids two known fingerprinting patterns, so your transactions blend in better on-chain.
* Radar — Cake's private messaging app with built-in self-custodial Bitcoin Lightning payments — is now available directly from the Apps screen.

## Improvements & fixes

### v6.3.0 — July 21, 2026

* Amounts are handled with exact precision throughout the app, fixing rounding and decimal edge cases when typing, converting, or displaying values.
* Upgraded the underlying Flutter engine and completed the next phase of internal refactoring, making the app noticeably more responsive.
* Solana wallets sync and load faster; spam-token detection is stricter on Solana and EVM chains.
* Cake Pay gift card buying is smoother, and all card variants are now shown.
* Lightning improvements: payment preimage in transaction details, better handling when a balance fetch fails, and invoice generation restricted to Bitcoin wallets.
* Receive page: Solana and Tron token info is now included in the QR code and payment link, plus fixes to the copy button and the address rotation control.
* Renaming a wallet is more reliable.
* Hardware wallet fixes for Ledger and Trezor, including a Monero passphrase prompt and correct handling of external outputs on Trezor.
* Added a recovery screen if the wallet database fails to open.
* Silent Payments no longer appear in non-Bitcoin wallets, the tokens button no longer appears on Litecoin, and coin control can no longer be edited from Settings.
* Transaction history layout, month and date localization, desktop QR sizing, and haptic feedback when copying.
* Retired unavailable swap providers, updated the price data endpoint, and hardened the vulnerability disclosure policy.
* Assorted UI polish, dependency bumps, and stability fixes.

### v6.3.2 — July 24, 2026

* Hardware wallets: added a back button to the connect screen, so you can always leave the reconnect flow instead of getting stuck.
* Swaps: your coin control selection is no longer reset when you start a swap, and the paste button on the swap page works again.
* Zcash: addresses are no longer unnecessarily persisted in wallet metadata, and the wallet migration path was corrected.
* Fixed a typo in the multichain receive info box.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cakewallet.com/release-notes/cake-wallet-6.3.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.