Skip to main content
Remote wallets are server-side wallets. They are not injected into the page; instead they expose a CIP-103 RPC endpoint over HTTP/SSE, and dApps register that endpoint with a RemoteAdapter. Remote wallets implement the asynchronous dApp API, where actions that need user interaction are completed through a userUrl redirect.

ā€‹
Expose a CIP-103 endpoint

Your service must expose a public RPC URL that implements the CIP-103 request methods and event stream. The SDK ships with a default list of remote wallets; additional ones are added by dApps at runtime.

ā€‹
Getting dApps to list your wallet

DApps add your endpoint to their wallet picker with a RemoteAdapter pointed at your public RPC URL. Share that URL and a display name with integrating dApps. The dApp-side registration steps are covered in Wallet discovery.

ā€‹
Requirements

  • Serve the CIP-103 RPC methods and event stream at a stable, public URL.
  • Configure CORS to allow the origins of the dApps that will connect.
  • Manage user sessions and issue the session token (JWT) the endpoint expects.
  • Handle authorization and signing on your side; never expose keys to the dApp.

ā€‹
Next steps