Keplr Wallet Extension: Creating Custom Token Lists and Hiding Spam Assets

A user manages positions across six Cosmos-ecosystem blockchains—Cosmos Hub, Osmosis, Juno, and three others—and watches their token inventory grow to over fifty assets. Most are legitimate holdings, but several are test tokens from failed projects, airdrop spam, or scam attempts that somehow arrived in their wallet. The portfolio view becomes cluttered, making it harder to track actual value and easier to make mistakes during transactions. The solution is not to abandon the wallet or manually track assets elsewhere. It is to understand that the keplr wallet extension provides explicit tools for controlling which tokens appear in the interface and which remain hidden.

Token management in a non-custodial multi-chain wallet is a practical security and usability issue. By default, most wallets show every token balance on a chain, creating visual noise and occasionally hiding important holdings under less frequently checked tabs. A scam token with a name similar to a legitimate asset can cause users to approve wrong transactions or send funds to attacker-controlled addresses. The keplr wallet extension addresses this through visibility controls, custom token lists, and the ability to add or hide assets based on the user’s needs. Understanding these features separates a portfolio view that is clear and actionable from one that obscures the user’s actual positions and invites mistakes.

Why default token visibility creates risk in multi-chain portfolios

When you connect a wallet address to a blockchain, that address can receive tokens without explicit consent from the user. Smart contracts, airdrops, and malicious actors exploit this to populate wallets with unwanted tokens. On Cosmos-ecosystem chains, where IBC enables interoperability and asset transfers between networks, a single address can theoretically accumulate hundreds of tokens across connected chains. The keplr wallet extension initially displays most of these automatically, creating a management problem rather than a convenience feature.

The practical risk is multifaceted. First, visual clutter obscures legitimate holdings. If a user owns meaningful quantities of OSMO, JUNO, and ATOM but the portfolio view is dominated by fifty dust-level tokens and scam variants, the user may overlook an important balance or misread which token they are about to spend. Second, scam tokens often mimic legitimate ones. A token named „OSMOSIS“ or „Atom“ (with slightly different capitalization or unicode characters) can sit in the wallet, waiting for the user to approve a transaction or transfer funds to an attacker’s address. Third, holding tokens that are not on the user’s intended list represents an unmonitored exposure. Price swings, contract vulnerabilities, or sudden unlocks can affect a wallet’s stated net worth without the user being aware.

The extension’s default behavior respects the principle that a wallet should show what is actually stored on the blockchain. However, respecting blockchain state does not require showing everything equally. Token visibility controls allow the user to establish a hierarchy: essential holdings are prominently displayed, legitimate but low-priority tokens are visible but secondary, and spam or unwanted assets are hidden entirely. This requires an active choice but produces a clearer relationship between the interface and the user’s actual risk and value.

Many users initially treat token management as a cosmetic preference. In practice, it is a critical maintenance task. The earlier a user establishes their token list, the fewer spam tokens will accumulate and the easier it becomes to spot new airdrop attempts. A wallet that starts with a curated view of important tokens makes it less likely that a user will approve an unintended transaction simply because they were scanning too many lines and clicked on the wrong row.

Adding custom tokens to the keplr wallet extension interface

The first operational step is to ensure that every token the user intends to hold is properly registered and visible in the keplr wallet extension. This involves navigating to the wallet’s settings, locating the token management section, and adding assets by their chain identifier and contract address. The process differs slightly between the Chrome extension, iOS, and Android versions, but the underlying logic is consistent: the wallet needs the asset’s contract address or token ID to fetch its metadata, display it in the portfolio, and enable transactions.

For tokens already supported by default or via community token lists, the addition process is automatic. Popular assets like ATOM, OSMO, JUNO, EVMOS, and SECRET are recognized across their native chains and immediately visible. However, wrapped versions, bridge-deployed tokens, or new assets may require manual entry. The user should gather the token’s contract address from a trusted source, such as the official project website or a reputable chain explorer, rather than copying it from unverified social media posts or airdrop announcements.

The contract address is a mandatory and precise field. Entering an incorrect address will not add the intended token; instead, it will add a worthless token (possibly controlled by the person who suggested the wrong address). A user should verify the address by checking it against the official source and confirming it matches the expected chain. Once entered correctly, the wallet will fetch the token’s name, symbol, and decimal precision automatically. The token then appears in the portfolio view and can be sent, received, and tracked alongside other holdings.

For users managing positions across multiple Cosmos chains, this process must be repeated for each chain-specific version of a token. A wrapped token on Juno may have a different address than the same asset bridged to Osmosis or Evmos. The keplr wallet extension keeps these separate by design, since they are technically different assets on different blockchains, but from a portfolio perspective, a user often wants to see them grouped together. Some users maintain a spreadsheet or note documenting which tokens live on which chains to streamline future lookups.

Hiding spam tokens and managing portfolio clutter

The inverse action—hiding tokens—is equally important. Once a user identifies a spam token, scam asset, or low-value airdrop that they do not intend to trade or hold, they can hide it from the portfolio view. Hidden tokens remain in the wallet and on the blockchain; they simply do not appear in the default display. The user can unhide them later if their circumstances change, but the default is to keep them out of sight and out of mind.

Many scam tokens arrive with marketing messages suggesting they represent value or require claiming. In reality, they are designed to trick users into approving an interaction that grants the scammer permissions to steal other assets in the wallet. A common attack vector involves a scam token that, when approved for spending, grants the contract unlimited access to other tokens held at the same address. The user might not notice because they are scrolling past dozens of worthless tokens to find the asset they actually want to move. Hiding spam tokens reduces the surface area for these attacks by eliminating the temptation to interact with them at all.

The hiding process is straightforward: locate the token in the portfolio view, access its options menu (often a three-dot icon or swipe gesture), and select „hide“ or „remove from view.“ Some implementations may offer a „block“ option, which not only hides the token but also prevents future instances of similar assets from appearing without explicit user action. The exact interface varies by platform—Chrome extension, iOS, or Android—but the outcome is consistent: the token no longer clutters the portfolio.

Users should develop a routine for reviewing and categorizing new tokens that arrive in their wallet. A monthly check of the portfolio for unexpected tokens, followed by a quick verification against known airdrop sources or projects the user is aware of, prevents spam accumulation from spiraling. Many legitimate projects announce airdrops well in advance and provide guidance on distinguishing legitimate tokens from scam variants. Consulting official project channels or community Discord servers before approving any interaction with an unfamiliar token is a practical defense.

Creating and applying token lists for multi-chain organization

Beyond individual token management, the keplr wallet extension supports the concept of token lists—curated collections of tokens grouped by category, chain, or user preference. A token list is a standardized format that the wallet can import, allowing the user to establish a consistent view across multiple devices or to apply a pre-vetted set of tokens that match their trading strategy or investment thesis. Rather than manually adding and hiding tokens on each new installation, a user can load a token list and the wallet automatically configures visibility based on the list’s contents.

Token lists can originate from several sources. Official project lists are maintained by the teams behind major Cosmos-ecosystem chains and assets. Community-curated lists, such as those maintained by Cosmos ecosystem working groups, include popular tokens voted on by the community. Individual users can also create private token lists and export them, effectively storing a personal whitelist that they can import into the wallet on different devices or after recovery from a backup.

The practical workflow begins with understanding the available lists and their scope. A list focused on major DeFi tokens across Osmosis will include OSMO, ATOM, and other blue-chip assets but may exclude smaller utility tokens or chain-specific tokens. A list curated for a specific project’s ecosystem will prioritize that project’s token and partners. A user can subscribe to multiple lists simultaneously, and the wallet merges them to create a composite view. If two lists conflict—one hides an asset while another shows it—the wallet typically defaults to showing the asset, but the user can manually override this by hiding it again.

For users who engage in decentralized finance activities, trading, or staking across multiple protocols, a custom token list tailored to those activities can significantly improve usability. Rather than a generic list of all tokens on a chain, a personal list might include only OSMO and IBC tokens relevant to the user’s positions on Osmosis, plus essential tokens for cross-chain swaps or liquidity positions on Juno or other connected blockchains. This list becomes part of the user’s setup and can be backed up or shared with other devices under the user’s control.

Staking and DeFi interactions within a clean portfolio view

Token management directly affects the user’s ability to participate in staking and decentralized finance activities efficiently. Many users stake ATOM on Cosmos Hub, delegate to validators on other chains, or provide liquidity to Osmosis pools. Each of these activities involves monitoring rewards, adjusting positions, and occasionally moving assets to different addresses or protocols. A cluttered token list makes it harder to distinguish which tokens represent active positions and which are passive holdings or spam.

The keplr wallet extension integrates staking interfaces and reward monitoring directly into the portfolio view. When a user has staked tokens, the wallet displays staking status, current rewards, and delegation details alongside balances. A clean token list ensures that the staking information is accessible without scrolling past irrelevant tokens. Similarly, for DeFi protocols connected via Web3 dApp integration, the wallet can display position summaries and reward accumulation for liquidity pools, lending protocols, or other complex positions.

This integration depends on the user taking an intentional approach to token visibility. If the token list includes only the assets the user is actively managing, the portfolio dashboard becomes a functional control panel. If it includes every token ever received, the dashboard becomes a data dump. The staking rewards that matter—ATOM staking yield, OSMO liquidity pool rewards, or Secret Network staking returns—remain visible and easy to monitor in a curated list. Spam tokens that might otherwise generate false alerts or obscure yield information are absent.

For users managing significant value across multiple protocols, this organizational clarity translates to better decision-making. Recognizing at a glance which positions are generating income, which are stable holdings, and which are experimental or high-risk requires a view that has been intentionally curated. The keplr wallet extension’s token management tools provide the interface; the user’s discipline in maintaining the list provides the discipline.

Protecting against scam tokens and social engineering attacks

Token visibility controls are a necessary but not sufficient defense against scam tokens. Many attacks exploit social engineering rather than technical weaknesses in the wallet. A scammer may create a fraudulent project website that looks identical to a legitimate one, announce an airdrop of a fake token, and instruct users to approve it. The user sees a token arrive in their wallet, checks the name, and assumes it is legitimate. Hiding that token prevents accidental interaction, but recognizing it as a scam in the first place requires additional vigilance.

The most reliable practice is to avoid approving any unknown token without independent verification. Legitimate projects announce airdrops through official channels, provide contract addresses, and explain the purpose of the token. Scams often involve pressure, artificial urgency, or requests to „verify“ the token by connecting to a website or approving a contract. If a token arrives unsolicited and the user has no memory of being airdropped by that project, hiding it is the appropriate response. If the user is curious about its legitimacy, they can research it on the Cosmos chain explorer using the token’s contract address, which will reveal if it has been traded, what its holder distribution looks like, and whether it is listed on any reputable exchanges.

The most dangerous scam tokens are those that mimic legitimate ones through name similarity or unicode lookalikes. „ATOM“ and „ATОM“ (with a Cyrillic character substituted) might appear identical in some fonts. The keplr wallet extension’s token list approach mitigates this by establishing a whitelist: if only official ATOM is on the list, the lookalike will not appear in the portfolio unless the user manually adds it. This transforms scam detection from an ongoing manual task into a one-time curation process.

Users can further protect themselves by enabling notifications for new token arrivals or by periodically auditing their wallet’s on-chain state. Tools like a Cosmos chain explorer will show the exact tokens held at an address without the filter of the wallet interface. Comparing the explorer’s list to the wallet’s visible tokens occasionally reveals spam that was not previously noticed. This manual verification is especially useful after participating in airdrops, new DeFi protocols, or other activities that may trigger unsolicited token transfers.

Multi-device synchronization and token list backup

A user who accesses their wallet across multiple devices—Chrome extension on a desktop, iOS app on a phone, Android app on a tablet—may find that token visibility settings are not automatically synchronized. The keplr wallet extension on desktop might have a carefully curated token list, while the mobile app shows all tokens by default. This inconsistency can create confusion and increase the risk of approving the wrong token when using a less-familiar interface.

The solution involves explicitly managing token list synchronization across devices. If the wallet supports cloud backup or exporting token lists, the user should configure this feature and ensure that any changes to the list on one device are reflected across others. Some users export their token list periodically and maintain it as a configuration file, effectively treating it as part of their wallet backup rather than relying on automatic synchronization. This approach is more labor-intensive but provides explicit control and a recovery path if a device is lost or factory-reset.

Backing up the token list is as important as backing up the recovery phrase or private keys. A recovery from the recovery phrase will restore the funds and signing capability, but it does not automatically restore the token visibility preferences. A user who has spent weeks curating their token list would face a tedious re-setup after recovery if they have not backed up the list separately. Some wallets store this information with the account configuration rather than the keyfile, so recovery procedures vary. The user should test the backup and recovery process on a secondary device before relying on it in an actual recovery scenario.

For users who manage portfolios of significant value or complexity, documenting the token list serves an additional purpose: it provides a reference for what constitutes a legitimate position in the wallet. If a device is compromised or a transaction is unauthorized, the documented list can help distinguish between legitimate tokens and injected scam tokens or malicious additions. This documentation, stored offline or in a secure note, becomes part of the user’s security posture and reduces the time required to audit the wallet’s state.

Advanced token management workflows for serious investors

Users who actively trade, manage positions across multiple protocols, or participate in community governance may require more sophisticated token management approaches. The keplr wallet extension’s basic hiding and custom list features are sufficient for most users, but advanced workflows often involve additional tools or processes. Some users maintain spreadsheets that map token contract addresses to their intended use, risk category, and approximate position size. Others use portfolio tracking applications that connect to the wallet and provide filtering, sorting, and visualization beyond what the wallet interface offers.

For users managing positions in both the keplr wallet extension and external protocols, creating a consistent naming convention across all tools prevents confusion and reduces the chance of approving wrong transactions. A token might be listed as „ATOM (Cosmos)“ in the wallet, „ATOM“ in a spreadsheet, and „cosmos (ATOM)“ in a DeFi protocol interface. Using the contract address as the definitive identifier, rather than relying on names that may vary, removes ambiguity.

Another advanced practice is maintaining separate wallets for different purposes. A user might keep a high-security wallet with only essential holdings (ATOM, OSMO, and a few others), a separate wallet for experimental or higher-risk tokens, and a third wallet for community governance participation or staking activities. The keplr wallet extension supports multiple wallet creation within a single account or extension instance, allowing the user to switch between contexts without managing separate browser profiles or applications. This compartmentalization reduces the risk that a compromised token or malicious transaction in one context affects the others.

Portfolio tracking applications and dashboard tools can also integrate with the keplr wallet extension through standard Web3 connections. Applications like Koinly, Zapper, or purpose-built Cosmos portfolio trackers can read the wallet’s balances without controlling the private keys. These applications can apply custom categorization, track cost basis for tax purposes, and provide richer visualization than the wallet itself offers. The wallet remains the source of truth for what is stored on-chain, while external tools provide the analysis and reporting layer. This separation allows the user to maintain a clean wallet interface while having comprehensive tracking elsewhere.

Practical steps for establishing and maintaining token discipline

A user beginning to use the keplr wallet extension should establish token discipline from the start rather than accumulating spam and attempting to clean it up later. The first practical step is to decide which tokens represent the core positions: ATOM if staking on Cosmos Hub, OSMO if trading on Osmosis, JUNO if holding Juno ecosystem assets, and any others integral to the user’s strategy. These become the foundation of the token list. All other tokens, whether they arrive through airdrops, transfers, or dust from failed projects, are evaluated individually and either added to the list if they serve a purpose or hidden if they do not.

The second step is to establish a monthly or quarterly review cycle. The user checks for unexpected token arrivals, verifies their legitimacy, and hides any spam. This routine maintenance prevents accumulation and keeps the portfolio view manageable. Setting a calendar reminder for this review, similar to reviewing password managers or security settings, ensures it does not slip. The time investment is minimal—typically 10 to 15 minutes per review—but the cumulative benefit is substantial.

The third step is to document the token list, either as an exported file or as a note describing the intended contents. This documentation serves as a reference for what should and should not be in the wallet, aids recovery after a device reset, and helps the user remember why each token is held. A simple format like „ATOM (Cosmos Hub, staking), OSMO (Osmosis, liquidity), JUNO (Juno, governance)“ is sufficient and takes only a few minutes to maintain.

The fourth step involves testing the configuration on a secondary device if possible. A user who manages significant funds should verify that their token visibility settings can be correctly restored after recovery or on a different device. This test prevents surprises during an actual recovery scenario. The test also confirms that the user understands their backup and recovery process, reducing the likelihood of mistakes when the stakes are real.

Finally, users should stay informed about new tokens in their ecosystems and evaluate them against their strategy. New IBC token connections, bridge deployments, or community airdrops will continue to arrive. A user who understands how to add and hide tokens can quickly incorporate legitimate new assets while filtering out spam. This ongoing awareness and maintenance is part of responsible portfolio management in a multi-chain ecosystem.