feat(tokens): add USDT0 on Optimism#35
Merged
Merged
Conversation
Adds the canonical Optimism USDT0 (0x01bFF41798a0BcF287b996046Ca68b395DbC1071) as USDT0-optimism and bumps the list to 1.7.0. Without this entry, cross-chain payments funded with USDT0 on Optimism fail after a successful LiFi quote with 404 "Invoice currency not found", since the currency isn't in the list. Legacy USDT-optimism is already present. REQ-190 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
MantisClone
marked this pull request as ready for review
July 8, 2026 15:04
rodrigopavezi
approved these changes
Jul 8, 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.
Problem
Cross-chain payments funded with USDT0 on Optimism fail on the secure payment page. After the LiFi quote succeeds, request-api's
getTokenList()lookup 404s with"Invoice currency not found"because USDT0 is not in this token list — only legacyUSDT-optimism(0x94b008aA…) is registered. USDT0 (0x01bFF41798a0BcF287b996046Ca68b395DbC1071) is now the canonical Optimism USDT, and REQ-190 added it to request-api's routing map, but the currency registry (this list) was never updated.Refs REQ-190. Pairs with RequestNetwork/request-api#1065 (which surfaces + resolves USDT0 as a cross-chain source).
Proposed Solution
Add
USDT0-optimismtotokens/token-list.json(mirroring the existingUSDT-optimismentry) and bump the list minor version 1.6.0 → 1.7.0.{ "id": "USDT0-optimism", "name": "USDT0", "symbol": "USDT0", "decimals": 6, "address": "0x01bFF41798a0BcF287b996046Ca68b395DbC1071", "network": "optimism", "type": "ERC20", "hash": "0x01bFF41798a0BcF287b996046Ca68b395DbC1071", "chainId": 10 }npm run validate→ "Token list is valid!" andnpx vitest run→ 11/11 pass.Considerations
idisUSDT0-optimismto match what request-api'sresolveSourceCurrencyIdproduces.deploy.ymlregenerateslatest.json), request-api picks it up after its token-list cache expires — so it's not instant on staging/prod.tokens/assets/if preferred.UAT
On staging, open a USDC-on-Base request and pay cross-chain from a wallet holding only USDT0 on Optimism → selecting USDT0 now returns a quote and proceeds (previously 404'd after the quote).