Skip to content

Solana Wallet

Solana Wallet

The Solana backend in agent-wallet/ is still the broadest wallet surface in AgentLayer.

It now covers much more than simple transfers.

Current read surface

Solana reads currently include:

  • wallet address, balance, and full token portfolio
  • token pricing through Jupiter
  • native staking validator discovery
  • native stake-account inspection
  • Jupiter Earn token discovery
  • Jupiter Earn position reads
  • Jupiter Earn earnings reads
  • Flash Trade market discovery
  • Flash Trade position reads
  • Kamino market, reserve, obligation, and rewards reads
  • LI.FI quote and status reads for cross-chain routes

Current write surface

Solana write-capable flows currently include:

  • sign_wallet_message
  • transfer_sol
  • transfer_spl_token
  • swap_solana_tokens
  • stake_sol_native
  • deactivate_solana_stake
  • withdraw_solana_stake
  • close_empty_token_accounts
  • request_devnet_airdrop

On top of the base wallet flows, Solana also includes:

  • launch_bags_token
  • flash_trade_open_position
  • flash_trade_close_position
  • jupiter_earn_deposit
  • jupiter_earn_withdraw
  • kamino_lend_deposit
  • kamino_lend_withdraw
  • kamino_lend_borrow
  • kamino_lend_repay
  • swap_solana_privately
  • continue_solana_private_swap
  • get_solana_private_swap_status
  • swap_solana_lifi_cross_chain_tokens

Solana-specific functional areas

Bags

Current Bags support includes:

  • token launch

Jupiter Earn

Current Jupiter Earn support includes:

  • supported token discovery
  • position reads
  • earnings reads
  • deposit and withdraw flows

Kamino

Current Kamino coverage includes:

  • market discovery
  • reserve reads
  • user obligation reads
  • user reward reads
  • deposit, withdraw, borrow, and repay flows

Flash Trade

Current Flash Trade support includes:

  • perpetual market discovery
  • open position reads
  • perpetual position open flow
  • perpetual position close flow

Private payouts

The Solana wallet now includes a Houdini-backed private payout path.

The current implementation is intentionally narrow:

  • same-token private payouts only
  • initial coverage for SOL -> SOL and USDC -> USDC
  • preview -> execute -> continue flow instead of the usual full prepare step

Cross-chain

Solana can now originate LI.FI-powered cross-chain swaps to supported EVM destinations when LI.FI returns a route.

Provider model

By default, Solana onboarding does not require operator-managed RPC.

The current default path can use:

  • hosted provider gateway
  • shared Solana RPC
  • Bags provider access
  • Jupiter Earn provider-gateway support
  • Houdini through the provider gateway in production-oriented setups

Bring your own RPC only when you want stronger operator control or better performance guarantees.