Remove client-side migration and reorganize wallets #2572
Merged
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
supersedes
#2546(merged intomasteralready in #2585)#2553(merged already in #2584) #2552 #2554#2552 (comment):
#2554 (comment):
Additional context
For me personally, it is definitely better to just have one big PR because I know what I did and then I can resolve conflicts between commits immediately. If I want to use the web interface to review and document my changes, I can also push to my own repository and do it there.
The small PRs were mostly meant to make review easier, but since that is apparently not really the case, I now squashed every individual PR into one commit that I added here.
I hope that is better.
Checklist
Are your changes backward compatible? Please answer below:
yes
On a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:
tested PRs individually before
For frontend changes: Tested on mobile, light and dark mode? Please answer below:
n/a
Did you introduce any new environment variables? If so, call them out explicitly here:
no
Did you use AI for this? If so, how much did it assist you?
no
Note
Reorganizes wallets by moving provider/reducer into hooks, removing v1→v2 client migration, extracting crypto utilities, renaming DnD component, and updating imports/usages across the app.
WalletsProvider, state, and actions intowallets/client/hooks/global.js; removewallets/client/context/*(provider/reducer) and update all imports to@/wallets/client/hooks.useDeleteLocalWalletsanduseDeleteOldDb.global.js; emitKEY_STORAGE_UNAVAILABLE,WRONG_KEY,KEY_MATCHactions.deriveKey,encrypt,decrypt,generateRandomPassphrasetowallets/lib/crypto.wallets/client/hooks/passphrase.js; keep encryption/decryption/key APIs inwallets/client/hooks/crypto.js.components/draggabletocomponents/dndand update re-exports/consumers.indicator,diagnostics,payment,query,wallet) to use new global/crypto/logger/query modules and simplified imports.WalletsProviderfrom@/wallets/client/hooksinpages/_app.jsandpages/wallets/index.js; wire passphrase prompt and DnD reorder via new hooks.Written by Cursor Bugbot for commit e56a914. This will update automatically on new commits. Configure here.