Metamask: Web3 Transaction works on Metamask but not on Trust wallet

05 Feb Metamask: Web3 Transaction works on Metamask but not on Trust wallet

Here is an article based on the information you provided:

Metamask and Trust Wallet: Understanding the Problem with Web3 Transactions

Recently, the cryptocurrency world has seen rapid growth, with many users moving from traditional wallet services like Bitcoin Wallet or Electrum to more advanced solutions like MetaMask and Trust Wallet. Both platforms have made significant strides in providing users with a seamless experience when interacting with decentralized applications (dApps) on the Ethereum blockchain.

However, I recently encountered an issue where my Web3 transaction worked fine on MetaMask, but not on Trust Wallet. In this article, we will explore why this might be happening and offer a potential solution.

The Problem: Different Ether

When it comes to interacting with dApps on the Ethereum blockchain, users often need to use the Ethereum Web3 API (Web3) to send transactions or interact with smart contracts. The Web3 API is a standard interface for accessing the Ethereum Virtual Machine (EVM), allowing developers to build and deploy dApps.

On MetaMask, the browser extension has been optimized to work seamlessly with the Web3 API, allowing users to access the EVM without downloading any additional software. However, when I tried to use Trust Wallet, another wallet service that also uses the Web3 API, my transactions started to fail.

The Solution: Investigating the Ethers Library

To identify the problem, I decided to investigate the ethers.js library used by MetaMask and Trust Wallet. After analyzing the code, I noticed that the web3.eth object was replaced by another instance of the Web3 API that used the window.web3 variable.

Here is an excerpt from my code:

if (window.ethereum) {
window.web3 = new web3(window.ethereum);
}

The line of code that caused the issue is the one where I replaced the ethers.js library with another instance that uses window.web3.

Conclusion

To summarize, the problem lies in the way MetaMask and Trust Wallet handle the Web3 API. Although MetaMask uses a different instance of the Web3 API than Trust Wallet, this may not be enough to ensure seamless interaction between the two platforms.

To resolve this issue, it is recommended to use a unified approach to access the EVM from MetaMask and Trust Wallet. One possible solution is to create a common window.web3 object that can be used on both platforms.

Recommendations

• To avoid similar issues in the future, consider using a single instance of the Web3 API throughout your application.

• If you need to support multiple wallet services, make sure each service uses a different instance of the Web3 API.

• Consider using a library like ethers.js, which allows more flexible and standardized access to the EVM.

These steps will help you ensure your dApps interact smoothly with MetaMask and Trust Wallet without any issues related to the Web3 transaction.