Ethereum: A problem with a safe version of CLI
We have experienced problems with a safe address currently related to the Binance Smart Chain (BSC) account. In addition, there is a threat to the safe version of the CLI we use for Ethereum operations.
error message
The error message shown in our tests to use safe CLI, was:
`
Error: could not import Ethersafe_Token. Is the ether updated?
`
This shows that there are problems with the Ethersafe_Token library, which is part of a safe cli. Specifically, version 3.4.1 seems to have compatibility problems.
Solution
To solve this problem, we took the following:
- Updated Ethersafe_Token Library in version 3.5.0.
- Changed our secure address from BSC to Ethereum (ETH).
- RAN
NPM Ethers and NPM implements the Ethers-Safe-token catalog project.
NEW Error Message
After renewing libraries, we encountered a new error message:
Error: could not import Ethersafe_Token. Is the ether updated?
at ./node_modules/ethers-safe-token/index.js (module './ethersafe_token/index.js')
at ./node_modules/@types/ethers_safe_token/ypes/index.ts (modulis'
`
This error message indicates that there is another compatibility problem with Ethersafe_Token Library. We have updated our secure address for Ethereum and Project Catalog to install NPM installation.
The final solution
To solve this new problem, we started as follows:
- Updated Ethersafe_Token Library in version 3.6.0.
- Renewed with a safe CLI with an updated Ethersafe_Token Library.
- Rano's NPM Link project catalog.
By renewing our libraries and re -connecting safe CLI, we were able to solve problems with the current safe version of CLI.
###'S conclusion
In the safe CLI, we encountered two separate compatibility problems with the Ethersafe_Token Library. By updating our libraries into compatible versions and re -connecting safe CLI, we can solve these problems and continue to use safe CLI ETHERUM operations.