WalletConnect is an open protocol to communicate securely between Wallets and Dapps (Web3 Apps). The protocol establishes a remote connection between two apps and/or devices using a Bridge server to relay payloads. These payloads are symmetrically encrypted through a shared key between the two peers. The connection is initiated by one peer displaying a QR Code or deep link with a standard WalletConnect URI and is established when the counter-party approves this connection request. It also includes an optional Push server to allow Native applications to notify the user of incoming payloads for established connections. The plugin helps you to connect your existing wallet to the Web3 Apps in order to send transactions in the currently opened sessions.
Hello @levon@ZeroqodeSupport - the WalletConnector only opens ETH Wallets. Even if I try a BTC provider (example: bitcoin.com wallet), an ETH wallet is trying to be selected.
Is there a way to enable the BTC network?
Thanks
Hi @segongora9, thanks for your question.
We’ve passed it to the developer team for research. Once any feedback will appear, we will let you know asap.
Regretfully, the developer team was not able to reproduce the above-mentioned issue. Please share a bit more details (used device, used application, and any details you consider important) about your case, it will allow us to find any issue much faster.
Hi @segongora9, thanks for the shared information.
We’ve passed it to the developer team for research. Once any result will appear, we will let you know asap.
Hello @ZeroqodeSupport - any updates on this? I’ve been progressing on other parts of the app but no luck with this and it’s critical for the client’s app!
The problem is that this wallets, which drops this error, doesn’t support wc v2.
Please see the list of supported wallets (it is slowly expanding, and probably required wallets will be added too).
We have tested the WalletConnect plugin on our demo page, and it is functioning as expected. Could you please ensure that the plugin is configured in the same way as shown on our demo page?
You can access the demo page and documentation here for reference:
Hello. When I try to send some transaction using code of token contract, trustwallet trys to sign a smartcontract, but not to send tokens. Metamask works correctly, but not TrustWallet. Same on your demo-page.
We have divided the answer into several parts to make it easier to understand:
1)We found that issue on our demo page that you mentioned with TrustWallet and have already passed that information on to the development team. As soon as we have a response from them, we will definitely get back to you.
2)Regarding the error you are seeing, please follow this link (Screenshot) and configure your domain(All domains must be enabled).
We have some additional questions regarding your setup and we would be happy to help you resolve any issues. Would it be possible for you to add our Support Team email to the list of collaborators in your application and provide us with a link to your app? This will enable us to check your settings and reproduce them on our side to identify the issue.
To add our Support Team as a collaborator, please follow these steps in the Bubble Editor:
Settings > Collaboration > Add email support@zeroqode.com.
Please note that you may receive a warning message regarding the plan, but since Zeroqode is on an Agency plan, you can easily add us to your collaborators.
Thank you for your time and we look forward to hearing back from you soon.
We’ve divided our answer into several to make it easier to understand:
When I try to send some transaction using code of token contract, trustwallet trys to sign a smartcontract, but not to send tokens
We are excited to share that we have effectively resolved the issue with the WalletConnect - All Crypto Wallets Plugin action and have updated it to version 1.45.0 :
-Metamask+Web3+WC : Fixed “Eth Sign type data” and “Send Transaction with Contract Address” actions - WalletConnect
-WalletConnect: Fixed “Eth Sign type data” and “Send Transaction with Contract Address” actions.
Could you kindly update the plugin within your app to this latest version and confirm whether everything is now operating smoothly?
Feel free to explore the plugin’s functionality on our demo page.
Add a support team a s collaborator
Thank you, we have received your application, our developers will check it soon and I will get back to you with a response
Your update does not work correct. Now in every wallet if you use any coin contract it sends only original token of chain. And it’s same in your demo page. For example i put address of usdt and it initiated payment in eth. And now it works same not only in trust, but in metamask as well.
We checked your application and sent you video in DM where you can see that other wallets accept tokens correctly. Please check this video and let us know if everything works correctly, if not, then record us a little Loom video where you show us the problem you encountered.