Unable to sign outgoing transactions from main account after wallet creation
Hello Klever team and community,
We are reaching out about a technical issue with a Klever Wallet installation on Android that has resulted in funds being effectively inaccessible. We have already submitted a support ticket through the official channel and are creating this thread to document the situation publicly and in case anyone in the community has encountered something similar.
Brief description
A wallet was created through the standard flow in Klever Wallet for Android in January 2026. After receiving incoming transfers without any issue, the first outgoing transaction could not be signed by the application. The funds remain visible on the blockchain, the balance is correctly displayed in the app, but no transaction can be sent from the main account.
What we observed during diagnostics
The Reveal Private Key function for the main account returns an empty field — nothing is displayed, nothing is copied. We have a video demonstrating this.
The seed phrase exported through the standard Backup Wallet function does not regenerate the main account address. We tested this on the client’s local machine with thousands of derivation variants. However, the same seed phrase correctly regenerates a second account in the same wallet (a test account that was created later). This indicates the seed phrase is authentic and belongs to this installation — it just does not produce the main account.
Two observations from the user
First, the wallet generation took unusually long during initial setup — noticeably longer than expected. The user attributed this to network conditions at the time.
Second, when revealing the seed phrase via the “reveal secret” button, the display has a “shaking” visual effect that the user had not seen in earlier Klever versions.
What we are asking
We are not sharing any sensitive data publicly or with anyone, including support — no seed phrase, no backup file, no password, no private keys. This is consistent with Klever’s own security policy.
We are asking the Klever team, through the official support ticket, to investigate on their side: review the application release that was in production at the time of wallet creation for any known issues with the wallet creation flow or local key storage, check whether any server-side data exists from that installation session, and if possible provide a diagnostic tool that the user can run locally on their device without transferring sensitive information.
Questions for the community
Has anyone encountered a situation where Reveal Private Key returns an empty field for a wallet created directly in the app, while still showing the correct balance and accepting incoming transfers?
Has anyone noticed unusually slow wallet generation in early 2026 builds, or the “shaking” effect during seed phrase reveal?
Any insight would be appreciated. We will update this thread as the situation develops.
Thank you.