-
Notifications
You must be signed in to change notification settings - Fork 411
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
feat: block/warn about bridges accordingly #2652
Conversation
Branch preview✅ Deploy successful! https://wc_bridge_warnings--walletweb.review-wallet-web.5afe.dev |
ESLint Summary View Full Report
Report generated by eslint-plus-action |
@@ -0,0 +1,43 @@ | |||
const DangerousBridges = [ |
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.
Naming-wise, there's nothing dangerous/risky about these bridges per se, it's just that they aren't smart contract account-friendly. Please find more specific, non-sensationalistic, names for the two arrays. And please move these lists (not the two functions below) to src/components/walletconnect/constants.ts
.
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.
Addressed in 398638f.
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.
Looks good apart from my comment 👍
What it solves
Resolves blocks/warns of risky bridge use
How this PR fixes it
The usage of certain bridges are either blocked or warned about, requiring user acceptance according to our research.
How to test it
Open one of the bridges specified and observe either a blocked connection window, or a warning that needs to first be accepted.
Screenshots
Checklist