Title: LOCK METAMASK: UNLIMPLY Otken Erc20 into Net Beap-20 from Oshbak
Edit
As a frequent policeman of the Metamask platform, I write this one to shoot a scoop that has been in the middle of Avgusta. The problem is connected with the token Erc20 (BeP-20) from my main Koshka Testnet in the second mate with Metamask. This problem has released significant non -discharge and reproaching, especially with my two -month experience with the platform.
Problem
The context of this is the sight of the pore, but I have a few symptoms, which can be relevant:
1.
- No Historia Passt : When I ask you to dry the history or transaction of the journal, there is no recording about any -liking transplant.
3.
Simptomas and Shagi
To shoot this problem, I will be dusted these shagies:
1.
- Auzed Posts Pople : Recontex that the place of the pole is drawn with the last balances of the tokens.
3.
Examination and Battle
After conducting the study, I have fallen that this problem can be connected with the existence in the Ethereum (ERC-20) or in the realization of metamask. One of the opportunities are the sake of the transition in the chart of Bep-20 from the melted client Koshelka or the non-positive configuration.
Construction and follow -ups
To solve this problem, I recommend the following:
- LOOK Your Metamask : Receive that you use the Metamask platform.
- verify the network : verify, rightly set your ethereum network for Bep-20.
3.
4.
the last thought
Well, I have started it with this unborn scoop, it is important to understand that the blockchain platform is developed and included. The follow -up of this is a shague and enormous for help, when it is necessary, you can resolve similar problems on the Metamask platform.