Skip to main content

Network Presets

The Privacy Boost CLI includes built-in network presets for common configurations.

Available Presets

Preset names are case-insensitive. All hosted presets use WETH at 0x4200000000000000000000000000000000000006. The chain IDs above identify the deployments; chain_id and shield_contract_address are auto-discovered from each server’s /api/v1/info endpoint at runtime.
The Rust CLI library exposes the same presets:
Other hosted variants are OpSepolia, OpMainnet, BaseMainnet, BaseSepolia, and SoneiumMainnet.

Custom Configuration

Configuration File

Create a custom configuration at ~/.privacy-boost/config.toml:
Load automatically or specify path:

Environment Variables

Override any configuration with environment variables:

Priority Order

The CLI selects one configuration source, in this order:
  1. --network (or PRIVACY_BOOST_NETWORK)
  2. --config (or PRIVACY_BOOST_CONFIG)
  3. ~/.privacy-boost/config.toml
  4. The local preset
Passing --network bypasses config files. Explicit field flags such as --rpc-url, and their corresponding PRIVACY_BOOST_* environment variables, override the selected source. A flag takes precedence over its environment variable.

Initialize Configuration

Create a configuration file from a preset:
If ~/.privacy-boost/config.toml already exists, init will skip and warn you. Delete the existing file first to reinitialize. You can also import an existing config file as the default:

Multiple Configurations

Use the --config flag to point at different config files per command:

RPC Provider Recommendations

Public RPC Endpoints

Private RPC Providers

For higher rate limits, use a dedicated RPC provider:
  • Alchemy: https://opt-sepolia.g.alchemy.com/v2/YOUR_KEY
  • Infura: https://optimism-sepolia.infura.io/v3/YOUR_KEY

Chain ID Reference

Next Steps