feat(wallets): Support multiple wallets #4678
Merged
+796
−208
Conversation
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
floganz
force-pushed
the
feat-multiple-wallets
branch
from
3d22587 to
ae0327e
Compare
annvelents
approved these changes
Dec 5, 2025
Contributor
annvelents
left a comment
annvelents
left a comment
There was a problem hiding this comment.
left couple of small comments
floganz
force-pushed
the
feat-multiple-wallets
branch
from
806db97 to
4d6ee86
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
We’re introducing the priority field to wallets to support custom execution or display ordering. This PR builds on the base work from #4391, which added the field to the Wallet model and exposed it via the API.
The goal of this PR is to implement the logic that uses the priority value when handling wallets — for example, when determining which wallets to apply or process first.
Description
This PR includes:
• Logic to order wallets by priority (and created_at as a secondary key).
• Ensures active_wallets_in_application_order returns wallets in the correct priority sequence.
• Updates any internal wallet processing to respect the defined order.
This builds directly on the foundation laid in PR #4391 and assumes the priority field and its validations are already in place.