-
Notifications
You must be signed in to change notification settings - Fork 537
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
Add verify.walletconnect.org to frame-src #1532
Conversation
Currently both WalletConnect and Rabby (which apparently uses WalletConnect) are broken on base.org. As a result, the BitBox02 hardware wallet is currently unusable with base.org. I see blocked requests to both verify.walletconnect.com and verify.walletconnect.org to the same URL path; [apps/base-docs/server.js][0] only uses the latter, so I’m assuming only one of them is needed and updated this to match. [0]: https://github.com/base-org/web/blob/9beb94e4201224dea6234d2a061c9855f5133fd1/apps/base-docs/server.js#L436
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@mrdomino is attempting to deploy a commit to the Coinbase Team on Vercel. A member of the Team first needs to authorize it. |
🟡 Heimdall Review Status
|
@mrdomino I was able to use WalletConnect on base.org just now, without merging these changes. could you clarify the issue here? |
I was able to as well! I don’t know what changed. |
@mrdomino hmm, not sure, perhaps some sort of rabby / walletconnect issue. For now I'm going to close this out, but please let me know if you see again. Thanks! |
Currently both WalletConnect and Rabby (which apparently uses WalletConnect) are broken on base.org. As a result, the BitBox02 hardware wallet is currently unusable with base.org.
I see blocked requests to both verify.walletconnect.com and verify.walletconnect.org to the same URL path; I have added both and confirmed (by locally overriding the response header) that this works with Rabby.
Fixes #1531.