$BOS Documentation

How It Works

$BOS runs as a persistent process connected to your Solana wallet via a read-only signing session. It monitors the Solana blockchain for new token launches, runs each token through your configured filter rules, and executes buy transactions automatically when conditions are met.

Requirements

Before using $BOS, make sure you have the following:

• —A Solana wallet — Phantom, Backpack, or Solflare recommended
• —SOL balance for gas fees — minimum 0.1 SOL recommended
• —Trading capital in SOL or USDC
• —A reliable internet connection — latency matters

Quick Start

Get from zero to trading in under five minutes.

1. Open the app

Navigate to the $BOS app. You'll be greeted by the dashboard with no active positions.

2. Connect your wallet

Click Connect Wallet in the top-right corner. Select your wallet provider and approve the connection request. $BOS only requests read permission — it cannot move funds without your explicit approval on each trade.

3. Fund your account

Ensure your connected wallet has SOL for both trade capital and gas fees. We recommend keeping at least 0.1 SOL dedicated to priority fees separate from your trading capital.

4. Configure your strategy

Go to Settings → Strategy and configure your entry parameters. At minimum, set:

max_entry_price = 0.001       # max SOL per token
position_size = 0.05          # SOL per trade
slippage_bps = 300            # 3% slippage tolerance
min_liquidity_sol = 10        # minimum pool liquidity

5. Enable the bot

Toggle the bot to ACTIVE from the dashboard. $BOS will immediately begin scanning and filtering new token launches against your config.

Connect Wallet

$BOS is fully non-custodial. Your private key never leaves your device. The connection between $BOS and your wallet is established through the standard Solana wallet adapter, the same protocol used by every major Solana DEX and application.

Supported Wallets

Your First Trade

Once connected and configured, $BOS will handle execution automatically. But you can also trigger a manual snipe from the dashboard for any token address.

# Manual snipe via dashboard
Token address:  [paste SPL token mint address]
Amount (SOL):   0.05
Slippage:       3%

> Click [Snipe Now] to execute immediately

Entry Parameters

Entry parameters define the conditions under which $BOS will execute a buy. All parameters are evaluated before every potential trade.

Risk Settings

Risk settings operate as a separate layer on top of entry parameters. Even if an entry signal passes your filter, it will be blocked if it violates your risk configuration.

Slippage & Fees

Slippage and priority fees directly affect your fill quality and execution speed. Higher slippage means more trades will fill but at worse prices. Higher priority fees mean faster inclusion but higher cost per trade.

# Fee cost per trade at 100,000 lamports priority fee:
# 100,000 lamports = 0.0001 SOL ≈ $0.015 at $150/SOL
#
# For high-volume setups, use dynamic_fees = true
# to avoid overpaying during low-congestion periods

Token Filtering

The filter engine is the core of what separates $BOS from a pure speed bot. Every new token launch is run through a multi-stage evaluation before an entry signal is triggered.

Filter Stages

Trade Execution

When a token passes all filters and entry conditions, $BOS constructs a swap transaction through the best available DEX route and submits it with your configured priority fee.

DEX Routing

$BOS routes trades through Raydium and Orca by default, with fallback to Jupiter aggregator for best-price routing on established tokens. For new launches, it targets the primary liquidity pool directly to minimize routing hops.

# Route priority (configurable):
1. Direct pool (Raydium V4 / CLMM)
2. Orca Whirlpool
3. Jupiter aggregator (fallback)

# Override routing:
dex_route = "jupiter"        # force Jupiter for all trades
dex_route = "raydium"        # force Raydium only
dex_route = "auto"           # default — BOS decides

Transaction Retry

If a transaction fails (dropped, simulation error, slippage exceeded), $BOS will retry up to max_retries times with exponential backoff before abandoning the entry.

Position Management

After a successful entry, $BOS tracks your position and manages exits based on your configured take-profit and stop-loss levels.

# Example position lifecycle:
Entry:    0.05 SOL @ 0.00042 SOL/token
TP:       +100% → sell at 0.00084 SOL/token
SL:       -30%  → sell at 0.000294 SOL/token
Trailing: enabled → SL moves up as price rises

Partial Exits

You can configure staged exits to take partial profits at multiple levels while keeping a portion running.

Risk Controls

Risk controls are hard limits that override all other settings. They exist to protect you from catastrophic loss in fast-moving markets.

# Emergency stop — disables all trading immediately
# Can be triggered from dashboard or via hotkey

Hotkey:  Ctrl + Shift + X
Effect:  Cancels all pending orders, pauses bot
Resume:  Manual re-enable required

RPC Configuration

$BOS connects to Solana via RPC endpoints. Your RPC quality directly impacts execution speed and reliability. By default $BOS uses a shared high-performance endpoint, but you can bring your own.

# Recommended RPC config for serious traders:
rpc_endpoint  = "https://your-node.helius-rpc.com/?api-key=XXX"
ws_endpoint   = "wss://your-node.helius-rpc.com/?api-key=XXX"
rpc_fallback  = "https://api.mainnet-beta.solana.com"

API Reference

$BOS exposes a local REST API on localhost:7171 when running. You can use it to query bot status, positions, and trigger actions programmatically.

# Example: get open positions
curl http://localhost:7171/positions

# Example: manual snipe
curl -X POST http://localhost:7171/snipe \
  -H "Content-Type: application/json" \
  -d '{"token": "So11111111111111111111111111111111111111112", "amount_sol": 0.05}'

Troubleshooting

FAQ