Ethereum: From CL CLAVE
We have encountered problems with our secure address, which is currently associated with the Binance Smart Chain (BSC) account. In addition, a safe version of CL CL, which we use for Ethereum transactions, has been endangered.
error message
The error message displayed during our attempt to use in a safe condition was:
`'
Error: I couldn't import "ettersafe_token". Are the “Etters” up to date?
'
This suggests that there is a problem with the library of Ettersafe_token, which is part of a safe condition. More specifically, it seems that version 3.4.1 has compatibility problems.
solution
We have taken the following measures to resolve this problem:
- Update of ETHERSAFE_TOKEN in version 3.5.0.
- Changed our safe address BSC in Ethereum (ETH).
- RunNPM Install Ethers
and" NPM Install ethers-security "in the project repertoire.
a new error message
After updating the libraries, we met a new error message:
'
Error: I couldn't import "ettersafe_token". Are the “Etters” up to date?
AT
to ./node_modules/@types/ethers_safe_token/types/index.ts (in the module './ethers-safe-taken/types/index.ts')
'
This error message suggests that there is another problem of compatibility with the Library of Ettersafe_Token. We have updated our secured address in Ethereum and performed "NPM installation" in the project directory.
The final solution
We have taken the following measures to resolve this new number:
- Update Library of Ettersafe_Token in version 3.6.0.
- Connected CL Clir to the Library of Ettersafe_Token.
- Runnpm link ‘in the project repertoire.
By updating our libraries and the rehabilitation of CL, we managed to solve problems with the current version of CL CL.
Conclusion
We have encountered two separate compatibility problems with the ETRARSAFE_TOKEN library in a safe CLI. By updating our libraries in compatible versions and the re -education of a safe state, we are able to solve these problems and continue to use Ethereum transactions.
Leave a Reply