Replies: 2 comments 1 reply
-
|
Hi @antoinedc, |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
any update on this? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
What problem does this new feature solve?
I'm building a block explorer as a service (https://tryethernal.com), and customers can host their explorer on their own subdomain.
This explorer includes a contract interaction part, where users can send transactions through the UI.
At the moment, the only way to connect a wallet is through Metamask.
I can't switch to WC because I need to manually whitelist every domain, and this would slow down the process of setting up an explorer considerably if I need to do that when a customer adds a new domain.
An alternative would be to ask the customer to create WC account and copy/paste the verification code, but that isn't an ideal UX.
Describe the solution you'd like
Ideally, I'd like to have an API that I can send a new domain to, and that returns the verification code.
On my end, I'll be able to generate a dynamic /.well-known/walletconnect.txt file with all the verification codes.
Beta Was this translation helpful? Give feedback.
All reactions