# Check KeySigner wallet discovery in Lido and Compound

[Read this guide on KeySigner](https://keysigner.io/integrations/guides/check-wallet-discovery-in-lido-and-compound/)

Check what each app’s wallet picker shows before you share an Ethereum address.

## Before you start

- Load the KeySigner development extension in a separate Chrome profile with other wallets disabled. Select Ethereum in KeySigner. You can leave the phone unpaired for these checks.

## Data and access

- **Shared or checked**. The wallet picker lists wallets a browser announces. In this exercise you stop at discovery, before sharing an address or approving a request.
- **Check separately**. Wallet discovery does not prove an app can complete a connection or a specific staking or borrowing operation.

## 1. Check that the browser sees KeySigner

Follow steps 1 and 2 of the local wallet example through the KeySigner found message. Stop before Share a test account. This checks that the extension is visible to a site that listens for wallet announcements.

**Check.** The local example finds KeySigner and shows no shared address.

## 2. Open Lido’s wallet picker

Open the Lido staking widget and choose Connect wallet. The Browser option is disabled while Lido’s terms checkbox is clear. Review Lido’s wallet requirements if you decide to continue.

**Check.** The picker shows Browser under Choose wallet. A disabled option tells you the picker has stopped at the terms step.

## 3. Open the Compound III Ethereum USDC market

Choose Connect Wallet. If the picker says No browser wallet detected even though the local check sees KeySigner, record the two results. Choose a documented wallet option for that market if you need to use Compound.

![Compound’s Connect Wallet dialog says No browser wallet detected.](https://keysigner.io/integrations/guides/check-wallet-discovery-in-lido-and-compound/compound-wallet-message.png)

Compound’s picker in a test profile with only the KeySigner development extension enabled.

**Check.** The message describes Compound’s wallet picker in this browser profile. In our check, the browser could see the KeySigner extension on the same page.

## Check your result

Wallet discovery, address sharing, and request approval each require a separate check. This walkthrough stops at wallet discovery.

### What we tested

**Tested on November 18, 2026.** Tested the live Lido staking widget and Compound III Ethereum USDC market in Chromium with the KeySigner development extension only. KeySigner announced itself on both sites and both had zero shared addresses. Lido’s terms remained unchecked. Compound displayed No browser wallet detected.

[How to verify your setup](https://keysigner.io/integrations/verify-a-setup/)

## If you get stuck

### The local example cannot find KeySigner

Check that the development extension is enabled in this Chrome profile, then reload the local page. When you report a picker issue, include the site URL, browser and extension versions, and the message you saw.

## Tools in this guide

- [Lido](https://keysigner.io/integrations/lido/)
  - [Compare staking tokens and supported operations](https://docs.lido.fi/guides/lido-tokens-integration-guide/)
- [Compound](https://keysigner.io/integrations/compound/)
  - [Review collateral and borrowing in Compound III](https://docs.compound.finance/collateral-and-borrowing/)

## Setup instructions

- [Check detection with the local wallet example](https://keysigner.io/integrations/guides/build-a-browser-wallet-integration/)
- [Open Lido](https://stake.lido.fi/)
- [Read Lido’s wallet connection instructions](https://help.lido.fi/en/articles/5231881-how-can-i-connect-my-wallet-when-staking-with-lido)
- [Open the Compound III Ethereum USDC market](https://app.compound.xyz/?market=usdc-mainnet)
- [Review Compound III markets and networks](https://docs.compound.finance/)

[More guides for this task](https://keysigner.io/integrations/tasks/check-key-approval/)
