Ethereum: Problem with the safe version of Cli
We had problems with our safe address, which is currently linked to a Binance Smart chain account (BSC) (BSC). In addition, the safe version of the CLI we use for Ethereum transactions has been compromised.
The error message
The error message shown during our attempt to use the safe click was:
`
Error: It was not possible to import 'Ethersafe_token'. Are the 'Éters' updated?
This indicates that there is a problem in the Ethersafe_token library, which is part of the safe click. Specifically, it seems that version 3.4.1 has compatibility problems.
The solution
To solve this problem, we take the following measures:
- Updated the Ethersafe_token library for version 3.5.0.
- Change our BSC Safe address to Ethereum (ETH).
- RANNPM INSTALL EThers
ENPM Install-Token ‘in the project directory.
The new error message
After updating the libraries, we find a new error message:
`
Error: It was not possible to import 'Ethersafe_token'. Are the 'Éters' updated?
in ./node_modles/ethers-safe-teken/index.js (in the module '.
In ./node_modles/@types/ethers_safe_token/types/index.ts (in module './ethers-safe-ton/types/index.ts')
This error message indicates that there is another compatibility problem in the Ethersafe_token library. We update our safe address for Ethereum and executeNPM Installin the project directory.
The final solution
To solve this new problem, we take the following measures:
- Updated the Ethersafe_token Library for version 3.6.0.
- Read the safe client with the Ethersafe_token library updated.
- RANNPM Link` in the project directory.
When updating our libraries and withdrawing the safe client, we were able to solve the problems with the current version of Cli.
Conclusion
We find two compatibility problems separate with the Ethersafe_token library in the safe click. When updating our libraries for compatible versions and linked to a safe click, we can solve these problems and continue using the safe click for Ethereum transactions.