Solana Wallet

Solana Wallet

The Solana wallet backend lives in agent-wallet/ and is the authoritative wallet layer for OpenClaw.

Current areas include:

• SOL and SPL transfers
• swaps
• staking
• Bags launch
• Bags fee claims and analytics
• Jupiter Earn
• Kamino lending

Current functionality

Reads

• wallet balance and address
• portfolio and token price reads
• staking validators and stake account state
• Bags claimable positions and fee analytics
• Jupiter Earn tokens, positions, and earnings
• Kamino markets, reserves, obligations, and rewards

Writes

• SOL transfers
• SPL transfers
• message signing
• swaps through Jupiter routing
• native staking
• stake deactivation and withdrawal
• empty token account cleanup
• Bags token launch
• Bags fee claim
• Jupiter Earn deposit and withdraw
• Kamino deposit, withdraw, borrow, and repay
• devnet airdrops

Write flow

Write-capable tools are designed around:

1. preview
2. prepare
3. execute

The intended boundary is:

• use preview first
• use prepare for an execution plan only
• use execute only with host approval

prepare does not expose signed transaction bytes to the agent.

Provider model

By default, users do not need to bring their own RPC to start.

The stack can use:

• hosted provider gateway
• shared Solana RPC
• Bags provider access for launch and fees

Advanced users can still override the default path with their own RPC or their own gateway deployment.

In practice:

• shared RPC is the easiest onboarding path
• a dedicated RPC is the better choice if you want faster or more predictable performance

Delegation model

Much of the operational setup can be delegated to an agent or local installer.

The user should still own:

• runtime secrets
• approval decisions
• any mainnet-risk acceptance