chore: update copies for multiple chains #864
Open
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.
Chore: Update Copies for Multiple Chains
Description
This PR addresses user feedback regarding a confusing and Ethereum-centric user experience when minting tBTC from non-EVM chains like Sui and StarkNet. Previously, the interface used language and linked to contracts specific to Ethereum, even when a user had a Sui or StarkNet wallet connected. This created uncertainty and could lead users to abandon the process.
To resolve this, we've introduced a dynamic, chain-aware UI that adapts its language and links based on the user's connected chain, providing a more inclusive and clear experience for all users.
Changes Made
New Utility (
src/utils/chainTextUtils.ts
):getChainDisplayInfo
, to provide chain-specific copy for labels, tooltips, descriptions, and more. This avoids scattered conditional logic and keeps the copy in one manageable place.Provide Data (
src/pages/tBTC/Bridge/Minting/ProvideData.tsx
):Make Deposit (
src/pages/tBTC/Bridge/Minting/MakeDeposit.tsx
):Initiate Minting (
src/pages/tBTC/Bridge/Minting/InitiateMinting.tsx
):Minting Timeline (
src/pages/tBTC/Bridge/Minting/MintingTimeline.tsx
):