Enhancement: Fee Payment with Sufficient Assets #11336
Merged
Conversation
This file contains 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 pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
📝 Description
In PR#11229, support for paying fees with Sufficient Assets was introduced. However, this functionality currently only applies to transferring system assets.
Now, it's a good time to extend this feature to all possible areas where users can submit transactions. To achieve this, we will move the Fee Asset dropdown from the
Transfer Modalto theAuthorize Transaction Modal. This change will ensure that users can select a fee asset for almost all the transactions they sign.🚀 New behaviour
Screen.Recording.2025-02-26.at.16.07.37.mov