SamuraiX Standard User Guide Last updated: 2026-07-09 Refresh: 2026-07-04 Audience: SamuraiX users, testers, and community support helpers =============================================================================== Read This First =============================================================================== SamuraiX is a Telegram-based Solana trading bot. It brings several trading lanes into one menu system: Manual Trading, Manual Paper Trading, Holdings, Auto Sniper, Samurai Legion Sniper Range, AI Auto Pilot, Copy Trading, Limit Orders, TP/SL monitoring, Rug Shield, history/export tools, wallet tools, API key setup, and global settings. This guide is written for real users. It explains what the current bot surfaces mean, where to find them, and how to use them safely. It does not guarantee profit, it does not replace your own judgment, and it does not make risky token launches safe. Start tiny, keep SOL reserved for fees, and prove each workflow before scaling. Never share seed phrases, private keys, wallet exports, API keys, auth tokens, or provider dashboards in Telegram or Discord support channels. No legitimate SamuraiX support flow should need those secrets. =============================================================================== 1. Main Menu =============================================================================== The Main Menu is the normal starting point. Visibility can vary by account, admin gates, subscription status, and feature maturity, but the current core surfaces are: * Wallets / Wallet Setup - create, import, select, and inspect trading wallets. * API Keys Hub - configure provider access required by live trading and AI. * Manual Trading - buy/sell flows for one-off trades. * Holdings - view token holdings and enter sell/send/burn flows where supported. * Transaction History And Exports - review fills, history, and exported records. * Auto Sniper - rules-based token sniping and paper/live sniper controls. * Samurai Legion Sniper Range - premium SLSR source-intake and auto-buy flow. * AI Auto Pilot - AI-guided paper/live strategy automation with risk controls. * Copy Trading - follow selected wallets with copy settings and TP/SL controls. * Limit Orders - trigger-based paper/live order checks and managed ladders. * Rug Shield - safety monitoring for supported buy sources and sell flows. * Settings - timezone, Operation Mode, speed, MEV, managed tokens, media preview, notification visibility, and admin-only controls where authorized. * Help / Settings Help - short in-bot help plus guide downloads. * SamuraiX Discord - community support, onboarding, updates, and SLSR role access. Paper trading is not a standalone main-menu button in the current public layout. Paper paths live inside service flows such as Manual Paper Menu, Auto Sniper paper mode, AI Auto Pilot paper mode, Copy Trading paper support, or Limit Orders paper support where that service exposes them. =============================================================================== 2. Getting Started Safely =============================================================================== Recommended first-run order: 1. Open Wallet Setup and confirm which wallet SamuraiX will use. 2. Open API Keys Hub and configure required providers before trying advanced live workflows. 3. Open Settings -> Operation Mode and confirm the required setup indicators. 4. Keep SOL in the wallet for transaction fees, priority fees, and route costs. 5. Use paper/simulation flows where available to learn menus. 6. Start live workflows with tiny size only after you can explain the exact menu, source, sizing, slippage, and exit path you are using. 7. Review Transaction History And Exports after each test. 8. Add TP/SL rules and safety tools before increasing size. Paper/simulation results are learning aids. They are not proof that the same settings will be profitable in live conditions. =============================================================================== 3. Wallets, Security, And Account Boundaries =============================================================================== Wallet safety is separate from bot convenience. Before any live trade: * Know which wallet is selected. * Keep reserve SOL for routing and fees. * Confirm destination addresses before send actions. * Treat burn actions as destructive. * Use tiny live size until you have proved buy, sell, TP/SL, and history flows. * Never post wallet exports, private keys, seed phrases, provider keys, or secret screenshots in public support. SamuraiX may store user settings, provider readiness state, trading preferences, per-service configuration, and trade/history records. Normal user-owned keys are separate from owner/runtime keys unless an admin explicitly allows a bypass or switches key mode. =============================================================================== 4. Current Provider / API Key Model =============================================================================== Path: Main Menu -> API Keys Hub Owned Keys is the current standard/default public model. In Owned Keys mode, normal users bring their own provider access instead of silently consuming shared owner/runtime credentials. Important concepts: * Helius/RPC setup unlocks the intended Pro+ RPC path. * Jupiter setup supports route/quote and execution-related workflows. * At least one AI provider is needed for AI features. * Birdeye is configured in API Keys, not inside Operation Mode. * Social/scanner provider tokens belong to the service that owns that scanner behavior, usually AI Auto Pilot Social Intelligence or SLSR/source setup. * AI fallback means selected provider first, then that user's other configured or explicitly allowed AI providers/endpoints. Normal Owned Keys users should not expect automatic fallback to owner/runtime AI keys. If API setup is missing, SamuraiX can redirect you to the relevant provider setup instead of enabling a mode that cannot safely run. =============================================================================== 5. Settings And Operation Mode =============================================================================== Path: Main Menu -> Settings -> Operation Mode Operation Mode is user-facing and lives in Settings. It shows required setup status and controls how SamuraiX should behave around provider readiness, cost, profile choice, and current runtime-promotion stages. Current Operation Mode concepts: * Pro+ RPC is the intended normal path once Helius is configured. It uses Helius first, then the user's fallback RPC order, and QuickNode last when configured. * Truly Free uses public/free endpoints where practical and locks Trading Profile to Cost-Optimized. * Optimal and Custom profiles require Helius/RPC readiness. If setup is missing, SamuraiX redirects the user back to provider setup instead of pretending the mode is safe. * Birdeye controls do not live in Operation Mode anymore; they live in API Keys. Runtime Promotions live at Settings -> Operation Mode -> Runtime Promotions. The button is: * 🚦 Runtime Promotions Runtime Promotions are not a secret profit switch. They are a controlled rollout and readiness view for newer SamuraiX runtime systems. They show what evidence has been collected, what is still missing, and whether a family should stay in observation, paper, or approved live influence. Global/shared proof can accelerate readiness, but user-local setup and SHADOW/PAPER proof gate LIVE. A new user can benefit from broad SamuraiX evidence, but that user still needs their own provider setup, service settings, and local paper/shadow proof before LIVE is considered safe. Runtime Promotion families: * Market Data Hub - market-data freshness, fallback behavior, provider health, stale-price rejection, and execution-price contract evidence. * Strategies - strategy attribution, replay/backtest, skipped-candidate review, optimizer reports, and paper/shadow outcomes. * Guard/protections - honeypot/tax/holder checks, provider-failure locks, cooldowns, drawdown locks, duplicate-action prevention, and hard safety gates. * Exit policies - TP/SL, trailing, moonbag, time-exit, sell-guardrail, and lifecycle proof. This is high-risk and should need user-local paper proof before LIVE. * Adaptive learning - model/learning proposals, learned blocker behavior, and calibration metrics. This is slowest to promote and should remain shadow/canary until global metrics and user/cohort evidence are stable. Runtime Promotion stages: * OFF - rollback/disabled; the promoted family is inert or kept on legacy paths. * SHADOW - advisory/proof mode; collect clean evidence without live trading influence. * PAPER - paper/simulated consumers may opt in; live execution remains blocked. * LIVE - final approved stage after paper proof, hard protections, fresh execution price contracts, and explicit approval. Safety contracts still win. What counts as evidence: * source/replay/backtest reports and already-produced SHADOW/PAPER envelopes; * provider freshness, fallback reliability, latency/error/backpressure signals, and stale-price rejection; * user setup proof such as Operation Mode, API keys, provider health, wallet and service binding, risk limits, slippage, trade size, and enabled modules; * completed paper/shadow events, skipped-candidate review, protection fixtures, duplicate-action checks, and exit-lifecycle proof; * blocker lists explaining why a family should not move forward yet. How to use the submenu: 1. Open Settings -> Operation Mode -> Runtime Promotions. 2. Review the index rows. Each row shows the family, current stage, next stage, effective progress, and whether it is ready or blocked. 3. Open a family row to see Global/shared evidence, Cohort/style evidence, User-local evidence, Effective readiness, Completed proof, Missing/blockers, and Manual override warnings. 4. Use Refresh Progress after changing API keys, provider setup, paper/shadow activity, or service settings. 5. Leave a family in SHADOW when evidence is still being collected. Use PAPER to prove simulated behavior. Treat LIVE as an explicit approval stage only. 6. If a manual override warning appears, read it before continuing. It means the selected stage is ahead of the readiness evidence and the safer choice is to return to SHADOW or PAPER. Recording evidence never fetches providers, promotes a stage, deploys, restarts, migrates, backfills, trades, or changes live runtime behavior. It only records or summarizes proof that already exists. 100% readiness means ready for the next controlled stage, not guaranteed profit or risk-free trading. Default stage is SHADOW. Treat LIVE as an explicit approval stage, not a default. =============================================================================== 6. Market Data Hub And Strategy Lab =============================================================================== SamuraiX market data hub and Strategy Lab status/reporting surfaces are designed to make market data, replay, optimization, and runtime health easier to audit. They should not be described as a stale cached price source for live execution. Market data and provider behavior: * Market Data Hub can build shared/advisory market views. * User-aware provider order comes from Operation Mode and API Keys state. * When Pro+/Optimal is active and Birdeye is available for that user, the current source provider order is: dexscreener -> jupiter -> birdeye. * When the user is cost-optimized/free, or Birdeye is disabled, paused, missing, or unavailable, the current source provider order is: dexscreener -> jupiter. * Execution-price contracts require fresh execution prices and reject stale or advisory snapshots. * Live execution prices come from fresh route/quote/helper paths that satisfy the execution contract, not from display/cache data by default. Strategy Lab / Control Center can expose reports around market data, replay, optimizer state, learning proposals, provider backpressure, provider-failure locks, protection locks, queue pressure, and health. These reports are meant to make behavior explainable before promotion. Strategy Lab, optimizer, and learning: * Strategy Lab wraps existing SamuraiX decisions into attribution and replay metadata first; it does not replace service settings. * Replay/backtest can compare actual buys, skipped candidates, paper trades, counterfactual exits, lookahead checks, and history-depth stability. * Optimizer and learning proposals remain report/shadow/canary-gated before live influence. * They cannot loosen route/quote, honeypot/tax/holder, cooldown, drawdown, wallet, reserve-floor, sell-guardrail, or admin locks. * Hard protections, numeric risk limits, wallet boundaries, and admin gates stay above optimizer suggestions. =============================================================================== 7. Manual Trading And Manual Paper Menu =============================================================================== Path: Main Menu -> Manual Trading Manual Trading is the clearest way to learn the bot because you choose a token, amount, slippage, and action directly. Use it to prove wallet setup, route behavior, buy/sell handling, TP/SL attachment, and history recording before using automation. Manual Paper Menu lets you practice manual flows without sending a live trade. Use paper mode to learn screens and confirm settings, but remember that paper fills are approximations and cannot prove real liquidity, taxes, route behavior, MEV conditions, or live slippage. Common manual workflow: 1. Verify selected wallet and reserve SOL. 2. Paste or select the token/mint. 3. Choose a tiny amount. 4. Review slippage, route, and safety prompts. 5. Execute only if you understand the action. 6. Review Holdings and Transaction History afterward. 7. Attach or inspect TP/SL where appropriate. =============================================================================== 8. Holdings, Sell, Send, Burn, And History =============================================================================== Holdings shows current token positions and service-scoped holdings where the live build exposes them. Actions may vary by token, service, and wallet state. Current concepts: * Sell flows can be manual, preset, custom, TP/SL-driven, copy-driven, limit, or safety-triggered depending on the service that owns the position. * Send flows require careful destination review. Sending to the wrong address can be irreversible. * Burn flows are destructive and should only be used when you understand the token and the action. * Transaction History And Exports help you reconcile what SamuraiX believes it did with wallet/provider records. * Empty holdings screens can be normal when no supported token balance is found. Very small token amounts can behave differently during sells because route minimums and dust rules may apply. =============================================================================== 9. How TP/SL Works =============================================================================== TP/SL means take-profit and stop-loss. SamuraiX supports TP/SL in several service contexts: Manual, AI Auto Pilot, Copy Trading, Limit Orders, and SLSR or other scoped flows where exposed. Good TP/SL practice: * Define the stop before entering live trades. * Use ladders carefully. For example, partial sells at different profit targets can reduce risk while leaving upside. * Understand whether a TP/SL belongs to Manual, Autopilot, Copy, or another scoped service. * Confirm whether monitoring is enabled for that service. * Review trade history after triggers. Global TP/SL monitoring can be ON while individual service rules still determine which positions are watched and how actions execute. =============================================================================== 10. Auto Sniper =============================================================================== Path: Main Menu -> Auto Sniper Auto Sniper is rules-based automation for finding and buying candidates that match configured filters. It is not the place for every social scanner setting; AI Auto Pilot Social Intelligence owns many social scanner controls. Common Auto Sniper settings include: * enable/disable and mode controls; * trade amount and slippage; * liquidity, market cap, age, score, buy-count, and source filters; * anti-honeypot and token-quality checks; * paper/live behavior where exposed; * status, history, and P&L displays. Multi-Timeframe can use a lot of provider calls, rate limit, and runtime budget. Use it deliberately, especially in free/cost-optimized modes. Start with conservative filters and tiny size. A sniping tool can enter volatile launches quickly; that speed does not remove token risk. =============================================================================== 11. Samurai Legion Sniper Range (SLSR) =============================================================================== Path: Main Menu -> Samurai Legion Sniper Range SLSR is a premium Solana-only source-intake and auto-buy lane. It is part of the main SamuraiX bot runtime, not a separate public cron product. Access model: * Whop membership updates the Discord Samurai role. * SamuraiX checks the linked Discord account for the allowed role when the SLSR gate is ON. * Link Discord / Replace Discord starts a DM-code verification flow. * Typing a Discord username or numeric Discord user ID is not proof by itself. * Clear Discord Link removes the saved Discord identity and cached role result. * After clearing, SLSR requires fresh link verification before role access can pass again. * Manual SLSR bypasses are Telegram user ID bypasses for bot access only; they do not grant the Discord Samurai role or private Discord visibility. Important SLSR concepts: * Source toggles control which groups/sources can trigger SLSR auto-buy. * AI Learning Mode records decisions and learning data but does not by itself block buys. * Live AI mode can block buys when hard blockers fire. * Shadow mode is advisory/log-only. * Recovery Guard can reduce or block buying after SLSR goes net-negative or recent exits get ugly. * SLSR P&L reset affects SLSR display counters only; it does not move funds. * SLSR Token Holdings can expose SLSR-scoped sell, send, and burn actions. * SLSR is Solana-only. Non-Solana/EVM posts should not be routed into the Solana SLSR trading path. SLSR learning/runtime notes: * Raw learning outcomes are user-specific. * Derived aggregates can exist per user and as global fallback evidence. * Runtime should prefer user-specific evidence and use global evidence only as a cold-start/shared fallback. * Learned blocker buckets are data-derived. Update Blockers snapshots current aggregate learning into the active learned-blocker set. * Current learned blockers are intentionally narrow so the system does not block every volatile meme runner. =============================================================================== 12. AI Auto Pilot =============================================================================== Path: Main Menu -> AI Auto Pilot AI Auto Pilot can run in Off, Paper, or Live mode depending on your setup and activation state. The AI receives current settings and runtime context each cycle; it is still constrained by wallet state, sizing, risk controls, service state, route checks, safety gates, and execution checks. AI Auto Pilot settings include: * Basic Settings - max/min trade, daily exposure, daily loss, cooldowns. * Trading Rules - liquidity, market cap, age, score, re-buy blocks, taxes, execution quality, Launch Probe Buy, and service behavior. * Data Sources - candidate discovery feeds and market source modes. * Social Intelligence - optional social context, Twitter/X, Telegram, Discord scanner tokens, channel/source lists, exclusions, source weights, and social edge behavior. * AI Settings - provider/model, prompt family/tier, risk behavior, temperature, and max tokens. * TP/SL - Autopilot-specific TP/SL rules and independent monitoring. * Extra Features - bot-owned overlays and explanation surfaces. * House Money Mode - optional profit-protection/capital-lock behavior. * Presets and saved profiles. AI Strategy Chat - currently removed from the Telegram menu; normal AI model settings remain in the service settings menus. Launch Probe Buy is a current Trading Rules setting. It can stage a fresh-launch entry in two legs; the staged follow-up is owned by Launch Probe itself, not by a separate hidden strategy. Current Extra Features / explanation surfaces can include: • Behavior Hub / Effective Setup • Shadow Alpha • Experimental AI • Math Controller AI • Execution Guardrails • Catastrophic Filters / Conviction Rule • Math Controller / experimental overlays where enabled AI AutoPilot Behavior Hub can show: • Experimental AI Options ON • Plain-English Behavior Summary Behavior Hub = read-only summary of the effective setup produced by your current config. Behavior Hub is an explanation surface for the effective setup, not a secret extra brain. Execution Guardrails is an advanced Autopilot execution-sizing / posture menu under Extra Features. Experimental AI settings, Math Controller AI, Shadow Alpha, Execution Guardrails, and Catastrophic Filters are advanced overlays and may be hidden or disabled by admin gates. Admin master OFF makes the feature hidden/inert. Shadow Alpha can be disabled or hidden globally by admin; when hidden it can become inert. Admin gates can make some overlays hidden or inert. Conviction Rule current meaning: it is handled inside the Catastrophic Filters area as a strong-signal safety concept, not as its own peer menu surface. Prompt families and tiers: * Adaptive Generalist - all-around style for mixed markets. * Launch Hunter - fresh launches and early asymmetric entries. * Momentum Rider - continuation/trend-following style. * Compound Builder - fewer higher-quality entries and steadier compounding. * Value Accumulator - patient discounted-quality thesis trading. * Blue-Chip Rotation - relative-strength rotation across higher-liquidity names. * Simple / Moderate / Advanced tiers adjust doctrine detail for model capacity. AI Risk Behavior: * Safe - higher score/confidence threshold, smaller position cap, stricter risk-off buying. * Balanced - middle-ground defaults. * Aggressive - lower thresholds, larger allowed sizing, more opportunity capture. Core AI Risk Behavior enforcement applies after model output even when advanced Execution Guardrails are OFF. Advanced Execution Guardrails are a separate layer for stricter structure, rollover, generic-reason, existing-position-add, and conviction-style checks. Max Tokens default is 800. Manual input accepts 100-4000. Temperature default is 0.2; lower values are more consistent, and higher values are more experimental. =============================================================================== 13. Copy Trading =============================================================================== Path: Main Menu -> Copy Trading Copy Trading follows configured wallets according to your copy settings. Do not copy every wallet blindly. Start with one or two targets, review behavior, and use tiny live sizing before scaling. Common Copy Trading concepts: * paper or live copy mode where supported; * fixed-size or percentage sizing; * mirror sells; * target-wallet management; * liked wallets and target discovery flows; * Copy TP/SL; * Copy AI Guardrails and Top Performers AI where enabled; * wallet quality filters. Top Performers lives under Copy Trading and may be admin-gated. Current mirror-sell behavior: * Mirror sells apply to open copied positions. * If SamuraiX did not copy the buy or no open copied position exists, the sell is skipped silently instead of warning about a position the user never held. * If an open copied position exists but balance data is missing, SamuraiX can warn because it expected a balance. * Very small partial sells may fall back to a cleaner full-position exit when the partial size is too small or cannot route. =============================================================================== 14. Limit Orders =============================================================================== Path: Main Menu -> Limit Orders Limit Orders let you define price-triggered buys/sells and managed checks. They are useful for planned entries, planned exits, and paper testing of trigger behavior. Current Limit Orders concepts include: * live or paper mode where supported; * active orders and history; * Run Limit Check Now; * quick-create flows and manual create flows; * presets and built-in ladders; * risk/execution settings such as max slippage, min liquidity, max spread, check interval, expiry, max fills per check, and seconds between fills; * Limit AI Labs where enabled. AI Labs and advanced ladder helpers should be treated as controlled assistance, not a promise that every trigger will be safe to execute live. =============================================================================== 15. Speed Tip, MEV Settings, Rug Shield, And Managed Tokens =============================================================================== Speed Tip: * Lives in Settings as the single global paid speed setting. * Applies across supported live execution services such as Manual, Limit Orders, Auto Sniper, SLSR, Copy Trading, AI Auto Pilot, TP/SL, and Rug Shield sells when those services use the shared live executor. * Is charged only after successful live trades. * Is separate from MEV/Jupiter priority fees. * May be waived for users with a Free Max Speed entitlement. MEV Settings are bot-wide for supported trades. They control route/priority and anti-frontrun behavior where supported; they are not the same as Speed Tip. Rug Shield is bot-wide for supported buy sources and can monitor Manual, Auto Sniper, AI Auto Pilot, Copy Trading, Limit Orders, and SLSR where supported. Treat Rug Shield as risk reduction, not a guarantee. Managed Tokens and fallback burn-address settings help control token lists and cleanup destinations. Review them carefully before relying on send/burn flows. =============================================================================== 16. Notifications, Discord, And Help Downloads =============================================================================== Path: Main Menu -> Settings Settings contains bot-wide and account-level controls: * Timezone * Operation Mode * Managed Tokens * Fallback Burn Address * MEV Settings * Speed Tip * Rug Shield * Media Preview * Settings Help Admin-controlled visibility: * Network switcher only appears if admin enables it. * Notification Center is hidden by default unless admin enables it. * Paper Trading Subscription only appears if admin enables that manager. * Admin Controls only appears to accounts with admin access. Settings Help explains only the settings rows currently visible for your account. Download Full User Guide button inside Settings Help sends the current standard guide. The owner receives the admin guide from the same download route. The main SamuraiX menu includes a SamuraiX Discord button. Discord is used for community support, onboarding, announcements, and premium Samurai role access. For SLSR, Discord is also the premium entitlement source: Whop updates the Discord Samurai role, and SamuraiX checks the linked Discord role before SLSR access when the SLSR gate is ON. =============================================================================== 17. Troubleshooting =============================================================================== If a mode will not activate: * Check API Keys Hub first. * Confirm Helius/RPC, Jupiter, and at least one AI provider if the mode requires them. * Check Operation Mode for setup warnings. * Confirm the wallet has reserve SOL. * Confirm the service has its own amount, slippage, and safety prerequisites. * Check whether an admin gate is hiding or disabling the feature. If AI Auto Pilot behaves differently than expected: * Check prompt family/tier and selected style preset. * Check AI Risk Behavior. * Check temperature and max tokens. * Check the selected AI provider and user-owned fallback providers. * Check whether advanced Execution Guardrails are admin-enabled and user-enabled. * Remember that prompt previews are doctrine-only; live cycles inject dynamic settings, positions, P&L, candidates, fees, and TP/SL state each cycle. If SLSR access fails: * Confirm the SLSR premium gate state. * Confirm the linked Discord account has the allowed Samurai role. * If the wrong Discord account is linked, use Link/Replace Discord or Clear Discord Link and complete the DM-code flow again. * If Discord DMs are closed, allow DMs from the server or make the account reachable before verification can finish. If guide content looks stale: * In-bot normal users receive the current standard guide download. * The owner receives the admin guide from the same download route. * Public website and Discord copies should match the same standard guide text so users do not receive conflicting instructions. =============================================================================== 18. Final Safety Checklist =============================================================================== Before live trading: * I know which wallet is selected. * I have reserve SOL. * I configured my own required provider keys. * I understand my Operation Mode and Runtime Promotion stages. * I know whether I am using paper, shadow, or live behavior. * I know the source of the candidate/token. * I know the amount, slippage, and exit plan. * I reviewed TP/SL and Rug Shield where applicable. * I can find Transaction History And Exports after the trade. Start small. Slow down when something looks unclear. Ask for help without posting secrets.