Solana execution terminal

ButcherBot

ButcherBot is built for microsecond decision paths, aggressive landing fanout, fast entries, and controlled exits. This page documents what operators can configure without exposing private routing logic, live presets, wallet secrets, or internal strategy.

View infrastructure View modes

3Execution modes

TripleRPC, gRPC, shreds, aRPC lanes

8+Landing providers and counting

LocalPrivate keys stay local

Desktop and server

Linux terminal. Windows GUI.

Run ButcherBot as a Linux CLI executable for VPS operation or as a Windows GUI for desktop task, wallet, webhook, log, and P&L management.

Windows GUI executable

ButcherBot for Windows provides local management for wallets, tasks, logs, notifications, balances, and P&L cards.

ButcherBot.exe

Linux CLI executable

ButcherBot for Linux uses local configuration and a terminal workflow for VPS deployment and live execution.

cp config.example.toml config.toml
# Edit config.toml locally. Never paste real values into support chats.
chmod +x ./Butcherbot
./Butcherbot

Local-first operation

Wallets, runtime configuration, tasks, private keys, webhooks, logs, and analytics are stored locally by the application. Operators should protect local files and never send full configs for support.

Infrastructure

Triple RPC, triple gRPC, UDP shreds, raw shreds, decoded shreds, and aRPC.

ButcherBot can run multiple observation and send lanes in parallel. The docs explain the setup surface without exposing route selection logic or live operator endpoints.

Triple RPC

Used for transaction send fanout, startup reads, blockhash refresh, balance checks, and fallback reads.

rpc_urlrpc_url_2rpc_url_3

Triple gRPC

Used for live Pump.fun events and account updates. Multiple gRPC lanes improve observation resilience.

grpc_urlgrpc_url_2grpc_url_3

UDP raw shreds

Optional local UDP listeners for providers that push raw shreds directly to the operator’s server.

shreds_udpshreds_udp_bindshreds_udp_bind_2shreds_udp_bind_3

Decoded shreds

Optional decoded HTTP or TCP shred streams. Use them when a provider delivers decoded transaction hints instead of raw UDP packets.

shreds_decodedshreds_decoded_urlshreds_decoded_url_2shreds_decoded_url_3

aRPC decoded-shred gRPC

aRPC is not raw UDP. It is a decoded-shred gRPC lane for transaction hints from supported providers.

arpcarpc_urlarpc_url_2arpc_url_3

Speed controls

Operator-visible network controls include timeout, concurrency, retry, and blockhash refresh settings.

commitmentrpc_timeout_msrpc_retry_attemptsblockhash_refresh_ms

Mode 01

Sniper settings.

The regular Sniper mode is the filtered launch-entry workflow. These are the operator-facing settings that matter.

Trade setup

Buy size
Maximum open positions
Enter-on-launch toggle
Buy and sell slippage
Buy and sell compute-unit limits
Compute-unit price

buy_solmax_open_positionsenter_on_launchbuy_slippage_bpssell_slippage_bps

Token and market filters

Token age range
Recent volume range
Market cap range
Market-cap movement triggers
Minimum unique buyers and transactions

min_token_age_msmax_token_age_msmin_volume_usd_10smin_marketcap_usdmin_mcap_change_up_pct

Creator quality filters

Fresh dev wallet allowance
Migrated dev wallet allowance
Migration requirement
Creator/dev buy size range
Optional dev history checks

allow_fresh_dev_walletsallow_migrated_dev_walletsrequire_fresh_or_migrated_devmin_dev_buy_soldev_history

Launch metadata and dip controls

Reject suspicious metadata categories
Optional buy-on-dip range
Optional recovery confirmation
Dip timeout
Buy-once protection

reject_mayhemreject_cashbackreject_bundle_launchbuy_dip_min_pctbuy_once

Mode 02

Dev Wallet Sniper settings.

Dev Wallet Sniper watches configured wallets and targets fresh launches where the creator or user matches the watchlist. It has separate trade, risk, take-profit, and tip settings.

Watchlist matching

Configure watched wallets and whether ButcherBot should match creator, user, or both fields.

walletsmatch_creatormatch_user

Dedicated execution settings

Dev Wallet Sniper has its own buy amount, open-position limit, slippage, compute limits, and compute-unit price.

buy_solmax_open_positionsbuy_slippage_bpscompute_unit_price_micro_lamports

Own exits and tips

Mode-specific risk rails, take-profit ladder, fixed take-profit option, and route-specific tips are configured separately.

dev_wallet_sniper.risktake_profit_ladderdev_wallet_sniper.tips

Public-safe explanation

This mode is documented as a watchlist-based fresh-launch workflow. The docs do not disclose private entry logic, live wallet lists, production thresholds, or internal route preferences.

Mode 03

Copytrade settings.

Copytrade watches selected wallets and can mirror supported buys and sells with its own sizing, filtering, and emergency rails.

Wallet watching

Copied wallet list
Copy buys toggle
Copy sells toggle
Maximum open positions

walletscopy_buyscopy_sellsmax_open_positions

Buy sizing

Mirror copied wallet size
Use fixed buy size
Apply multiplier
Clamp minimum and maximum buy size

mirror_buy_sizebuy_solbuy_multipliermin_buy_solmax_buy_sol

Copytrade filters

Market cap range
Copied buy size range
Reserve range
Fee limits
Launch-event requirement
Transaction count and optional dip controls

copytrade.filtersmin_copied_buy_solmax_fee_bpsrequire_launch_event

Sell behavior

Mirror copied wallet sells when enabled
Fallback sell fraction when prior copied balance is not observed
Use take-profit ladder when mirrored sells are disabled
Emergency hard stop and max-hold rails

sell_fraction_fallback_pctcopytrade.riskcopytrade.take_profit_ladder

Landing

Multi-route landing without exposing strategy.

ButcherBot can fan out through multiple landing routes while also sending through direct RPC. The docs name the supported route surfaces, but not private provider keys, live endpoints, or internal ranking details.

Route cap

Control how many enabled landing routes are used per trade while direct RPC remains available.

max_routes_per_tradelocation

Fast landing providers

Operator-configurable landing routes include Lunar, Aura, Falcon, Astralane, Vision, BlockSprint, Node1, and Stellium.

Route-specific tips

Tip settings exist for normal, aggressive, capped, sell-multiplied, and mode-specific route tips.

base_tip_solaggressive_tip_solmax_tip_solsell_tip_multiplier

Provider hygiene

Provider URLs, API keys, tip accounts, dashboards, and live limits should remain private.

Risk

Exits, monitoring, and profit modes.

Risk exits

Hard stop loss
Loss timeout
Profit-stall timeout
Maximum hold time
No-movement exit
Pending buy/sell timeout

hard_stop_loss_pctloss_timeout_msprofit_stall_timeout_msmax_hold_msmax_no_movement_ms

Sell monitoring

Monitor interval
Sell rebroadcast cadence
Rebroadcast max window
Balance check timeout

monitor_interval_mssell_rebroadcast_msrebroadcast_max_msbalance_check_timeout_ms

Ladder take profit

Use staged exits with a profit target, a sell percentage of the current position, and a profit floor.

take_profit_mode = ladderprofit_pctsell_pct_of_currentfloor_pct

Fixed take profit

Use a single take-profit target when the operator wants a simpler exit configuration.

take_profit_mode = fixedfixed_take_profit_pct

Fee-based access

Simple transaction-based pricing.

0.69% per transaction

ButcherBot is fee-based, not subscription-based. A 0.69% fee applies per transaction.

Fee reserve and priority fees

Operators should review wallet balance, fee reserve, compute settings, priority fee estimates, and route tips before going live.

Infrastructure

Bring your own nodes.

Operators arrange their own node infrastructure.

ButcherBot is designed for users comfortable managing execution infrastructure. ButcherBot partners with selected providers, which may help operators reduce infrastructure costs.

Ready

Open the terminal. Confirm the checklist.

0% complete

I have the approved Windows or Linux build. I configured triple RPC, triple gRPC, optional shreds, and optional aRPC deliberately. I verified selected mode, wallet balance, fee reserve, priority fees, and route tips. I reviewed Sniper, Dev Wallet Sniper, or Copytrade settings for the active task. I reviewed risk exits, take-profit mode, monitoring cadence, and rebroadcast settings. I know what to redact before asking for support.

No leaks

Security rules for operators.

Private keys, wallet vaults, full configuration files, RPC or gRPC URLs, shred endpoints, aRPC endpoints, provider keys, Discord webhooks, settlement wallets, live thresholds, or route preferences.

Share operating system, build version, selected mode, sanitized error messages, and redacted screenshots only.

Trading involves risk. ButcherBot cannot guarantee profit or execution outcome.

FAQ

Frequently asked questions.

Is ButcherBot suitable for everyone?

ButcherBot is designed for operators with some trading and technical experience. Users should understand wallet management, node infrastructure, fees, and the risks involved in high-speed execution before running live.

Is ButcherBot fee-based or subscription-based?

ButcherBot is fee-based. There is no subscription model; a 0.69% fee applies per transaction.

Do I need to arrange my own nodes?

Yes. ButcherBot operators are expected to arrange their own nodes. ButcherBot partners with selected providers, which may help operators reduce infrastructure costs.