Here is an article based on the information provided:
Metask and Trust portfolio: Understanding the problem with the Web33 transaction
Recently, the world of cryptocurrencies has undergone rapid development, many users move from traditional portfolio services, such as Bitcoin or Elektro’s portfolio, to more advanced solutions such as Metaments and the Trust wallet. Both platforms have taken significant steps in ensuring a perfect impression for users to interact with decentralized applications (DAPP) on blockchain Ethereum.
Recently, however, I encountered a problem in which my WEB3 transaction worked well over Metask, but not on Trust Portlelet. In this article we will deepen why this can happen and give a possible solution.
Problem: Various eters
When it comes to interaction with DAPPS to blockchain ethereum, users often have to use the API Ethreum Web3 (Web3) interface to send transactions or interact with intelligent contracts. API WEB3 is a standard interface for access to the Ethereum virtual car (EVM), which allows programmers to build and implement DAPP.
In Metask, the browser extension has been optimized to perfectly work with the API WEB3 interface, enabling users to access EVM without having to download additional software. However, when I tried to use the trust portfolio, another portfolio service that also uses the API WEB3 interface, my transactions began to fail.
solution: Ethers Library Research
To identify the problem, I decided to investigate the library “Ethers.js used both by metamans and Portlelet Trust. After analyzing the code, I noticed that the ‘Web3.etha’ object was replaced by another instance of the API WEB3 interface using the Window.Web3 ‘variable.
Here is the extract from my code:
`Javascript
if (window.ethereum) {
Window.web3 = new web3 (window.ethereum);
}
The code line that caused the problem is the one in which we replaced the library “Ethers.js” with another instance using ‘Window.web3’.
Application
To sum up, the problem is how Metask and Trust Wallet deal with API Web3. While Metask uses a different speech of the API WEB3 interface than a trusted wallet, this cannot be enough to ensure an excellent interaction between two platforms.
To solve this problem, it is recommended to use a uniform approach to access to EVM with both Metask and a trusted wallet. The possible solution is to create a facility made available “Window.web3”, which can be used on both platforms.
Recommendations
- To avoid similar problems in the future, consider using a single API WEB3 interface in the entire application.
- If you need to support more portfolio services, make sure that each service uses a different API3 Web3 instance.
- Consider using a library such as’ Ethers.js, which allows more flexible and normalized access to EVM.
By taking these steps, you can make sure that your DAPPS interacts without problems with Metas and trustworthy, without problems related to the web3 transaction.