Keplr Tells Social-Login Users to Stop Deposits as Balances Show Empty
新云社 reports: Keplr, the wallet most closely associated with the Cosmos ecosystem, has advised users who created accounts through Google or Apple sign-in to stop making deposits and to move any remaining liquid assets out, while indicating that an ongoing recovery effort may explain why some wallets are displaying empty balances. The guidance applies specifically to accounts provisioned through social login rather than to wallets created from a seed phrase.
The distinction matters. Social-login wallets abstract away the private key: the key material is derived from, or custodied on behalf of, an identity provider session and the wallet provider’s own infrastructure. That design is what makes onboarding painless, and it is also what makes recovery non-trivial. When the underlying session, encryption shard or derivation path needs to be rebuilt, the address a user sees can remain valid while the data needed to render its holdings is temporarily unavailable — producing the unnerving appearance of a zeroed-out portfolio.
Why ‘Empty’ Rarely Means ‘Gone’
On-chain balances are a property of the ledger, not of the interface. If a wallet shows nothing while the address still holds tokens, the likely failure is in the read path: key derivation, indexer queries or RPC endpoints. The corrective instruction to halt deposits follows the same logic. If a user is not certain which address their social-login account currently resolves to, a deposit could land at an address they cannot yet operate — recoverable in principle, awkward in practice.
Keplr’s framing of the incident as tied to a recovery effort is the reassuring reading, and it is also the one that warrants the most scrutiny. Recovery operations involve reconstructing key material, and that is precisely the moment when an address’s control surface changes. Users should verify that the address they see after recovery is the address they held before.
The Broader Lesson for Cosmos Liquidity
Cosmos has spent years competing on interoperability and on the quality of its wallet experience; Keplr is arguably the single most important consumer surface in that stack. Any perceived instability in its account model reaches further than one app. Validators, DEX operators and lending markets built on Cosmos chains inherit the same social-login cohort as customers, and those users are the least equipped to diagnose derivation problems themselves.
- For users: export or confirm your address independently before moving funds, and never deposit into an address you have not verified out-of-band.
- For protocols: monitor for anomalous withdrawal patterns from social-login cohorts and consider pausing deposit incentives aimed at them.
- For wallet providers: social login needs a visible recovery path with explicit, verifiable address continuity.
What to Watch Next
The credibility test will be documentation: a clear post-mortem identifying whether this was an indexer fault, a key-derivation regression or something more serious, plus confirmation that every affected address maps one-to-one onto its pre-incident counterpart. Until that lands, the prudent posture is the one Keplr itself recommended — no new deposits, withdraw what is liquid, and treat any address you cannot verify as hostile ground.





