-
Notifications
You must be signed in to change notification settings - Fork 8
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
Hotfix/1.11.6 #1338
Hotfix/1.11.6 #1338
Conversation
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
…definition address points to another. This stems from an old bug on VerifyDAppsUseCase were a dApp was always verified when dev mode was enabled. It was later fixed to always verify the network id of that dApp is the same with the current network id.
/** | ||
* Simple extension on `ProfileNetwork` that filters out dApps with dAppDefinitionAddress | ||
* on another network. All AuthorizedDApps are supposed to be under the same `ProfileNetwork::networkId` | ||
* but due to an old bug that was later fixed on `VerifyDAppUseCase`, there seems to be some profiles that | ||
* have authorized dApps with dApp definition address pointing to another network. A user with | ||
* **Developer Mode ON** could "verify" any dApp and store it in profile. | ||
*/ |
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.
good that you added an explanation there, thanks!
# Conflicts: # app/src/main/java/com/babylon/wallet/android/presentation/ui/composables/assets/StakingTab.kt # core/src/main/java/rdx/works/core/sargon/ProfileExtensions.kt
|
Description
Addresses three fixes:
Estimated
label on NFTs that are classified as predicted in tx analysis, in both non fungible collections and in stake claimsAmount of deposit is unknown