Seeker Connect for web dapps

Seeker Connect links a web page open in the browser on the device to a Solana Mobile certified device's own wallet — Seeker is the first such device. It is a dapp-only SDK built on top of the official Mobile Wallet Adapter libraries: a UX/DX layer, not a protocol reimplementation. Where generic MWA centers on a "pick a wallet" chooser, Seeker Connect launches the device wallet directly through the MWA spec's Endpoint-specific URI (Android App Link) mechanism, carries the session over a Nostr relay, and ships Seeker-branded progress and error UI — all exposed to the app as an ordinary Wallet Standard wallet named "Seeker Connect".

Targets: Web is available today. React Native and Android (Kotlin) are planned. Until they ship, wallet connection inside an Expo or React Native app uses the solana-mobile-wallet skill instead.

The mental model — read this before writing code

• There is no long-lived connection. Every wallet interaction (connect, sign message, sign transaction) opens its own short-lived MWA session, runs one request, and tears down. Each interaction launches the wallet app and shows a branded progress overlay — the one exception is a silent connect, which only reads the cache and never opens a session. This is by design — do not build reconnect loops or keep-alive logic around it.
• "Connected" means "holds a cached authorization." The first connect() stores a wallet-issued authToken plus accounts and capabilities (localStorage by default). Later operations replay that token silently — no repeated consent prompt.
• Disconnect only forgets the token locally. It deliberately never calls the wallet's deauthorize, because that would launch the wallet app just to disconnect.
• It only completes on the device. On desktop, connect fails with association-failed — typically within seconds, when nothing answers the wallet launch; the association timeout only applies to a wallet that launches but never connects. Register the wallet unconditionally; it simply won't get past association elsewhere.
• The relay is a public Nostr relay, and the SDK ships no default. Use the verified default in Step 2 unless the developer names one. Solana Mobile's own relay is handed out behind a terms-of-use acceptance and is never yours to fill in.

Step 1: install

New project: the react-kit-shadcn template from the Solana Mobile CLI ships with Seeker Connect already wired up, using the same default relay as Step 2:

npx solana-mobile@latest create my-app --template react-kit-shadcn

Existing app: install the Wallet Standard entry point plus the Wallet Standard helpers the snippets below import from:

npm install @solana-mobile/seeker-connect-wallet-standard @solana/wallet-standard-features @wallet-standard/app @wallet-standard/features

The Wallet Standard package pulls in the other Seeker Connect packages (core, ui, web) as dependencies. They are not re-exported, though — so also install any of them the app imports from directly (@solana-mobile/seeker-connect-ui for the optional button below, @solana-mobile/seeker-connect-web for the imperative path in the references); strict package managers like pnpm refuse imports of undeclared transitive dependencies.

Step 2: choose the relay

Seeker Connect carries MWA's extended remote communication protocol over a Nostr relay, named by relayDomain. Every session generates a fresh Nostr keypair and publishes ephemeral events (kind 20012), so the relay has to accept ephemeral events from a pubkey it has never seen — no authentication, payment, allowlist, or web-of-trust check. Payloads are end-to-end encrypted between dapp and wallet; the relay carries ciphertext, so a bad relay costs availability, not secrecy.

Default to relay.primal.net. It met that requirement in repeated probes (September 2026): every kind 20012 event accepted and delivered, no rate limiting, a funded operator, Cloudflare anycast in front. Read it from the app's environment configuration (for example a VITE_SEEKER_RELAY_DOMAIN variable) with that value as the fallback, so the developer can switch relays without a code change.

Solana Mobile's relay is the developer's to supply, not yours. Solana Mobile runs a relay that is faster still, but its domain is published only on the Seeker Connect quickstart page, behind a terms-of-use acceptance the developer has to click through: https://docs.solanamobile.com/solana-mobile-stack/seeker-connect-quickstart

• Never write the Solana Mobile relay domain into the app yourself — not from memory, not copied from another project, not from a search result. Accepting the terms is the developer's act, and the page where they accept is the only place the domain is handed out. If the developer wants it, send them there and let them paste the value back.
• Do not invent any other hostname. Many public relays reject unknown pubkeys or ephemeral kinds, and the failure surfaces later as association-failed, not as a clear configuration error. Stay with the default, a relay the developer names, or one from the verified list in references/troubleshooting.md.

Step 3: register once at startup

Call registerSeekerConnect before the UI renders, so wallet discovery sees it from the first render. It must run in the browser — the snippet below reads window, so under SSR (Next.js and similar) put the call in a client-only module or guard it with typeof window !== 'undefined'; in a plain client-rendered app, module scope of the entry file is fine:

import { registerSeekerConnect } from '@solana-mobile/seeker-connect-wallet-standard';

registerSeekerConnect({
  identity: {
    name: 'My Dapp',
    uri: window.location.origin,
    icon: '/icon.png', // resolved relative to uri; shown in the wallet's consent UI
  },
  relayDomain: 'relay.primal.net', // verified public default; Step 2 covers overriding it
});

Configuration:

registerSeekerConnect also accepts seekerLink, authorizationCache, and presenter overrides — see references/imperative-api.md.

Step 4: use it like any other wallet

After registration, "Seeker Connect" appears in the Wallet Standard registry, so wallet-adapter, ConnectorKit, @solana/react-hooks, or a raw @wallet-standard/app listing all pick it up with no further wiring. Existing connect buttons and signing code keep working.

Features exposed: standard:connect, standard:disconnect, standard:events, solana:signMessage, solana:signIn, and — depending on the wallet's reported capabilities after the first connect — solana:signTransaction and/or solana:signAndSendTransaction.

Working with the wallet directly:

import { SeekerConnectWalletName } from '@solana-mobile/seeker-connect-wallet-standard';
import { getWallets } from '@wallet-standard/app';
import { StandardConnect } from '@wallet-standard/features';

const seeker = getWallets()
  .get()
  .find((wallet) => wallet.name === SeekerConnectWalletName);
const { accounts } = await seeker.features[StandardConnect].connect();

Restore the session on page load with a silent connect — it reads the cache and never launches the wallet, resolving with zero accounts when there is nothing cached:

const { accounts } = await seeker.features[StandardConnect].connect({ silent: true });

Feature-detect the signing routes. Until the first connect, both transaction features are assumed; after it they are re-derived from the wallet's actual capabilities, announced via a standard:events change event. Check before calling:

import { SolanaSignAndSendTransaction } from '@solana/wallet-standard-features';

const feature = seeker.features[SolanaSignAndSendTransaction];
if (feature) {
  const [{ signature }] = await feature.signAndSendTransaction({
    account,
    chain: seeker.chains[0],
    transaction,
  });
}

chain is part of the Wallet Standard input, but this wallet ignores it — the network is the one passed to registerSeekerConnect, replayed from the cached authorization on every call. Nothing cross-checks the two, so a per-call solana:devnet against a mainnet registration submits on mainnet without complaint. Pass seeker.chains[0] so the two can never disagree, and change networks at registration.

Transactions cross the feature boundary as raw serialized bytes (Uint8Array), legacy and v0 both supported — serialize with whichever client library the app already uses. Sign-in follows the SIWS spec via solana:signIn; domain defaults to window.location.host.

When sign-in authenticates a user, the server is the authority, not the client: issue a single-use, short-lived nonce server-side, and verify the returned message and signature — including the expected domain and validity window — on the server before creating a session. The seeker-genesis-token skill walks through that server flow step by step.

Handle errors by code

Wallet outcomes reject with a SeekerConnectError carrying a code:

Three failures are plain Errors instead, and they are misuse rather than wallet outcomes: signAndSendTransaction on a wallet that reported no support for it, any signing call before a successful connect, and a sign-in the wallet answered without a result.

That distinction decides who shows the error. The branded dialog fires for SeekerConnectError and nothing else — every code above except cancelled, which is a normal outcome and stays silent. The three plain Errors never reach the presenter, so if the app shows nothing they fail invisibly. Branch on the type first, then on .code:

import { SeekerConnectError, SeekerConnectErrorCode } from '@solana-mobile/seeker-connect-wallet-standard';

try {
  await seeker.features[StandardConnect].connect();
} catch (error) {
  if (error instanceof SeekerConnectError) {
    if (error.code === SeekerConnectErrorCode.cancelled) {
      return; // user closed the overlay; nothing to report
    }
    // The SDK has shown its dialog. Log, and leave the UI in the disconnected state.
    console.error(error);
    return;
  }
  // No dialog was shown for this one. Surface it yourself.
  showToast('Could not connect to the wallet.'); // your app's own error UI
  console.error(error);
}

Optional: the branded connect button

@solana-mobile/seeker-connect-ui ships a <seeker-connect-button> custom element in Shadow DOM (no host CSS needed). The SDK defines its elements on first use; call defineSeekerConnectElements() at startup to define them eagerly:

import { defineSeekerConnectElements } from '@solana-mobile/seeker-connect-ui';

defineSeekerConnectElements();

<seeker-connect-button theme="dark" variant="sign-in"></seeker-connect-button>

Attributes: disabled, theme="light" | "dark" (names the host page's theme), and variant="connect" (default) or variant="sign-in" for the label. Wire click to the connect or sign-in call yourself — the button is presentation only.

Reference material

• references/imperative-api.md — the non-Wallet-Standard path via createNostrSeekerLink().transact, and the seekerLink / authorizationCache / presenter overrides
• references/troubleshooting.md — association failures, desktop testing, capability-derived features, cache behavior

Related skills

• seeker-domains — display .skr names instead of raw addresses
• seeker-genesis-token — verify Seeker device ownership after connecting
• solana-mobile — the CLI, templates, and toolchain behind solana-mobile create
• solana-mobile-wallet — wallet connection in React Native apps (Mobile Wallet Adapter directly)

Links

• MWA web docs: https://docs.solanamobile.com/get-started/web/installation
• Seeker Connect docs: https://docs.solanamobile.com/solana-mobile-stack/seeker-connect
• Seeker Connect quickstart (relay terms live here): https://docs.solanamobile.com/solana-mobile-stack/seeker-connect-quickstart
• Seeker Connect repository: https://github.com/solana-mobile/seeker-connect