fix: Virtuals chain detection (tokens now deploy on Robinhood too) - #1439
Merged
Conversation
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.
Problem
Virtuals Protocol has expanded to Robinhood chain. The
FetchVirtualsTokensfetcher was hardcodingchain=basefor all tokens. The Virtuals API now returns achainfield (e.g.ROBINHOOD,BASE) but we were ignoring it, so Robinhood-deployed Virtuals tokens were being probed on Base → 0.8% coverage across all EVM providers.Fix
chainfield from the Virtuals API responsechainSlug()helper to mapROBINHOOD/BASE/BSC/SOLANAto our internal slugs, defaulting tobasefor unknown valuesAlso included