# Check if OpenSea detects KeySigner

[Read this guide on KeySigner](https://keysigner.io/integrations/guides/check-opensea-wallet-detection/)

Find KeySigner in OpenSea’s wallet picker and review which wallet types OpenSea supports.

## Before you start

**Desktop Chrome 111 or later and the KeySigner development extension**

- Use a separate Chrome profile with other wallet extensions disabled. OpenSea excludes wallets that require multiple private keys to sign and send a transaction.

## Data and access

- **Shared or checked**. The site’s wallet picker receives the browser wallet announcement. This check only confirms the KeySigner entry is visible.
- **Check separately**. Check each intended network and wallet type separately. Sharing an address and signing an order are later decisions.

## 1. Load KeySigner in a test profile

Load the KeySigner development extension in a separate Chrome profile with other wallets disabled. Open KeySigner from the toolbar and select Ethereum. You can check detection with the phone unpaired.

**Check.** The KeySigner icon is available in the Chrome toolbar.

## 2. Open the OpenSea wallet picker

Open opensea.io and choose Sign in. Under external wallets in the Connect with OpenSea dialog, look for KeySigner marked Installed. Close the dialog after checking.

![The Connect with OpenSea dialog lists KeySigner marked Installed under external wallets.](https://keysigner.io/integrations/guides/check-opensea-wallet-detection/opensea-wallet-picker.png)

KeySigner appears in OpenSea’s external wallet list before you share an address.

**Check.** OpenSea shows KeySigner with the Installed label.

## 3. Review OpenSea’s wallet requirements

OpenSea supports browser wallet discovery and excludes multisig wallets that require multiple private keys to sign and send a transaction. Check OpenSea’s requirements for your wallet type before choosing a wallet.

**Check.** OpenSea’s help article lists supported wallet types and explains its multisig restriction.

## Check your result

The Installed label confirms that OpenSea detected the browser extension. Connecting an address and using it to sign are separate steps with their own requirements.

### What we tested

**Tested on November 18, 2026.** In Chromium 159.0.8154.6 with the KeySigner development extension, the live OpenSea dialog showed KeySigner marked Installed. We stopped with the dialog open. The browser reported zero shared addresses before and after opening it.

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

## If you get stuck

### KeySigner is missing from the OpenSea picker

Confirm that the development extension is enabled in this Chrome profile. Reload opensea.io and reopen the wallet picker. Check the extension against the local wallet example if it still does not appear.

## Tools in this guide

- [OpenSea](https://keysigner.io/integrations/opensea/)
  - [Setup requirements](https://keysigner.io/integrations/setup-requirements/#opensea)

## Setup instructions

- [Open OpenSea](https://opensea.io/)
- [Check which wallets OpenSea supports](https://support.opensea.io/en/articles/8867089-what-crypto-wallets-can-i-use-with-opensea)
- [Review an OpenSea signature request](https://support.opensea.io/en/articles/8867119-what-does-a-typed-signature-request-look-like)
- [Set up the KeySigner extension in Chrome](https://keysigner.io/integrations/guides/approve-an-ethereum-request-in-chrome/)
- [Test address sharing on a local page](https://keysigner.io/integrations/guides/build-a-browser-wallet-integration/)

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