Cannot deploy contracts using WalletConnect
See original GitHub issueWe planned to enable support for WalletConnect V1 today. Everything seemed to be working properly, connection is established, prompts come up.
However, when trying to deploy a contract to a network, we get the error Invalid ENS Name
with regard to the tx.to
field because for contract creation transactions the tx.to
field is a blank string (instead of null
which I believe it should be).
Please change this so that we can support users deploying contracts using WalletConnect.
Issue Analytics
- State:
- Created a year ago
- Comments:7
Top Results From Across the Web
Remix IDE now has a plugin for WalletConnect | by Rob Stupay
Connect a mobile wallet to Remix IDE with the new WalletConnect plugin ... Remix Desktop users can now deploy a contract to a...
Read more >Web3 client can't write to contract in Flutter app using ...
Solved! Just deploy the contract instead of running it locally on your machine. I was basically trying to make a transaction to a...
Read more >WalletConnect How to Connect your dapp with ... - YouTube
Join Pedro Gomes of WalletConnect for a workshop titled, "How to Connect your dapp with ... Your browser can't play this video.
Read more >Create, Deploy and Mint Smart Contract (ERC-721) with ...
We will create ERC-721 smartcontract, deploy to Goerli with Hardhat + Solidity. For minting we will use NextJs + WalletConnect + Web3Modal.
Read more >Deployed Smart Contract To Remix ,Can't find launched smart ...
Try going to the "Activity" section of your MetaMask. There should be an entry that reads something like "Contract Creation" which you can ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you for everyone’s hard work on this. Closing the issue as I’ve just successfully deployed a contract with 1.7.8.
I’m testing V1.7.8 that has just been released, if it fixes this problem, I will close the issue.