How to Discover dApps on the Kroma Network in 2026

Kroma is an Ethereum layer-2 network. A layer-2 is a scaling network that runs alongside Ethereum, processes transactions more cheaply, and settles to Ethereum. Kroma is built to be compatible with the Ethereum Virtual Machine (EVM), which means most smart contracts written for Ethereum can be deployed there with few or no changes.

That compatibility matters for discovery. An app that works on Ethereum can often appear on Kroma without a separate code base, so the question is less about whether a dApp is "a Kroma app" and more about whether it has been deployed to Kroma and whether the deployment is genuine.

Before you search for dApps, confirm the basics from official sources: the network name, chain ID, native gas token, and the public RPC endpoint. These details can change, so check them each time you set up a wallet. The official documentation and the network's announcement channels are the places to verify current values.

Kroma's status and ecosystem can change, and this guide does not state current activity levels. Treat any statement about the network's live status as something to confirm on the day you use it.

A dApp is a decentralized application: a front end that interacts with smart contracts on a blockchain. To use one on Kroma, your wallet must be pointed at Kroma, not Ethereum mainnet or another layer-2.

A typical setup looks like this:

• Install a self-custody wallet that supports EVM networks.
• Add Kroma as a custom network, using the chain ID and RPC URL from the official documentation.
• Check the currency symbol and block explorer link shown by the wallet against the official values.
• Keep a small amount of the gas token for transaction fees.

When you connect to a dApp, the wallet should show which network is active. If the app asks you to switch networks, confirm the chain ID in the prompt matches the one you expect. A mismatch is a common sign of a copied or malicious site.

Use a fresh wallet or a separate account for testing new apps, and keep your recovery phrase offline. Never type that phrase into a website or a support chat.

You need assets on Kroma to use most dApps, and you usually move them from Ethereum or another supported chain through a bridge. A bridge locks or burns tokens on one chain and releases or mints matching tokens on another.

The safest route is usually the official bridge or the one listed in the network's documentation. Bridges are a frequent target for attackers, so confirm the bridge address and the token contract before you approve anything.

Follow these steps:

1. Start with a small test transfer.
2. Confirm the destination chain in your wallet before signing.
3. Wait for the transfer to finish on the destination chain.
4. Check the balance on the Kroma block explorer.

Some bridges are general-purpose cross-chain protocols. Across is one example of an intent-based bridge and swap protocol for moving tokens between Ethereum, rollups, and other chains, and it offers an API for apps. Whether a given route to Kroma is supported is a question to verify in the bridge's own supported-chains information at the time you transfer.

Do not rely on a bridge link from a search ad or a direct message. Open the bridge from official documentation you have checked yourself.

There is no single guaranteed directory that shows every app on Kroma. Instead, combine several sources and compare what they say.

• The network's official documentation and ecosystem announcements, which often list supported apps and infrastructure partners.
• The Kroma block explorer, where you can view contracts, transactions, and token pages.
• The official websites and documentation of individual dApps, which normally list the networks they support.
• Community channels run by the network, reviewed with caution because they can be impersonated.
• Data tools that index deployments across chains, which can help you filter by network. Use them as a starting point, not as proof.

When you find a candidate app, record its name, its official URL from the project's own documentation, and the contract addresses it publishes. Then check each address on Kroma. This two-way check is the core of the method.

If a list names an app but the official project does not mention Kroma, treat the listing as unverified until you confirm it.

A deployment is real when the contract code exists at the address the project publishes on Kroma. Follow these checks:

1. Open the Kroma block explorer and search for the address the app gives you.
2. Confirm the address is a contract, not a regular wallet.
3. Look for verified source code, which lets you compare the deployed code with the published source.
4. Check the creation transaction and the deployer address against what the project states.
5. Compare the token addresses with the project's documentation. Fake tokens often use the same name and symbol.

A verified contract does not guarantee the app is safe or well run. It only means the code is public and matches the address. Read the project's documentation, its audit reports if it publishes them, and its governance or admin controls.

For lending and exchange protocols, check which contracts control funds and who can change them. Some protocols use upgradable contracts or privileged roles, and you should understand those before depositing.

Many well-known protocols are deployed on several EVM networks. Their presence on Kroma is something to verify for each one, but these are the categories readers most often search for and where the big names tend to appear:

Category	Example protocols	What to check on Kroma
Decentralized exchange	Uniswap V3	Official deployed-networks list and the pool and router addresses
Lending	Aave V3, Compound V3, Morpho	Market list, supported assets, and the pool or market contracts
Aggregator	1inch	Supported chains page and the router contract
Cross-chain bridge	Across, LayerZero V2	Supported routes and the contract addresses

Uniswap V3 is described as running across more than 40 chains, Aave V3 across 21 chains, and Compound V3 across ten chains. Those counts are from the sources reviewed and can change, so treat them as background, not as confirmation of Kroma support.

When you use a lending protocol, understand supply and borrow rates, collateral factors, and liquidation rules before you deposit. Rates and market sizes change constantly, so look them up on the app at the time you act.

Before you connect a wallet, check the following:

• Is the URL the official one, listed in the project's own documentation?
• Does the app name the network it runs on, and does that match Kroma?
• Are the contract addresses published and verifiable on the block explorer?
• Does the project explain who controls upgrades, fees, and emergency actions?
• Has the project published audits, and do they cover the deployed version?
• Is there a public record of incidents or an active support process?

Also consider the type of product. A decentralized exchange, a lending market, and a yield vault carry different risks. Smart contract bugs, oracle failures, liquidity problems, and governance decisions can each cause losses.

No single check is decisive. A verified contract with a clear team can still fail, and a new app with little history can still be sound. Use the checks together and size your position so that a loss would be acceptable to you.

If an app involves gambling or wagering, check your local laws first and make sure you meet the minimum age that applies where you live. Gambling can be illegal or restricted in some places, and you should never try to bypass age or location checks.

Exploring a new network carries predictable risks. Most losses come from phishing, malicious approvals, or copied apps rather than from the chain itself.

• Bookmark the official dApp URLs you have verified, and type them rather than clicking public reporting or links in messages.
• Review each token approval your wallet grants, and revoke approvals you no longer need. Use the wallet's own approval manager or an established revocation tool that you have checked independently.
• Read every signature request. A signature that grants unlimited token spending or transfers permission is high risk.
• Never sign a message or transaction you do not understand, and never enter your seed phrase on a website.
• Keep only the funds you are prepared to use on a new network in that wallet.
• Use a hardware wallet for larger balances if your wallet supports it.

Watch for support scams. Real teams do not message you first asking for your recovery phrase, and they do not ask you to send funds to unlock an account.

If you think you have signed something harmful, move remaining funds to a new wallet you control, revoke the approval, and report the incident to the affected project through its official channel.

Networks and apps change, so build a habit of re-checking rather than relying on any single list.

1. Confirm the network details from official documentation each time you add or reconnect the network.
2. Check each dApp's supported-networks page before you use it.
3. Verify contract addresses on the Kroma block explorer when you first interact and after any announced upgrade.
4. Watch the official channels of any protocol you use for migrations, paused markets, or new deployment addresses.
5. Re-check bridge routes and token addresses before large transfers.
6. Review your open approvals and positions periodically.

For figures that change often, such as total value locked, trading volume, fees, yields, and token prices, do not rely on numbers in a guide. Look them up on the dApp itself or on the block explorer at the time you decide.

If you are unsure whether an app is still live on Kroma, treat the absence of recent activity as a signal to investigate, not as proof either way. Ask the project directly through its official support channel, and do not trust unsolicited contacts.