* Shuffle change output on hardware wallet sends
Hardware wallet BTC/LTC sends passed outputs to the PSBT/device in the
given order (change last), a position fingerprint. The outputOrdering
param was plumbed but ignored. Add orderOutputs() and apply it in both
buildHardwareWalletTransaction paths; set the send call site to shuffle.
Refs #3376 (the software send + RBF paths were covered by #3420).
* Shuffle change output on Bitcoin Cash sends
The BCH send path built via ForkedTransactionBuilder with
outputOrdering: none, leaving change deterministically last. The builder
shuffles natively and change is found by isChange, not position, so flip
it to shuffle (matches the BTC software path from #3420).
Refs #3376.
* Update cw_bitcoin/lib/electrum_wallet.dart
Co-authored-by: Omar Hatem <omarh.ismail1@gmail.com>
---------
Co-authored-by: Omar Hatem <omarh.ismail1@gmail.com>
Both providers checked the wrong SettingsStore flag in isEnabled(), so
their toggles in Settings > Connection and sync > Domain lookups had no
effect:
- YatAddressProvider read lookupsWellKnown instead of lookupsYatService,
so the 'Yat' toggle did nothing and '.wellknown' unexpectedly gated it.
- ZcashMeAddressProvider read lookupsZcashNames instead of
lookupsZcashAddress, so the 'Zcash.me' toggle did nothing and it was
gated by the 'Zcash Names' toggle.
Each provider now reads the flag its own toggle writes, matching the
mapping in ConnectionSyncViewModel.lookupValue/setLookupValue.
The string still described the old UI navigation ("Menu → Security and
Backup → Show key/seeds"). With FeatureFlag.hasNewUi there is no Menu,
and the Show seed/keys row is commented out of the Security page. Seeds
and keys now live at Settings → Wallet settings → Seed & Keys.
Rendered in two places, both reachable:
- seed_verification_success_view.dart:54
- wallet_group_existing_seed_description_page.dart:57
Two entries in SupportViewModel's link list displayed one destination
but opened another.
SwapTrade pointed at mailto:support@exolix.com, so a user with a
SwapTrade trade problem emailed Exolix — who cannot help, and who
absorbed another provider's support traffic. The entry was added as
Quantex with Exolix's mailto already copy-pasted in from the entry
above it; the Quantex -> SwapTrade rename updated the title, icon and
linkTitle but carried the wrong link forward.
Point it at https://help.swaptrade.io/contact/, which matches what
docs.cakewallet.com/support/swap lists for SwapTrade. Live chat is the
only contact method that help center publishes — there is no SwapTrade
support email — so the mailto form is not an option. Using a path below
the displayed host follows the existing SideShift entry in this file.
Telegram had the inverse problem: linkTitle read t.me/cakewallet while
the link went to the announcements channel. Here the link was correct —
t.me/cakewallet is a group that self-describes as the inactive Cake
Wallet Community and directs visitors to the announcements channel — so
the stale label was updated to match the destination rather than the
reverse.
The other 15 entries were audited and are consistent.
The 'Rename apk file'/'Find APK file' steps used the raw ${BRANCH_NAME}
as an APK filename, so any branch containing a '/' (e.g. claude/*) made
cp target a non-existent test-apk/<prefix>/ subdirectory and failed the
build. Derive the sanitized branch name from android/app.properties, the
same approach already used in automated_integration_test.yml.
* v6.3.0 Release Candidate
- the new transaction history
- Radar in Apps screen
- Zcash update
- Flutter update
- Parts of the Refactor
should improve how amounts are handled in the app and fix any issue with amounts
improve handling sending to aliases
- Improvements for Cake Pay mobile
- Bug fixes
* don't use memo for note/message values
* save message in QR locally in the notes field
* Make stealth addresses generated from silent payment, not reliant on output index (#3420)
* - fix swaps showing only on primary account
- switch tron default node
- privacy fixes
* - enlarge destination tag and make it copiable
- migrate users on hashvault
- minor fix
* feat: zkool2
* feat: rescan on zkool
fix: sending to extracted addresses
fix: labeling shielding txs
fix: autoshield endless loop
fix: autoshield t addr not firing
fix: autoshield destinations
chore: remove old routes for rescan with zkool
other minor fixes/cleanups
* fix: zcash hardfork
* fix: update sync progress more reliably
* fix: pending transaction loading
fix: autoshield txs
fix: taddress
fix: fee estimation
fix: tx send errors
* chore: bump zkool2 to latest version
fix: reduce amount of taddrs generated
fix: derivation path for internal wallets
fix: display address in correct hidden/usable spots
fix: get wallet db height before it syncs for the first time
fix: taddr rotation with passphrase
fix: sync progress ui refresh
fix: taddress generation not getting capped
fix: hidden addresses not being hidden
fix: pending transactions not being shown
fix: t address cache misses
fix: t address rotation not getting refreshed
fix: t address high index not being used
* fix: refresh t addresses
* fix: patch rust side to make t addr rotation work
* fix: ui issue in recipient address
fix: zcash multiaddress send to show in the ui
fix: potential race condition
* minor fixes
* format
* fix: flashing on receive screen
* remove unused 'autoShield'
* review
* feat: add ExchangeRate class for currency conversion with tests
* docs: add detailed comments to ExchangeRate class
* refactor: rename `baseCurrency` to `base` in `ExchangeRate`
* auto-reformat
---------
Co-authored-by: Robert Malikowski <malikowskirobert@gmail.com>
Co-authored-by: Omar Hatem <omarh.ismail1@gmail.com>
* add prepaid range support for CakePay cards
* use selected denomination for order creation
* fix Flexible widget issue
* forces to use prod api
* auto-reformat
* fix the input string format [skip ci]
Co-authored-by: Omar Hatem <omarh.ismail1@gmail.com>
* fix the value string format [skip ci]
Co-authored-by: Omar Hatem <omarh.ismail1@gmail.com>
* fix the nextamount string format
Co-authored-by: Omar Hatem <omarh.ismail1@gmail.com>
---------
Co-authored-by: Robert Malikowski <malikowskirobert@gmail.com>
Co-authored-by: Omar Hatem <omarh.ismail1@gmail.com>
Remove the extra GitHub issue contact link that pointed to a broken Discussions category.
The repository already has a working Feature request issue template, so the duplicate
Feature or Enhancement Request contact link created a confusing entry in the issue
creation modal and led users to a failing GitHub Discussions URL.
