Solana Namespace - JSON-RPC Provider Authorization

Author Jon Wong, Glitch, bumblefudge
Status Draft
Type Standard
Created 2024-02-05
Updated 2024-02-05
Requires CAIP-25, CAIP-217


For context, see the CAIP-25 specification.


In the Solana ecosystem, standardization of the RPC provider interface has centered on the Wallet Standard and Wallet Adapter open-source tooling. For the most part, progressive CAIP-25 negotiation and iteration is possible over a Wallet Standard connection, with the former inheriting the declaration of initial capabilities and permissions made in the latter as initial state for further negotation.

Network-Specific versus Namespace-Wide Scopes

Few use-cases incorporating multiple Solana-compatible networks require granular permissions or capability declarations per-chain, so a Solana-wide CAIP-217 authorization scope (keyed to the entire solana namespace rather than to a specific chain), with permissions and capabilities set and with only one member at a time in the chains array, is recommended in most cases.

Multichain Considerations

Developers addressing multichain use-cases incorporating non-Solana networks are RECOMMENDED to use distinct CAIP-217 authorization objects per chain type, in cases where those CAIP-25 capabilities and configurations can be deterministically mapped to Wallet Standard Multichain Extensions variables by a CAIP-25 provider.

Also, consumers of the Wallet Standard interface assume the WalletAdapterNetwork enum variable to be set to exactly one network at a time, so implementers are recommended to map only one chains member at a time to this standard interface, whether by ordering it by preference or by never allowing it to have more than one member at a time.

Session Properties

Wallet capabilities in the Wallet Standard model are declared upfront at time of connection and persisted as read-only constants, so wallets are recommended to declare them explicitly in the sessionProperties object in a CAIP-25 interaction for maximum interoperability and stability. Note that the sessionProperties object is shared across any and all namespaces in a given wallet<>application session, which may span multiple types of networks all declaring sessionProperties, so to avoid collisions the following properties names are recommended for easily mapping to the case-sensitive properties names in the Wallet Standard:

sessionProperties key in CAIP-25 expression Wallet Adapter mapping values documentation reference implementation
SolanaTransactionVersion SolanaTransactionVersion 0 or legacy (default)
SolanaTransactionCommitment SolanaTransactionCommitment finalized (default), confirmed, processed

As these properties are mandatory and required for stability in Wallet Standard connections, CAIP-25 providers MAY inject defaults if any of the above are not set explicitly by a wallet. For this reason, wallets are RECOMMENDED to set them explicitly even if not requested by their counterparty to avoid inaccurate values being injected.


Example CAIP-25 Request

  "id": 1,
  "jsonrpc": "2.0",
  "method": "provider_authorize",
  "params": {
    "optionalScopes": {
      "eip155": { ... },
      "solana": { ... }
    "sessionProperties": {
      "capabilities": { ... }
      "eip155": { ... }
      "solana": {
        "SolanaTransactionVersion": "0",
        "SolanaTransactionCommitment": "finalized"



Copyright and related rights waived via CC0.


Please cite this document as:

Jon Wong, Glitch, bumblefudge, "namespaces/solana-caip25: Solana Namespace - JSON-RPC Provider Authorization [DRAFT]," Chain Agnostic Namespaces, solana-caip25, February 2024 / February 2024. [Online serial]. Available: