-
Notifications
You must be signed in to change notification settings - Fork 1.2k
feat(qt): warn when sending to duplicate recipients #7015
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Conversation
|
WalkthroughThe PR changes duplicate-address handling during send operations. In walletmodel.cpp the duplicate-address check is moved to occur after fee computation/absurd-fee validation rather than before balance/fee checks. In sendcoinsdialog.cpp, when a DuplicateAddress prepare status is returned the UI now shows a confirmation dialog and only aborts the send if the user declines; other non-OK prepare statuses still abort immediately. Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20–30 minutes
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
please rebase to fix: https://github.com/dashpay/dash/actions/runs/19746402134/job/56581519530?pr=7015 |
Handle DuplicateAddress as a warning status instead of an error. Show a confirmation dialog when duplicates are detected, allowing the transaction to proceed if the user confirms. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
nmarley
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍. I like it better than #7012
PastaPastaPasta
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK e14aaa0
Issue being fixed or feature implemented
Having duplicated recipients is ok on protocol level, we could be less restrictive in GUI.
Inspired by #7012
What was done?
Handle
DuplicateAddressas a warning status instead of an error. Show a confirmation dialog when duplicates are detected, allowing the transaction to proceed if the user confirms.How Has This Been Tested?
Run dash-qt, send a tx
Breaking Changes
n/a
Checklist: