fix(tokens): correct withdrawal pairs and PT-DETH aliases - #317
Merged
Conversation
This was referenced Sep 3, 2026
essserrr
approved these changes
Sep 4, 2026
doomsower
approved these changes
Sep 4, 2026
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
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.
Summary
Compatibility
Tested legacy client main (1ca53dab) with SDK master candidate and client staging (ad810c1e) / current main (0184fa56) with SDK next conventions. Current client main has migrated to SDK next.
Static aliases do not fix unresolved phantom symbols intercepted by UI-kit. Companion SDK changes resolve legacy icons by address on master and load historical withdrawal metadata on next; those SDK changes must be released and consumed by clients. Publish these assets first.
Validation
Limits
Not claiming complete deployed multichain coverage: the broader audit encountered Base/WorldChain RPC or deployment errors and incomplete legacy snapshot chains. These do not invalidate the focused icon checks; post-release live verification is still required.
SDK companion PRs: Gearbox-protocol/sdk#502 (master), Gearbox-protocol/sdk#503 (next).