-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: correct return of chain when connecting to bitcoin #3450
Conversation
🦋 Changeset detectedLatest commit: c37b34d The changes in this PR will be included in the next version bump. This PR includes changesets to release 18 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Coverage Report
File Coverage
|
case 'bitcoin:mainnet': | ||
return chain.caipNetworkId === bitcoin.caipNetworkId | ||
case 'bitcoin:testnet': | ||
return chain.caipNetworkId === bitcoinTestnet.caipNetworkId | ||
default: | ||
return chain.caipNetworkId === chainId |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wallet standard has a different set of ids?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, they use these aliases and not exactly caip-2
Description
Fix the chainId response when connecting to bitcoin with multichain adapters.
Type of change
Associated Issues
For Linear issues: Closes APKT-xxx
For GH issues: closes #...
Showcase (Optional)
If there is a UI change include the screenshots with before and after state.
If new feature is being introduced, include the link to demo recording.
Checklist