Configuration
Paths, config.toml, environment overrides, and network mode.
Paths
Print resolved paths:
seashail pathsEnvironment overrides (useful for tests/CI):
SEASHAIL_CONFIG_DIRSEASHAIL_DATA_DIR
Config File
config.toml lives under config_dir. Example:
network_mode = "mainnet" # or "testnet"
[rpc]
solana_rpc_url = "https://api.mainnet-beta.solana.com"
[http]
binance_base_url = "https://api.binance.com"
jupiter_base_url = "https://quote-api.jup.ag/v6"
# 1inch requires an API key. If unset, swaps use the Uniswap provider on EVM.
# oneinch_api_key = "..."Network Mode (Mainnet/Testnet)
Mainnet is the default.
Network mode is a convenience setting that affects default chain selection when tools omit chain/chains.
It does not hard-block mainnet/testnet usage: if a tool explicitly specifies a chain (for example chain="ethereum"),
Seashail will use that chain regardless of the current mode.
For a deeper explanation (including Solana RPC defaults, airdrops, and faucets), see:
/docs/guides/network-mode
First Run Defaults (Zero-Config)
If you want zero-config defaults for testnets, set this environment variable before first run (before config.toml is created):
export SEASHAIL_NETWORK_MODE=testnetAlias:
export SEASHAIL_NETWORK=testnetLegacy compatibility (not recommended):
export SEASHAIL_TESTNET_MODE=1Per-Client Override (Non-Persistent)
Per-client override (does not modify config.toml):
seashail mcp --network testnetPersistent Configuration
You can also set the mode in config.toml:
network_mode = "testnet"Agents can persist the mode via MCP using set_network_mode.