Solana memecoin trading,
emotion-free.

Executive Summary

emoX sits between two extremes in the Solana trading-tool landscape: the firehose of Axiom (everything, zero curation) and the chat-only feel of Trojan (Telegram bot, no charts, no real coin visibility). We give you a curated, structured live feed with real charts, dev intelligence and dev wallet history, paired with a fully automated lifecycle — every position is managed by a saved strategy with stop loss, ratcheting profit levels, partial sells and a moonbag remainder.

New users get 24 hours of Demo mode with 10 virtual SOL to learn every menu — no risk, full feature parity (Auto-Buy included). Real-mode trading runs through your own dedicated Solana wallet that the platform never has custody beyond a server-encrypted hot key for execution.

Everything below describes what is actually in production today, not roadmap aspirations. Where a feature is in development we mark it explicitly under §14 Roadmap.

The Problem We Solve

Memecoin trading punishes humans on two axes: speed and emotion. The edge isn’t only “finding the call” — it’s executing a plan when your nervous system wants to do the opposite.

Positioning vs. Other Tools

Call Engine — Categories & Filters

Every detected token is classified into one or more category lanes. Each lane carries its own quality filter set — continuously back-tested and re-tuned by us — and can be wired to its own Auto-Buy rule, sizing and strategy.

4.1 Verified Calls flagship

Verified is our highest-confidence lane. A coin must pass every active V1 filter constraint inside our internal screening engine to be flagged Verified and broadcast. Filters operate on a multi-dimensional feature vector measured at the moment of the call:

• Bundler structure — total bundler count, initial bundle %, current bundle % of supply.
• Holder distribution — total holder count, one-buy holder share, top-10 holder concentration.
• Microstructure — average time between trades, buy pressure (% of trades that are buys), total SOL volume in window.
• Dev signal — dev’s initial SOL injection, age of the token at call time.
• Market structure — entry market cap band, on-chain bonding state.

Filters are tuned by an admin-side back-test playground. We replay 30 days of historical calls against candidate filter combinations, measure realised win-rate (% of calls that hit ≥ +50% ATH from entry) and average ATH, and only promote a filter once it beats the current baseline on both metrics. The same engine runs in production live — no divergence between back-test and reality.

An Auto-OR-Composer additionally searches the filter space combinatorially: it finds non-overlapping filter variants that each capture a distinct sub-segment of high-win-rate calls, then unions them. This lets us widen coverage without diluting quality. The Verified lane today typically runs 2–5 simultaneously active variants; the user-facing Call History applies the exact same union live.

4.2 Mooner Calls momentum

Mooner is our aggressive early-momentum lane. It activates only after a token has shown verifiable real-time strength: rapid holder growth, sustained buy pressure, and a qualifying market-cap trajectory inside a short window after launch. The lane is intentionally higher-variance — bigger ATHs, more failures — so it is best paired with smaller per-trade size and tighter stop / partial-sell ladders on the Strategy side.

Each Mooner candidate carries a mooner_qualified_at timestamp and the market cap at the moment of qualification. The Mooner lane uses its own independent filter set (V2) tuned the same way as Verified.

4.3 Pre-Bond Calls high risk

Pre-Bond targets tokens spotted before they graduate the pump.fun bonding curve to Raydium. You are entering ahead of the public listing wave — highest theoretical upside, highest risk of fizzling. The filter set (V3) is independent from V1/V2 and gates on early-stage signals (bundler quality, holder velocity, top-10 concentration) tuned specifically for the pre-bond micro-structure.

Recommended pairing: smaller fixed buy size, wide stop loss, an aggressive partial ladder so you de-risk fast if the bond completes successfully, and a moonbag to ride the post-Raydium discovery wave.

4.4 CTO Calls community takeover

CTO = Community-Takeover. After an original dev abandons, quits or rugs the social channels, a fresh community sometimes takes over marketing and governance of a still-live token. emoX detects these events via DexScreener community-takeover signals and live social activity tracking. Each CTO call card shows:

• Time since takeover.
• Current community size (followers, channel members where available).
• Liquidity, market cap and price relative to pre-takeover baseline.
• Whether the token is currently bonded / listed.

CTOs are unpredictable in timing but historically over-represented in surprise runners — the social re-launch gets a second wave of attention that the original launch never had.

4.5 Dev Launches repeat devs

Dev Launches are brand-new tokens from developer wallets with a track record we already classified. For each known dev we track:

• Total launches — how many tokens this wallet has ever created.
• Bonding rate — % of those launches that completed the pump.fun curve and graduated to Raydium.
• Median ATH multiple across the dev’s past launches.
• Last-10-launch chart and dev wallet history right on the coin card.

On Auto-Buy, you can set a minimum bonding-rate threshold per rule — e.g. fire only if this dev has historically bonded ≥ 25% of their launches. Combine with size and strategy assignment to follow specific dev archetypes (high-bonding, slow-build, fast-flip) automatically.

4.6 Winner Calls leaderboard

Winner Calls is not a buy lane — it is a live leaderboard of the top-performing calls (sorted by realised ATH multiple since they were broadcast) across all lanes for the last 24 hours, 7 days and 30 days. Use it for:

• Market read — which lane is firing today? Mooner runs hot, Pre-Bond dry? Adjust your sizing accordingly.
• Setup study — click into the top performers and inspect what they had in common (dev, bundler %, holder count, launch timing).
• Filter feedback — winners that we missed on Verified are valuable signal for the next round of filter tuning.

Trading Engine — Strategy

Your Strategy is the brain that runs every trade after entry. The same configured strategy applies identically to manual buys, Auto-Buy fills, and Telegram-bot fills — there is no separate "manual mode" with different behaviour. You configure it once under Settings → Strategy and the bot executes it deterministically.

6.1 The full toolkit

6.2 Manual overrides during a trade

Strategy automation does not lock you out. From the position card you can at any time:

• Manual sell — all — immediate full-position exit, bypassing remaining profit levels.
• Manual partial sell — sell a chosen fraction (10/25/50/75/custom %) and keep the rest active under strategy.
• DCA (manual buy-add) — add to a position with another buy; new average entry recalculated automatically.
• Skip pending — cancel a position still in Dip-and-Recovery wait without firing.
• Pin to chart — keep the live DexScreener chart open for hands-on management while the bot still enforces the stop floor.

Auto-Buy Rules

Auto-Buy is the "set and forget" backbone of the platform. The moment the call engine flags a new qualifying coin, Auto-Buy fires the trade for you within milliseconds — far faster than any human reaction.

7.1 Rule structure

Rules are defined per category lane, so each lane can have its own size and strategy. You can stack multiple rules per lane (e.g. one rule fires on Verified-low-mcap, another on Verified-high-bundler-quality with bigger size).

1. Category — Verified / Mooner / Pre-Bond / CTO / Dev Launches.
2. Min. bonding rate % (Dev Launches only) — gate on dev’s historical pump.fun bonding ratio. Example: ≥ 25% only fires for devs that have historically bonded at least 1 in 4 of their launches.
3. Buy amount (SOL) — fixed size per fill for this rule. Use small sizes (0.05–0.2 SOL) on high-variance lanes (Mooner, Pre-Bond) and larger sizes on Verified.
4. Strategy — pick any saved strategy preset, or "Default" to follow your current Strategy tab settings.

7.2 Execution speed

From call broadcast to on-chain transaction submission, our typical Auto-Buy pipeline takes:

• ~10–30 ms — call engine pushes the qualifying coin to the trading engine via an internal SSE channel.
• ~20–80 ms — strategy build, slippage / priority-fee compute, transaction assembly, signing.
• ~100–400 ms — Jito bundle or RPC submission until first inclusion attempt.

A frontend SSE event fires the moment the buy submits — your position card appears with a "Buy submitted" tag before the on-chain landing, giving you instant feedback without waiting for confirmation latency.

7.3 Risk controls

• Wallet balance assertion — Auto-Buy never fires if your wallet balance is below buy amount + buffer. You get a clear "insufficient balance" event in the activity bar.
• Per-mode separation — rules configured in Demo do not auto-execute in Real, and vice versa. You explicitly switch modes under Settings → Wallet.
• Pause/Resume — single toggle to halt all Auto-Buy rules instantly (useful during news events or wallet maintenance).
• Per-rule enable/disable — keep a rule configured but turned off until you want it active.

Demo Mode

Every new account ships with 24 hours of free Demo mode and 10 virtual SOL. This is the recommended on-ramp: spend the first day learning every menu, click every button, watch how positions behave under live market data without risking a cent.

8.1 What is identical to Real mode

• The full Call feed — Verified, Mooner, Pre-Bond, CTO, Dev Launches, Winners — using live production data.
• The full Strategy editor — every parameter behaves the same.
• The full Auto-Buy lane — your rules fire on demo positions exactly as they would in Real.
• Manual buy / sell / partial sell / DCA / Dip-and-Recovery / Skip Pending.
• The Telegram bot — if you switch Wallet Mode to Demo, the bot also trades virtual SOL.
• Trading history with full PnL accounting in virtual SOL.

8.2 What is intentionally not realistic

• No on-chain slippage — your fills are at the displayed price exactly.
• No priority-fee competition — every Demo order "lands" instantly.
• No buy/sell latency — there is no Jito tip race and no failed transactions.
• No platform fees — Demo trades are uncharged.

Translation: Demo is a UI and behaviour tutorial, not a profit forecast. The only way to know how a strategy really performs is Real mode — but Demo gets you fluent on the workflow first.

8.3 Demo-only convenience tools

Two practice helpers that are deliberately not available in Real mode:

• Bulk Sell — close many open positions in one go filtered by PnL band, market cap range, or hours-open threshold. Useful for cleaning up Demo experiments fast.
• Delete Dead Pending — remove stale pending entries that are stuck below a market-cap threshold or older than N hours. Keeps the Demo dashboard tidy when you’re iterating on Dip-and-Recovery rules.

These would be dangerous on real money — they intentionally bypass per-trade confirmation. Hence Demo only.

Telegram Trading Bot

A dedicated Telegram bot is tied to the same account as the web app (same Telegram identity, same wallet, same strategy). It is built for parallel use: keep the desk on desktop, execute on the phone.

• Mint-first workflow — paste a Solana mint, the bot replies with contextual buy actions.
• Instant buy — optional mode: bot submits immediately using one of your four web-configured presets (slot #1–#4).
• Demo / Real parity — bot follows the same mode you set under Settings → Wallet on the web. No separate paper account.
• Positions & status — inline panels to list open positions and refresh state without opening the browser.

Referral Program — Tier-1 + Tier-2

Every account ships with a personal referral link. We share platform fees back with referrers in two tiers, lifetime:

Payouts auto-credit when your combined Tier-1 + Tier-2 pending balance reaches 0.25 SOL, sent to your bot wallet. The Settings → Wallet panel shows a full breakdown of both tiers, your direct/indirect referral counts, lifetime earned and pending balance.

Fees, Cashback & Airdrop

emoX has no subscription, no signup fee, and no deposit fee. You pay only on actual trade fills. A large portion of every fee flows back to users — through Tier-1/Tier-2 referrals, fee cashback, and an emoX token airdrop tied to your lifetime credited cashback.

11.1 Trading fee — 1% per fill

Every successful buy or sell carries a 1% platform fee, denominated in SOL and netted from the trade. There are no hidden surcharges and no priority-tier subscriptions — the rate is identical for all users in Real mode.

Where each 1% goes (per fill):

• 25% → Tier-1 referrer (lifetime, in SOL) — see §10.
• 5% → Tier-2 referrer (lifetime, in SOL) — only when the referrer themselves was referred.
• 25% → fee cashback credited to your trading wallet (see §11.2).
• Remainder → emoX operations (infrastructure, RPC, liquidity, dev team).

11.2 Fee cashback — paid in SOL

Every Real-mode fill credits 25% of the 1% platform fee back into your personal cashback balance, denominated in SOL. The balance updates live as your trades close and is visible at any time under Settings → Wallet → Fee cashback.

• Total credited — lifetime cumulative SOL you have earned in cashback (this is also the number that drives your airdrop allocation — see §11.3).
• Paid out — lifetime cumulative SOL already sent to your trading wallet.
• Available — current balance ready for payout.
• Payout — single click, sent directly to your bot wallet. No minimum threshold, no fee on payout.

11.3 Post-launch emoX airdrop — tied to your cashback

emoX is launching a token. Your lifetime credited fee cashback maps 1:1 into an emoX token allocation at launch — so every Real-mode trade you do today is simultaneously farming a real airdrop tomorrow. Launch is anticipated in 4–8 weeks from publication of this document.

Illustrative valuation — at our internal reference market cap of $1M, 1M emoX ≈ $2,000 USD. A fully-capped account (5M emoX) therefore corresponds to roughly $10,000 USD at that reference. This is the target band — actual market cap at launch may be higher or lower; nothing is guaranteed.

The allocation is fully transparent: open Settings → Wallet → Post-launch airdrop to see, in real time:

• Your total credited fee cashback in SOL.
• Your current emoX allocation (capped at 5M).
• An illustrative USD value using the $1M-mcap reference.

Disclaimer. Launch timing, exact distribution mechanics, claim flow, vesting (if any), and reference market cap can change before listing. The numbers above describe the program as it is running today in the app — they are not a price target or financial advice.

11.4 Withdrawal & deposit

• Deposit — send SOL to your dedicated bot wallet address shown in Settings → Wallet. Funds are usable instantly after a single confirmation.
• Withdraw — single click from Settings → Wallet → Withdraw, sent to any external address. Standard Solana network fee only; no platform fee on withdraw.
• Reveal private key — full self-custody escape hatch: open Settings → Wallet → Show Private Key at any time and export to Phantom/Backpack/Solflare.

High-Level Architecture

emoX is a single-tenant Node.js backend with a thin browser client and a Telegram bot, both consuming the same internal APIs. Everything sensitive lives server-side; the browser never sees private keys, vendor credentials or strategy primitives that could be reverse-engineered.

12.1 Component map

12.2 Real-time pipeline (a single Auto-Buy trace)

1. ZMQ event arrives in detection worker (~10 ms post-mint).
2. Worker enriches with SolanaTracker / DexScreener and computes the V1/V2/V3 feature vector.
3. Filter engine scores the coin against active variants. If a variant matches → push internal call.
4. Trading engine receives the call → loads the user’s matching Auto-Buy rule → assembles the transaction.
5. Wallet balance asserted → tx signed server-side → submitted via Jito bundle.
6. SSE event broadcast to the user: "Buy submitted" appears in the activity bar instantly.
7. On-chain confirmation lands → position card animates to active, PnL polling kicks in, strategy state machine starts running stop / profit ladder.

End-to-end median from ZMQ event to position visible in the user’s browser: ~250–600 ms under normal network conditions.

Wallet & Security

The wallet model is intentionally simple: one dedicated on-chain wallet per user, generated at signup, fully self-custodial via the "reveal private key" escape hatch. No pooled treasury, no shared liquidity pool, no platform that can freeze or rehypothecate your funds.

13.1 Wallet model

• Per-user dedicated wallet — generated at first login, exclusively yours, displayed in Settings → Wallet → Wallet Address.
• Server-encrypted hot key — required for the trading engine to sign your trades. Encrypted at rest with AES, decrypted only inside the signing path, never logged.
• Reveal Private Key — single-button export to plain text under Settings → Wallet. Import into Phantom / Backpack / Solflare at any time. You are never locked in.
• Withdraw — single-click send to any external address. Standard Solana network fee only; emoX takes no withdrawal fee.
• No custody beyond execution — emoX has no pooled treasury that controls user balances. If our service goes offline tomorrow, your wallet keys (revealable from settings) keep working forever on Solana.

13.2 Transport & auth

• TLS 1.3 everywhere — HTTP traffic, SSE channels, internal worker RPC.
• Telegram OAuth verification — every login validates the Telegram signature server-side; sessions are server-side cookies (httpOnly, sameSite).
• Least-privilege API scope — every endpoint enforces that the authenticated user can only touch their own resources. Admin routes carry an independent role check.
• CSRF-safe — state-changing endpoints require the session cookie + a same-origin fetch; no third-party can submit trades on your behalf.

13.3 Server & operations

• Hardened Linux host, no public DB port, firewall-isolated worker processes.
• Per-day PostgreSQL backups (pg_dump) with off-server replication.
• Structured logging for every trade lifecycle event — full audit trail for support and disputes.
• RPC provider redundancy — Helius primary, Alchemy fallback; automatic switch on failure or rate-limit.

13.4 What we explicitly do NOT do

• We do not co-mingle user funds in any pooled wallet.
• We do not ever push trade-signing code to the browser. Every signature happens inside the backend process you cannot reach.
• We do not share user wallets, trade history or strategy with third parties for marketing.
• We do not require KYC for trading. Telegram identity is the only authentication.

Roadmap

We ship continuously. The list below is intentionally short and concrete — anything not on it is currently out of scope, by design.

Now (next 4–8 weeks)

• emoX token listing & airdrop claim — the post-launch airdrop (§11.3) opens for claims. Allocation snapshot tied to your lifetime credited fee cashback at the snapshot block.
• Mobile-first responsive overhaul — full re-skin of dashboard, trade cards and modals for phone-grade interaction.
• Referral Contest — first season of the new referral leaderboard (25 pts Tier-1 / 5 pts Tier-2) with a 14 SOL total prize pool.

Next quarter

• End-user strategy back-tester — replay your saved strategy against the last 30 days of calls in any lane, see realised PnL distribution and stop-floor evolution.
• Whale-mirror lane — track a curated set of known profitable wallets and surface their first buys as a separate call lane.
• Social-spike lane — Twitter/X-mention velocity as a primary signal, gated by historical win-rate baselines.
• Cross-DEX routing — extend beyond pump.fun → Raydium graduation flow to also score Meteora and Orca early-stage tokens.

Later

• Native iOS / Android wrapper (push notifications for Auto-Buy fills, position alerts).
• Public REST API for read-only call data (rate-limited).
• Conditional cross-position rules ("if Position A hits +200%, automatically open Position B").

Risks & Disclaimers

• Memecoin trading is speculative — you can lose 100% of risked capital on any single trade.
• Slippage, failed transactions, RPC congestion and DEX behaviour can alter fills vs. intent.
• Automation reduces emotional error but not market risk; past performance of any lane does not guarantee future results.
• Demo mode does not model slippage / latency / priority-fee competition. Real-mode behaviour will differ.
• Third-party clients (e.g. Telegram) have their own availability and security considerations.
• This whitepaper is technical orientation, not investment advice. Always do your own research.