Dolphin IDConsole

Web3 auth, Web2 expectations

Wallet login for apps that need real sessions.

Dolphin ID turns multi-chain wallet signatures into production auth: polished login UI, verified SIWX messages, account-linked identities, refreshable sessions, and an OIDC bridge for existing app stacks.

EVMSuiSolanaBitcoinAptos
app.dolphin.idLive session
noncevalid
domainmatched
identitydid:dlp:8f2
const { signIn } = useDolphin();
await signIn({ chain: "evm" });

Inspired by mature auth products

Designed like a Web2 auth platform, specialized for wallet identity.

Clear platform promise above the fold

Product UI mock that shows the actual workflow

Capability groups instead of feature soup

Docs and dashboard CTAs always visible

Product

Everything between connect wallet and authenticated app state.

Dolphin ID packages the parts teams usually rebuild: adapters, React runtime, default components, server verification, hosted primitives, and dashboard-managed OIDC clients.

Drop-in UI

A familiar login surface for wallet users

Give teams a hosted-feeling sign-in component, account menu, error states, and localization hooks without hiding the wallet signature flow.

Chain adapters

One identity model across multiple chains

Normalize EVM, Sui, Solana, Bitcoin, and Aptos accounts into stable sessions that product code can consume the same way.

Server auth

Nonce, verification, refresh, and logout included

Use the self-hosted server primitives or the hosted Worker contract to issue real app sessions after SIWX verification.

OIDC bridge

Wallet sessions that plug into Web2 systems

Expose wallet-backed identities through OIDC clients, JWKS, userinfo, and dashboard-managed client registration.

Developer path

Four steps from wallet proof to application session.

01

Connect

Discover installed wallets and connect the user's preferred chain account.

02

Prove

Build the SIWX message, request a signature, and verify domain, nonce, address, chain, and expiration.

03

Session

Issue a JWT session, bind accounts to an identity, and refresh or revoke when policy changes.

04

Integrate

Send OIDC claims or session snapshots into the app, API, or customer dashboard.

Implementation

Use hosted primitives or keep the auth boundary on your own server.

The public API stays small: configure adapters in React, call nonce and verify routes, then read identity and session state from hooks or server middleware.

app/dolphin-config.tscopy ready
import { DolphinProvider } from "@dolphin-id/react";
import { createEvmAdapter } from "@dolphin-id/adapter-evm";
import { createSuiAdapter } from "@dolphin-id/adapter-sui";

<DolphinProvider
  config={{
    adapters: [createEvmAdapter(), createSuiAdapter()],
    auth: {
      nonceUrl: "/auth/nonce",
      verifyUrl: "/auth/verify",
      refreshUrl: "/auth/refresh",
      logoutUrl: "/auth/logout"
    }
  }}
/>

Docs

Find the exact integration page.

Search guides, adapter specs, API references, security notes, and SDK setup from the same product surface.

Ship wallet auth

Give Web3 accounts the operating model of a serious auth product.