-
Notifications
You must be signed in to change notification settings - Fork 59
feat(platform-wallet): support DashPay shielded tips with dedicated accounts #4616
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
Open
PastaPastaPasta
wants to merge
6
commits into
dashpay:v4.3-dev
Choose a base branch
from
PastaPastaPasta:feat/dashpay-shielded-tips
base: v4.3-dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
4290e2b
feat(dashpay)!: support shielded tips with dedicated wallet accounts
PastaPastaPasta 4956dfa
fix(swift-example-app): expose shielded tip address storage
PastaPastaPasta 75e1592
fix(platform-wallet): harden shielded tip recovery and mobile error h…
PastaPastaPasta b02eb22
fix(platform-wallet): address shielded tip review findings
PastaPastaPasta 47e9e1b
Merge branch 'v4.2-dev' into feat/dashpay-shielded-tips
QuantumExplorer a637a0e
fix(platform-wallet): contain tip export panics and share the mobile …
QuantumExplorer File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
24 changes: 24 additions & 0 deletions
24
...nExampleApp/app/src/main/java/org/dashfoundation/example/ui/dashpay/ShieldedTipFailure.kt
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,24 @@ | ||
| package org.dashfoundation.example.ui.dashpay | ||
|
|
||
| import org.dashfoundation.dashsdk.errors.DashSdkError | ||
|
|
||
| /** | ||
| * Permit a fresh user review only for failures known not to have executed a tip. | ||
| * On the tip path, Rust maps selection/build/recipient-check failures to | ||
| * WalletOperation. Broadcast ambiguity maps to ShieldedSpendUnconfirmed, and | ||
| * successful post-broadcast bookkeeping is best-effort (never WalletOperation). | ||
| * Unknown exceptions, including JNI failures and cancellation, remain locked. | ||
| */ | ||
| internal fun canReviewShieldedTipAfterFailure(error: Exception): Boolean = when (error) { | ||
| is IllegalArgumentException, | ||
| is DashSdkError.InvalidParameter, | ||
| is DashSdkError.PlatformWallet.InvalidHandle, | ||
| is DashSdkError.PlatformWallet.NotFound, | ||
| is DashSdkError.PlatformWallet.SigningKeyUnavailable, | ||
| is DashSdkError.PlatformWallet.WalletOperation, | ||
| is DashSdkError.PlatformWallet.ShieldedNoRecordedAnchor, | ||
| is DashSdkError.PlatformWallet.ShieldedBroadcastFailed -> true | ||
| // ErrorInvalidParameter is a preflight-only FFI failure on this call path. | ||
| is DashSdkError.PlatformWallet.Generic -> error.nativeCode == 2 | ||
| else -> false | ||
| } |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
🟡 Suggestion: Invalidate the previous tip account when switching identities
Changing produceState's keys restarts its producer but does not reset its remembered value to initialValue. The active-identity branch remains in composition when selection changes, so identity A's successful account result remains available while identity B's asynchronous identityIndex lookup runs. The button and sheet consume that untagged result alongside the current wallet selection. If a dedicated-account send is confirmed during that window, ShieldedTipSheet captures the stale index as sendAccount; the Rust send API accepts an account rather than a sender identity and does not reject another bound account merely because it belongs to a different identity. Wrap the state in a composition key scoped to network, wallet, and identity, or return the lookup identity with the result and reject mismatches. Add a regression that pauses B's lookup after switching from A and verifies that A's account cannot be used.
source:
gpt-6-astra(phase2-reviewer: general)