=============================================================================== SAMURAIX TRADING BOT - STANDARD USER GUIDE Refresh: 2026-06-04 =============================================================================== This guide describes the current standard SamuraiX user experience. It is written for normal users in the current public/default setup: Owned Keys mode, Helius first, optional free fallback RPC providers after Helius, QuickNode last as trial/paid overflow, and feature visibility controlled by admin gates where needed. 1. What SamuraiX Is ------------------------------------------------------------------------------- SamuraiX is a Telegram-based Solana trading bot with multiple trading lanes: * Wallet management * API Keys / bring-your-own providers * Manual Trading * Auto Sniper * AI Auto Pilot * Samurai Legion Sniper Range (SLSR) * Copy Trading * Limit Orders * Holdings, Managed Tokens, and history * Per-service TP/SL management * Bot-wide Speed Tip, MEV Settings, and Rug Shield * SamuraiX Discord access and support * Notification Center when admin makes it visible The bot is menu-driven. Commands still exist, but the safest path is usually to use the visible menu buttons so you stay inside the right service flow. 2. Safety First ------------------------------------------------------------------------------- * Never share your seed phrase or private key. * Start small. Fresh launches, copy trades, and AI decisions can all be wrong. * Keep SOL available for priority fees, rent, swaps, and slippage. * TP/SL, Rug Shield, MEV protection, AI checks, and guardrails reduce risk. They do not remove risk. * If a button is missing, it may be admin-hidden, service-specific, or moved into another menu. It does not necessarily mean the feature is gone. * Paper or simulation paths, where present, are learning aids only. They are not proof of live profitability or safety. * Speed Tip is a paid execution-tier fee collected to the configured fee wallet after successful live trades. It is separate from Jupiter/MEV priority fees and does not guarantee a profitable fill. 3. Current Provider / API Key Model ------------------------------------------------------------------------------- Current standard mode is Owned Keys. Normal users should configure their own required provider access in the main-menu API Keys hub. Admin/shared key behavior is an admin operation, not something standard users should assume. Required for normal trading activation: * Helius - primary Solana RPC/read/WebSocket provider. * Jupiter - swap quote/routing/execution access through a Jupiter portal key. * At least one AI provider - OpenAI, Claude, Ollama, or LM Studio. Helius is first across the bot. Optional fallback RPC providers are tried after Helius in the order you set. If Helius free-plan credits or limits run out, you have practical choices: * add free fallback RPC providers such as OrbitFlare, Alchemy, GetBlock, or Ankr; * upgrade Helius or another paid provider; * keep QuickNode as the last optional fallback/overflow provider; * wait for monthly Helius free credits to recharge if you want to stay free. Optional providers: * Free fallback RPC providers - optional Solana RPC/data backups behind Helius. * QuickNode - optional last Solana RPC/WSS fallback or extra paid capacity. * Birdeye - optional richer market data; Multi-Timeframe can use a lot of Birdeye API credits and defaults off. * GoPlus - optional authenticated token tax/security checks; public/free checks can work but may rate-limit or return no result. * Telegram, Discord, Twitter/X - optional user-owned social integrations. Local AI options: * Ollama - self-hosted local model endpoint. * LM Studio - self-hosted OpenAI-compatible local model endpoint. Cloud AI options: * OpenAI - API key required, pay-per-use. * Claude - Anthropic API key required, pay-per-use. AI provider fallback: * SamuraiX tries the selected AI provider first. * If that provider fails, the bot tries the user's other configured AI keys/endpoints when the service supports model fallback. * In Owned Keys mode, normal users fall back only to their own configured AI keys/endpoints. * Owner/shared runtime AI keys are used only when admin/shared access or User Keys Bypass explicitly allows it. 4. Main Menu ------------------------------------------------------------------------------- The current main menu can show: * Refresh * Wallets * Transaction History * Manual Trading * Auto Sniper * AI Auto Pilot * Samurai Legion Sniper Range * Copy Trading * Limit Orders * Holdings * API Keys * Check Wallet for Unmanaged Tokens * SamuraiX Discord * Help * Settings * IMPORTANT: How TP/SL Actually Works Current main-menu status lines can show network, Auto Sniper, SLSR, AI Auto Pilot, Copy Trading, Limit Orders, and Rug Shield state. Important current layout notes: * Paper Trading is not a standalone main-menu button. * Sell is not a standalone main-menu button. * Send is not a standalone main-menu button. * TP/SL is not one global main-menu control. Those capabilities exist inside service menus, position views, Holdings, paper submenus, or command flows. 5. Wallets ------------------------------------------------------------------------------- Wallets controls which Solana wallet SamuraiX acts on for your account. Current wallet actions include: * Create Wallet * Import Private Key * Select Wallet The active wallet is the wallet used for live actions, balances, holdings, trades, sends, and cleanup flows. First wallet creation auto-selects the wallet and prompts for timezone setup. 6. Transaction History And Exports ------------------------------------------------------------------------------- SamuraiX separates bot-focused trade history from broader wallet history. Bot/trade history can include: * manual bot trades; * Auto Sniper trades; * AI Auto Pilot trades; * SLSR buys and exits; * TP/SL-triggered exits; * Copy Trading actions; * Limit Order fills. Wallet-level history can include direct wallet activity outside SamuraiX when chain history is available. Use stricter confirmed-only views for clean reconciliation and broader views when debugging submitted or pending paths. 7. API Keys Hub ------------------------------------------------------------------------------- Path: Main Menu -> API Keys The API Keys hub is the standard place for users to add and manage provider access. Service menus remain browseable, but trying to activate a service before required setup is ready will bring you back to API Keys. Required - Free access available: * Helius - raw API key, optional HTTPS RPC URL, optional WSS URL. * Jupiter - portal key for api.jup.ag. Helius and Jupiter setup are free and easy to get, although Jupiter still needs a portal key for reliable live trading. Required - choose at least one AI option: * OpenAI - paid cloud AI. * Claude - paid cloud AI. * Ollama - free/local AI endpoint. * LM Studio - free/local OpenAI-compatible endpoint. The selected AI provider is tried first. If it fails, SamuraiX can try your other configured AI keys/endpoints. Owned Keys mode does not silently fall back to owner/shared AI keys unless admin/shared access or User Keys Bypass allows it. Skip All This: API Keys includes a Skip All This / Public Routes button for users who want to try the bot before finishing setup. The warning is intentionally strong: skipping is allowed, but not recommended for normal use. If you proceed anyway, SamuraiX stores that choice for your user only, sends you to Operation Mode, and forces Truly Free plus Cost-Optimized until required setup is finished. Public endpoints can rate-limit, lag, or miss token data; swap routing can be less reliable without Jupiter; and AI-backed features run without model-backed AI until you add OpenAI, Claude, Ollama, or LM Studio. Optional Fallback Data RPC (Free): Open this submenu from API Keys. These providers sit behind Helius. The free fallback providers are free and easy to get, and most also have paid upgrades. Add all or as many as you can, then set order numbers: 1 is first fallback after Helius, 2 is second, and so on. * OrbitFlare - optional API key or full Solana RPC endpoint. * Alchemy - optional API key or full Solana RPC endpoint. * GetBlock - optional access token or full Solana RPC endpoint. * Ankr - optional API key or full Solana RPC endpoint. Optional Data, RPC & Safety (paid): * QuickNode Fallback - full HTTPS endpoint URL and optional WSS endpoint. Keep it last because public access is trial/paid-limited. * Birdeye Controls - key plus per-operation switches. * GoPlus - app key and optional app secret. Optional Socials: * Telegram bot token * Discord bot token * Twitter/X API token Provider pages include setup guides and direct provider links. Deleting or pausing a key affects only your user-owned provider setup. 8. Manual Trading ------------------------------------------------------------------------------- Path: Main Menu -> Manual Trading Manual Trading is a hub. Current manual surfaces include: * Refresh * Manual Paper Menu * Reset P&L * Buy/Snipe * TP/SL * Live Manual Positions * Burn Worthless Manual sells are usually reached from Live Manual Positions, Holdings, or the /sell command. Send flows exist inside Holdings/service-specific send-all paths or command flows. Manual TP/SL Independent lives in Manual Trading. When enabled, manual TP/SL monitoring can keep managing manual positions independently of other service state. 9. How TP/SL Works ------------------------------------------------------------------------------- TP/SL is service-aware. SamuraiX does not treat all positions as one generic bucket. Core rule: * Sell percentage applies to your current remaining position, not your original position size. Example: * TP +20% sell 80% leaves 20% of the position. * TP +35% sell 10% then sells 10% of the remaining 20%. * That second sell is 2% of the original size. Current TP/SL surfaces include: * Manual TP/SL * Auto Sniper TP/SL * AI Auto Pilot TP/SL * Copy Trading TP/SL * Paper TP/SL where supported * Limit Orders TP/SL * SLSR TP/SL Independent TP/SL toggles are explicit-enable controls. When a service-specific independent toggle is ON, that service's TP/SL management can keep monitoring eligible positions even if the service itself is not actively buying. This is useful, but it should be used intentionally. SLSR has extra AI TP/SL controls: * AI TP/SL Override can let SLSR AI-suggested TP/SL rules manage a token after a permitted SLSR buy. * No AI Take Profit and No AI Stop Loss can block AI from controlling those sides while user rules still work if configured. 10. Holdings, Managed Tokens, Send, Burn, And Cleanup ------------------------------------------------------------------------------- Path: Main Menu -> Holdings Holdings is the all-wallet token hub. It can show wallet-held tokens across services and gives access to token-level sell/send/burn flows. Common Holdings actions include: * Sell All Holdings * Send All Holdings * Burn Worthless * service-scoped send-all flows where available Managed Tokens lives in Settings and groups tokens by service source: * Manual * Auto Sniper * SLSR * AI Auto Pilot * Copy Trading Check Wallet for Unmanaged Tokens is different from Managed Tokens. It scans the wallet for token accounts that are not currently managed by SamuraiX service state. It intentionally treats known service-owned tokens as managed, including SLSR, active TP/SL overrides, paper rows, copy-paper rows, and recent trade history fallback rows. Fallback Burn Address: * Lives in Settings. * Used only when normal burn/incinerator cleanup cannot complete. * It is not the same thing as the Send All Holdings destination. Send All destination: * Entered inside explicit Send All flows. * Used for holdings transfer, not burn fallback. 11. Auto Sniper ------------------------------------------------------------------------------- Path: Main Menu -> Auto Sniper Auto Sniper is rules-based sniping. It uses configured filters before buying: * amount and slippage; * liquidity and market cap; * holder-count range when holder data is available; * token age, including Max Age and Min Age; * score / buy-count rules; * cooldowns and max buys per window; * anti-honeypot and link requirements; * DexScreener and Birdeye source modes where enabled; * TP/SL rules. Rug Shield is now bot-wide from Settings. Service menus should not be treated as owning separate Rug Shield toggles. Current age behavior: * Max Age is value-driven. Set it to 0/off to disable the upper-age filter; any positive value is enforced. * Min Age is value-driven. Set it to 0/off to allow brand-new tokens; any positive value requires the token to be at least that old. * Plain numeric age input means minutes. For example, 5 means 5 minutes. * Seconds input such as 30s is rounded to the smallest representable 1 minute value instead of silently turning the filter off. Speed Tip is no longer configured inside Auto Sniper. Use Settings -> Speed Tip for the one global paid speed setting. Free Max Speed users can have that fee waived by admin/owner entitlement while keeping their speed tier. Holder-count behavior: * Min Holders and Max Holders are separate filters. * If Min Holders is enabled and holder data is missing, Auto Sniper skips the token because it cannot prove the minimum. * If Max Holders is enabled and holder data is missing, Auto Sniper does not skip only because the maximum cannot be checked. * Impossible ranges, such as Min Holders higher than Max Holders, are rejected in settings. Social scanner tokens and channel/source lists do not live in Auto Sniper anymore. Auto Sniper keeps token link requirements such as website, Twitter/X, Telegram, or Discord links. AI Auto Pilot Social Intelligence owns social scanner tokens, channel lists, exclusions, source weights, and Social Edge. 12. Samurai Legion Sniper Range (SLSR) ------------------------------------------------------------------------------- Path: Main Menu -> Samurai Legion Sniper Range SLSR is SamuraiX's premium Solana call-source lane. It watches enabled source feeds for Solana token mints and can place real buys quickly when the SLSR master switch, source toggle, wallet, API keys, and settings are ready. Premium access model: * SLSR access is based on Whop -> Discord -> SamuraiX. * Whop handles checkout and subscription billing. * The active paid buyer role is the Discord Samurai role. * SamuraiX checks the linked Discord account for the allowed Samurai role or allowed Samurai Legion staff/category roles before opening or using SLSR. * If Whop removes the Samurai role because a user cancels or stops paying, SamuraiX performs a fresh role check on SLSR access/action and should block the user again. * If the SLSR gate is OFF by admin, the Discord role gate is intentionally not enforced. In normal premium operation the gate should be ON. Linking Discord for SLSR: * Link Discord / Replace Discord lets you connect the Telegram user to a Discord account for SLSR access checks. * Typing a Discord username or numeric Discord user ID is not enough by itself. * SamuraiX sends a one-time code to that Discord account by DM. * The user must enter that code back in Telegram before the link counts. * Linking again replaces the previous Discord identity, clears stale cached roles, and refreshes against the new Discord account. * Clear Discord Link removes the saved Discord identity and cached role result. After clearing it, the user must link Discord again before SLSR can pass the premium role gate. * If Discord DMs are closed, the user may need to allow DMs from the SamuraiX server or otherwise make the account reachable before verification can finish. 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. * AI blockers are intentionally narrow so SLSR can still trade volatile meme pump candidates instead of blocking every high-volatility runner. * 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 has SLSR-scoped sell, send, and burn actions. * Manual SLSR bypasses are Telegram user ID bypasses. They allow SLSR bot access only; they do not grant the Discord Samurai role or open private Discord channels. SLSR is Solana-only. Non-Solana/EVM posts should not be routed into the Solana SLSR trading path. When SLSR uses the shared live executor, the global Settings Speed Tip and any Free Max Speed waiver are resolved through the same execution-priority path as other live services. SLSR learning/runtime notes: * SLSR is part of SamuraiX, not a separate OpenClaw cron agent. * The main bot runtime handles menus, settings, access checks, role linking, clear-link actions, normal SLSR actions, and in-bot learning/report refreshes. * The separate SLSR Telegram watcher is only the source-intake listener that can feed Discord/Telegram source calls into SamuraiX. * A separate SLSR learning worker may exist for optional background learning work, but normal in-bot SLSR use is not dependent on an OpenClaw cron agent. * Learned blocker buckets are data-derived. The stricter 100/0 bucket means only patterns with 100% losers and 0% winners; the looser 60/40 bucket allows patterns with at least 60% losers and no more than 40% winners. * Update Blockers snapshots the current aggregate learning data into the active learned blocker set. 13. AI Auto Pilot ------------------------------------------------------------------------------- Path: Main Menu -> AI Auto Pilot AI Auto Pilot can run in Off, Paper, or Live mode depending on your settings and activation state. The AI is not a magic permission layer; it receives your real settings and runtime state every cycle and its actions are still filtered by rules, sizing, risk controls, service state, 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, and service behavior. * Data Sources - DexScreener, Birdeye, and market source modes. * Social Intelligence - optional social context, Twitter/X, Telegram, Discord scanner tokens, channel/source lists, exclusions, source weights, and social-edge weighting. * AI Settings - provider/model, prompt family/tier, risk behavior, temperature, max tokens. * TP/SL - Autopilot-specific TP/SL rules and independent monitoring. * Extra Features - bot-only overlays such as Shadow Alpha, Experimental AI, Math Controller, Execution Guardrails, and Catastrophic Filters when admin allows them. * House Money Mode - optional profit-protection/capital-lock behavior. * AI Strategy Chat - currently removed from the Telegram menu; normal AI model settings remain in the service settings menus. * Presets and saved profiles. AI Auto Pilot no longer has its own paid speed-tip setting. Live Autopilot execution uses the global Settings Speed Tip when the execution path supports speed-tip collection. AI Social Intelligence is the owner of social scanner setup. If you are looking for Twitter/X, Telegram, or Discord scanner tokens or channel lists, use AI Auto Pilot Social Intelligence rather than Auto Sniper. 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 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. Admin gates can make some overlays hidden or inert. Shadow Alpha can be disabled or hidden globally by admin; when hidden it can become 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. Behavior Hub can show: • Experimental AI Options ON • Plain-English Behavior Summary Prompt families and tiers: The prompt family/tier is static trading doctrine. It tells the AI how to trade. It does not store current positions, P&L, candidates, or sample settings. Runtime context is dynamic. Every trading cycle rebuilds and injects current settings, positions, P&L, candidates, TP/SL state, fees, Shadow Alpha state, and execution context. Prompt families: * 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, cleaner exits, steadier compounding. * Value Accumulator - patient discounted-quality thesis trading. * Blue-Chip Rotation - safer relative-strength rotation across higher-liquidity names. Prompt tiers: * Simple - lower-context doctrine for 7B-14B or cheaper models. * Moderate - balanced detail for 14B-32B models. * Advanced - richest doctrine for 32B+ models with deeper context handling. Style presets: Selecting a style family aligns the matching preset/settings stack, not only the prompt text. For example, Compound Builder should behave as lower-churn compounding through its settings and doctrine together. 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 the model responds even when advanced Execution Guardrails are OFF: * min score and risk-off score boosts; * minimum confidence to buy; * risk-off new-buy caps; * base buy size and max buy cap. 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. * Normal AI decision cycles use the configured max. * Fast sell-only review cycles can auto-downshift to a smaller token budget for speed. Temperature: * Default is 0.2. * Lower values are more consistent. * Higher values are more experimental. AI provider fallback for Autopilot: * The chosen model/provider is tried first. * Other configured AI providers are fallback options. * In Owned Keys mode, fallback stays user-owned unless admin/shared access or User Keys Bypass explicitly permits runtime/shared keys. 14. Copy Trading ------------------------------------------------------------------------------- Path: Main Menu -> Copy Trading Copy Trading follows configured wallets according to your copy settings. Common concepts: * paper or live copy mode where supported; * fixed-size or percentage sizing; * mirror sells; * copied-wallet target management; * copy-specific TP/SL; * Copy AI Guardrails and Top Performers AI where enabled; * wallet quality filters. Do not copy every wallet blindly. Start with a small number of targets, review their behavior, and use tiny live sizing before scaling. 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 the user about a position they never held. * If there is an open copied position but balance data is missing, SamuraiX can warn because it expected a position to exist. * Very small partial sells may fall back to a cleaner full-position exit when the partial size is too small or cannot route. * Top Performers lives under Copy Trading and may be admin-gated. 15. Limit Orders ------------------------------------------------------------------------------- Path: Main Menu -> Limit Orders Limit Orders let you define price-triggered buys/sells and managed order checks. Current Limit Orders concepts include: * live or paper mode where supported; * active orders and history; * Run Limit Check Now; * Auto-check interval; * max fills per check; * seconds between fills per token; * slippage, liquidity, and spread controls; * Risk / Execution Settings; * AI Labs for optional model-assisted limit decisions or dynamic ladder ideas; * Limit Orders TP/SL and independent monitoring. 16. Settings ------------------------------------------------------------------------------- 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 the admin paper subscription manager is enabled. * Admin Controls only appears to accounts with admin access. Operation Mode: * Lives in Settings for every user. * Shows required Helius, Jupiter, and AI setup status. * Pro+ RPC is the intended normal path once Helius is configured: Helius first, your fallback RPC order next, QuickNode last if configured. * Truly Free uses public/free endpoints where practical and locks Trading Profile to Cost-Optimized. * Optimal and Custom profiles require Helius. If Helius is missing, those buttons redirect you back to Helius setup. * Birdeye controls do not live here anymore; they live in API Keys. 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 collected to the configured fee wallet. * Is separate from MEV/Jupiter priority fees. * May be waived for users with 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, Limit Orders, and SLSR where supported. Settings Help explains only the settings rows currently visible for your account. The Download Full User Guide button inside Settings Help sends the current standard guide file to normal users. Download Full User Guide button inside Settings Help sends the current standard guide. The owner receives the admin guide from the same download route. SLSR Discord link management appears in the SLSR access/settings flow: * Link/Replace Discord starts the DM-code verification flow. * Clear Discord Link opens a confirmation screen with Cancel and Clear. * Clear removes the stored Discord identity and cached role result. * After clearing, SLSR requires the user to link Discord again before premium Discord role access can pass. 17. Notifications And Discord ------------------------------------------------------------------------------- Notifications can be delivered to Telegram or Discord depending on your setup, admin configuration, and feature visibility. Notification Center may be hidden in Settings unless admin enables it. Some system/service notifications can still happen independently of a visible Notification Center toggle when they are part of a required safety or trade workflow. 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 that linked Discord role before SLSR access when the SLSR gate is ON. Never post seed phrases, private keys, provider API secrets, or wallet exports in Discord support channels. 18. Troubleshooting ------------------------------------------------------------------------------- No AI option available: * Open API Keys. * Add OpenAI/Claude, or point SamuraiX at a working Ollama/LM Studio endpoint. * In Owned Keys mode, normal users need their own configured AI provider. * Fallback cannot use an AI provider that the user has not configured unless admin/shared access or User Keys Bypass explicitly allows runtime/shared keys. Helius errors or rate limits: * Check your Helius key/RPC URL. * Add one or more free fallback RPC providers and set their fallback order. * Upgrade Helius or another paid provider if you need guaranteed higher capacity. * Keep QuickNode as the last optional fallback/overflow provider. * Wait for monthly free credits to recharge if you want to stay fully free. Jupiter trading fails: * Confirm a Jupiter portal key is saved. * Check wallet SOL balance and slippage/routing settings. Birdeye usage is high: * Open Birdeye Controls. * Turn off Multi-Timeframe or other expensive operations. GoPlus rate-limits: * Public/free checks may rate-limit. * Add GoPlus app key/secret for authenticated access if you need reliability. SLSR says Discord link is required: * Open SLSR and use Link/Replace Discord. * Enter your own Discord username or numeric Discord user ID. * Check the DM sent by the SamuraiX Discord bot for a one-time code. * Enter that code back in Telegram. * If you do not receive the DM, allow DMs from the SamuraiX server or make sure you entered the correct Discord account. SLSR says Samurai role is required: * Confirm your Whop subscription is active. * Confirm Whop assigned the Samurai role to the same Discord account you linked in SamuraiX. * If you linked the wrong Discord, use Link/Replace Discord or Clear Discord Link and link the correct account. * If the Samurai role was removed because the membership stopped, SLSR access will be blocked on the next fresh role check. TP/SL did not fire: * Check the service-specific TP/SL menu. * Confirm the position belongs to the service you are configuring. * Confirm independent monitoring is ON if you expect TP/SL to keep managing positions after a service stops buying. A token appears unmanaged: * Use Managed Tokens to see known service-managed rows. * Use Check Wallet for Unmanaged Tokens for wallet-level cleanup detection. * Do not burn/send anything unless you are sure it is not an active position. 19. Good Operating Practice ------------------------------------------------------------------------------- * Configure required API keys first. * Learn the main menu before enabling live trading. * Use small size. * Change one setting at a time. * Keep a SOL fee reserve. * Review Managed Tokens and Holdings before cleanup actions. * Treat AI output as an assistant inside guardrails, not as certainty. * Never let urgency override wallet safety. =============================================================================== END STANDARD USER GUIDE ===============================================================================