Getting Started
Dashboard Guides
Trading Guides
Need Help?
Join our community for support, updates, and trading discussions.
Initial Setup Guide
Before you can start trading, you need to configure your wallet and RPC settings. This guide will walk you through the initial setup process step by step.
Grab the newest ScreenerBot build before configuring your wallet and RPC. The download page always shows the latest installers and SHA256 checksums for every platform.
macOS, Windows, and Linux packages refresh together—no outdated links.
Setup Overview
Wallet Setup
Configure your Solana wallet private key
RPC Configuration
Add your Solana RPC endpoint(s)
First Launch
Start the bot and verify everything works
Before You Begin
Prerequisites Checklist
- ScreenerBot installedFollow the Installation Guide if you haven't already
- Solana wallet with private keyAny wallet that exports base58 private keys (Phantom, Solflare, etc.)
- RPC endpoint URLFree or premium Solana RPC provider
- SOL for tradingFunds in your wallet for trades and transaction fees
Step 1: Wallet Configuration
ScreenerBot needs your wallet's private key to sign transactions. This is stored locally in your configuration file and never shared.
Getting Your Private Key
ScreenerBot supports any Solana wallet that can export private keys in base58 format. Popular options include Phantom, Solflare, Backpack, Fuse, Exodus, Trust Wallet, Coinbase Wallet, and Math Wallet.
From Phantom Wallet
- Open Phantom wallet
- Click menu (☰) → Settings → Security & Privacy
- Select "Export Private Key"
- Enter password to confirm
- Copy the private key (base58 format)
From Solflare Wallet
- Open Solflare wallet
- Click Settings (gear icon) → Export Private Key
- Enter password to verify
- Copy the private key (base58 format)
From Other Wallets
Most Solana wallets support private key export. Look for options like:
- Backpack: Settings → Security → Export Private Key
- Fuse: Profile → Security → Show Private Key
- Exodus: Settings → Solana → Export Private Key
- Trust Wallet: Settings → Wallets → Show Private Key
Security Warning: Your private key gives full control over your wallet. Never share it with anyone. ScreenerBot encrypts it with AES-256-GCM before storing in config.toml - keep this file secure and backed up safely.
Supported Private Key Format
Base58 Format (Required):
- A string of characters (typically 87-88 characters long)
- Standard format exported from all major Solana wallets
- This is the only format ScreenerBot accepts
Note: If your wallet only provides a JSON keypair file (array format like [1,2,3,...]), you'll need to convert it to base58 format using Solana CLI tools or online converters before using it with ScreenerBot.
Step 2: RPC Configuration
ScreenerBot features an advanced multi-provider RPC system with automatic failover, rate limiting, and performance optimization. You can use free or premium RPC providers.
Smart RPC Management
Auto-Detection
ScreenerBot automatically identifies your provider (Helius, QuickNode, Triton, Alchemy, or public) and applies optimal rate limits.
Circuit Breaker
Failed endpoints are temporarily disabled, automatically switching to healthy alternatives.
Adaptive Selection
The default strategy learns from performance metrics to select the best endpoint for each request.
Rate Limiting
Per-provider rate limits (Helius 50 RPS, QuickNode 25 RPS, Triton 100 RPS) prevent throttling.
Choosing an RPC Provider
Free RPC Providers
- Helius: 100k requests/day free tier
- QuickNode: Limited free tier available
- Alchemy: Generous free tier for beginners
Good for testing and light trading.
Note: May have rate limits and slower response times.
Premium RPC Providers
- Helius Pro: High throughput, low latency
- QuickNode: Dedicated nodes, premium support
- Triton: Optimized for trading bots
Recommended for active trading. Higher rate limits and better reliability.
Tip: Configure 2-3 RPC endpoints from different providers for maximum reliability. ScreenerBot's circuit breaker will automatically failover to healthy endpoints if one fails. For more details, see our Best RPC Providers Guide.
Getting Your RPC URL
Example: Helius RPC
- Visit helius.dev
- Sign up for a free account
- Create a new project
- Copy your RPC URL (looks like:
https://mainnet.helius-rpc.com/?api-key=YOUR_KEY)
Example: QuickNode
- Visit quicknode.com
- Create an account and select "Solana Mainnet"
- Create an endpoint
- Copy your HTTP Provider URL
Step 3: Complete Initial Setup
On first launch, ScreenerBot starts in initialization mode and guides you through a web-based setup wizard to configure your wallet and RPC endpoints.
Setup Wizard Flow
Launch ScreenerBot
The app detects no configuration exists and enters initialization mode.
Access Setup Wizard
- Desktop App: Setup wizard opens automatically in the app window
- Command Line: Open
http://localhost:8080in your browser
Enter Credentials
Provide your Solana wallet private key and RPC endpoint URLs.
Automatic Configuration
Wizard validates credentials, encrypts your wallet, and creates config.toml automatically.
Services Start
All background services initialize and the bot becomes fully operational.
Security: Your wallet private key is encrypted with AES-256-GCM using a machine-bound key before storage. Never share your private key or config.toml with others.
Configuration File Location
After setup completes, your encrypted configuration is stored at:
~/Library/Application Support/ScreenerBot/data/config.toml%LOCALAPPDATA%\ScreenerBot\data\config.toml~/.local/share/ScreenerBot/data/config.tomlAfter initialization, you can modify settings anytime via the dashboard Config page. Changes are saved automatically to config.toml. You can also export/import config for backup or sharing.
Next Steps
Troubleshooting Setup
"Invalid Private Key" Error
Ensure you are using the Base58 format (string of characters), not a JSON array. If you have a JSON file, use the Solana CLI to convert it or import it into a wallet like Phantom and export the private key.
RPC Connection Failed
Check that your RPC URL is correct and includes your API key. Verify you have credits/requests remaining on your plan. Try accessing the URL in a browser to see if it returns a response.
Port 8080 Already in Use
If the dashboard fails to start, another application might be using port 8080. You can change the port in config.toml under the [webserver] section.