chore: show chain not supported on rFOX claim #7617
Merged
Conversation
This file contains 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
NeOMakinG
approved these changes
Aug 26, 2024
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.
Description
As a follow-up (and inspired by) to #7600, this PR ensures we show the
<ChainNotSupported />component when connected to a wallet that does not support arbitrum.This PR:
develop:When attempting to stake FOX on Arbitrum without an Arbitrum account connected:
When attempting to stake FOX on Ethereum without an Arbitrum account connected (the bridge can never complete because there is no account to sign or pay gas on Arbitrum):
Issue (if applicable)
Follow-up of #7600
Risk
Small
rFOX staking.
Testing
<ChainNotSupported />component shows on the staking tab when an Arbitrum account is not connected.Engineering
☝️
Operations
☝️
Screenshots (if applicable)
See above.