Repository navigation
Flag HyperEVM wpUSDT as reported (extensions.reported) - #440
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
What
Adds wpUSDT (Peaches USDT, HyperEVM
0xD8d5…e93f) with"reported": true, so the app warns onPT-wpUSDT(USD₮0)-2026/11/10. The token wasn't in the list, so this is a new entry rather than a one-key change like #434.Why
The vault reports 3,675 USD₮0 in
totalAssets(), but redeeming one share returns 0.0067 USD₮0 (previewRedeem(1e6)is 6733). The market is still listed, and only Add Liquidity shows a warning today.Why the entry has so few fields
extensions.underlying, please keep it out. The app's pool creation offers any token that has it, so setting it would make wpUSDT selectable as an IBT for new pools. The flag doesn't need it.logoURI. The schema doesn't require one, and the market has no logo today.Verification
token-validation.yml(ajv 6, allErrors): tokens 393/393, wrappers 114/114, protocols 1/1 valid.npm run buildcompared withmain:spectraTokensgains this one entry and nothing else changes. Wrappers and protocols are identical./v1/avalanche/poolscarryibt.extensions.reported.compileFutureData.spec.tscovers an entry with only this extension.After merge
No API or app release is needed. tokens.spectra.finance updates after the usual publish and deploy hook, then the API picks it up when its token-list cache refreshes, within about an hour.
Please merge it on its own: back-to-back merges collide in the version-bump job.
🤖 Generated with Claude Code