Why is the private key and seed phrase from Klever Wallet not imported into other wallets and why is the private key and seed phrase from other wallets not imported into Klever Wallet? What’s wrong with Klever Wallet?
-
The private key (BTC, SOL, APT, SUI and other blockchains) from Klever Wallet is not imported into other wallets. Also, the private key from other wallets is not imported into Klever Wallet. In both cases it says that the private key format is incorrect. Only the private key of the ETH and EVM network are imported, respectively, because the key is the same.
-
Seed phrase (BTC, SOL, APT, SUI and other blockchains) from Klever Wallet is not imported into other wallets. Also, the private key from other wallets is not imported into Klever Wallet. Wallets do not see imported blockchains and create new addresses when importing a seed phrase. Imported only by seed phrase ETH and EVM network, respectively.
With this private key or seed phrase, for example from Exodus, it is easily imported into the same TrustWallet or Atomic and from Atomic is easily imported into the same Exodus or TrustWallet.
What’s wrong with Klever Wallet and why are there such problems with importing private keys and seed phrases? This raises great concerns about the security of user funds. If something happens to Klever Wallet, inexperienced users simply will not be able to recover their funds in many other wallets.
This affected the same USDT on the Solana network - it turned out that USDT users were blocked indefinitely while tests were being carried out. And inexperienced users cannot import a private key from the Solana network, because it does not fit many third-party wallets, and recovery using a seed phrase is also impossible, because many third-party wallets do not restore the Solana address and create a new address when importing the seed phrases.
This is a very serious problem and puts users’ funds at risk. I would like to hear the development team’s response.