Architecture

System overviewCopy Anchor Link

The request flow through the dev wallet has three layers:

flowchart TD
    A["Your dApp"] -->|"wallet-standard API"| B["DevWallet Core"]
    B -->|"auto-approve check"| C{"Auto-approve?"}
    C -->|"Yes"| D["Adapter signs immediately"]
    C -->|"No"| E["Queue as pendingRequest"]
    E --> F["UI: Signing Modal"]
    F -->|"Approve"| D
    F -->|"Reject"| G["Return error"]
    D --> H["Return result to dApp"]
    G --> H

Your dApp — calls wallet-standard methods via dApp Kit or directly.

DevWallet Core — checks auto-approve policy, executes immediately or queues for user approval.

Adapters — InMemory (Ed25519), WebCrypto (Secp256r1), Passkey (WebAuthn), and Remote CLI (HTTP) all implement the same SignerAdapter interface.

Embedded vs standaloneCopy Anchor Link

flowchart LR
    subgraph Embedded["Embedded Mode"]
        direction TB
        EA["dApp Process"]
        EB["DevWallet instance"]
        EC["Lit UI in DOM"]
        ED["Adapter + Signer"]
        EA --> EB --> EC
        EB --> ED
    end

    subgraph Standalone["Standalone Mode"]
        direction TB
        SA["dApp Process"]
        SB["DevWalletClient"]
        SC["Popup Window"]
        SD["DevWallet + UI"]
        SE["Adapter + Signer"]
        SA --> SB -->|"PostMessage"| SC
        SC --> SD --> SE
    end

Embedded mode — the wallet runs in-process in your dApp. The DevWallet instance is created directly, and the UI renders in your DOM. Best for development and testing.

Standalone mode — the wallet runs as a separate web app. Your dApp uses DevWalletClient to communicate via popup windows and PostMessage. Supports CLI signing and team sharing.

The signing pipelineCopy Anchor Link

When a dApp calls signTransaction:

1. Transaction is serialized to JSON via transaction.toJSON()
2. Auto-approve check: adapter's allowAutoSign is evaluated first (adapters can opt out regardless of wallet policy), then the wallet-level autoApprove policy
3. Auto-approved: calls the adapter's signer directly, returns the result
4. Manual: stored as pendingRequest, listeners notified, UI shows the modal
5. approveRequest() → adapter signs → promise resolves; rejectRequest() → promise rejects

Export map architectureCopy Anchor Link

The package is split into subpath exports to support different environments:

Wallet-standard complianceCopy Anchor Link

The dev wallet implements the full wallet-standard interface:

Key design decisionsCopy Anchor Link

One request at a time — prevents confusion. The user always reviews exactly one transaction. DApps that batch transactions should serialize their signing calls.

Adapter aggregation — DevWallet unions accounts from all adapters. This lets you use InMemory for quick throwaway accounts alongside WebCrypto for persistent ones.

Shadow DOM UI — Lit components render in Shadow DOM, isolating styles from your app. The wallet panel never breaks your layout or inherits your CSS.

Listener pattern — onRequestChange() and onConnectChange() return unsubscribe functions, following the same pattern as wallet-standard events.