chore: block PYR bridging on mapped and default tokenlists - #843
Merged
Conversation
Tag PYR Token (0x430ef9263e76dae63c84292c3409d61c598e9682) with noDeposit and noWithdraw so it is no longer bridgeable via Portal. The default (popular) list is tagged as well as the mapped list. Consumers key tokens by chainId + originTokenAddress and prefer the popular list entry, discarding the mapped one when both are present, so tagging the mapped list alone would have had no effect. All three wrapped tokens on the default list are covered (pos, lxly and agglayer) so every bridge route is closed, not just PoS.
py-zoid
marked this pull request as ready for review
August 16, 2026 11:48
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
1 participant
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.
What
Tags PYR Token (
0x430ef9263e76dae63c84292c3409d61c598e9682) withnoDepositandnoWithdrawso it is no longer bridgeable.mappedTokens.jsonposdefaultTokens.jsonpos,lxly,agglayerWhy the default list is included
Consumers key tokens by
chainId+originTokenAddress, which is identical for this token in both lists. The popular/default list is processed first and its entry takes precedence — the mapped entry is discarded when both are present.Tagging
mappedTokens.jsonalone would therefore have had no visible effect. The default list is tagged as well so the block actually applies.All three wrapped tokens on the default list are covered so every bridge route is closed, not just PoS.
Scope
Staging lists (
mappedTokensStaging.json,defaultTokensStaging.json) are intentionally left unchanged in this PR.Verification
npm run lint— cleannpm run test-all— 3 passingnpm run build— regeneratesmapped.tokenlist.jsonandpopular.tokenlist.jsonwith the new tagsNote on base branch
Opened against
masterbecause both deploy workflows (ecs_prod.yml,deploy_gcp.yaml) trigger onmaster. The repository default branch isdev, which has diverged frommaster— this change will not reachdev.