Configuration

Wallet Configuration

The WalletManagerSolana accepts an optional configuration object that defines how the wallet interacts with the Solana blockchain:

import WalletManagerSolana from '@tetherto/wdk-wallet-solana'

const config = {
  rpcUrl: 'https://api.mainnet-beta.solana.com', // Solana RPC endpoint
  transferMaxFee: 10000000 // Optional: Maximum fee in lamports
}

const wallet = new WalletManagerSolana(seedPhrase, config)

Account Configuration

Accounts are obtained through the WalletManagerSolana instance using getAccount() or getAccountByPath():

import WalletManagerSolana from '@tetherto/wdk-wallet-solana'

const accountConfig = {
  rpcUrl: 'https://api.mainnet-beta.solana.com',
  transferMaxFee: 10000000 // Optional: Maximum fee in lamports
}

const wallet = new WalletManagerSolana(seedPhrase, accountConfig)

// Get account by index
const account = await wallet.getAccount(0)

// Or get account by custom derivation path
const customAccount = await wallet.getAccountByPath("0'/0'/5'")

Configuration Options

rpcUrl

The rpcUrl option specifies one Solana RPC endpoint or an ordered list of endpoints for blockchain interactions.

Type: string | string[] (optional)

Default: If not provided, wallet functionality that requires RPC will throw an error

Examples:

// Single endpoint
const config = {
  rpcUrl: 'https://api.mainnet-beta.solana.com'
}

// Devnet
const config = {
  rpcUrl: 'https://api.devnet.solana.com'
}

// Failover across multiple endpoints
const config = {
  rpcUrl: [
    'https://api.mainnet-beta.solana.com',
    'https://rpc.ankr.com/solana'
  ]
}

// Custom RPC
const config = {
  rpcUrl: 'https://your-custom-rpc-endpoint.com'
}

When rpcUrl is an array, WDK initializes a failover provider and tries the next RPC when the current provider fails.

retries

The retries option controls how many times the failover provider retries a request before moving on to the next RPC entry.

Type: number (optional)

Default: 3

Example:

const config = {
  rpcUrl: [
    'https://api.mainnet-beta.solana.com',
    'https://rpc.ankr.com/solana'
  ],
  retries: 5
}

transferMaxFee

The transferMaxFee option sets the maximum allowed fee (in lamports) for transfer operations. This helps prevent unexpectedly high transaction fees.

Type: number (optional)

Unit: Lamports (1 SOL = 1,000,000,000 lamports)

Example:

const config = {
  transferMaxFee: 10000000 // 0.01 SOL in lamports
}

Complete Configuration Example

import WalletManagerSolana from '@tetherto/wdk-wallet-solana'

const config = {
  // Required for most operations
  rpcUrl: 'https://api.mainnet-beta.solana.com',
  
  // Optional: Fee protection
  transferMaxFee: 10000000 // 0.01 SOL maximum fee
}

const wallet = new WalletManagerSolana(seedPhrase, config)

Network Endpoints

Mainnet

• RPC: https://api.mainnet-beta.solana.com
• WebSocket: wss://api.mainnet-beta.solana.com/

Devnet

• RPC: https://api.devnet.solana.com
• WebSocket: wss://api.devnet.solana.com/

Testnet

• RPC: https://api.testnet.solana.com
• WebSocket: wss://api.testnet.solana.com/

Derivation Paths

Solana wallets use SLIP-0010 derivation paths. The default derivation path follows ecosystem conventions:

• Default path: m/44'/501'/{index}'/0' (where {index} is the account index)
• Custom child paths must keep every segment hardened, for example 0'/0'/5'

Security Considerations

• Always use HTTPS URLs for RPC endpoints
• Use RPC endpoints that serve the same Solana network when enabling failover
• Set appropriate transferMaxFee limits for your use case
• Consider using environment variables for configuration in production
• Use trusted RPC providers or run your own Solana validator for production applications

Need Help?