Getting Started

Quickstart

Start with live market data, then sign in with Telegram to use your bot wallets.

Explore without signing in

1. Open the Trade terminal for live pairs, charts, recent trades and holders.
2. Open the terminal on the main page and enter help. Use agents to see the twelve categories.
3. Use trending or venues for source-backed market observations. Check the timestamp and coverage next to the result.
4. Use conversation for general questions when the assistant is enabled. This mode cannot inspect your private bot account or execute a trade.

Sign in with the same Telegram account

Choose Login and approve the request in @elisisnipebot. Return to the same browser, then use status. If the bot connection is unavailable, the site says so and nothing is sent. An address or Telegram ID pasted into a prompt is not authentication.

Signing out ends the website session but keeps the approval you gave in the bot. To revoke it, use Disconnect from bot in the account menu, or revoke the website in Telegram.

Read before changing anything

wallets       review wallet names, roles and balances
positions     inspect holdings and available cost basis
history       inspect recorded trades and their status
limits        open trading permissions and limits
actions       open the bot operation forms

Prepare a first action

1. Choose the wallet and exact token contract. Inspect the token and request a quote.
2. Review amount, slippage and available risk checks. An estimate or simulation is not a completed trade.
3. Confirm the action on the site. If it also needs Telegram (see Confirmations), approve it there before it expires. Keep the operation ID and check its status after submission.

The Telegram bot keeps working on its own, and some operations stay in Telegram only. See Bot Capabilities for the list.

Elisia Guide

Prompts, Agents & Results

Use ordinary language to explain your intent. Keep identity, spending authorization and transaction evidence outside the model’s judgment.

Conversation and Bot modes

Ask a precise question

Explain this token using the available source data.
Show my open positions and mark unknown cost basis.
Review my paused AFK task without enabling it.
Check the status of operation <request ID>.

What attaching an agent does

Choose a catalogue role or enter attach trader. Trader focuses on trade context; Portfolio on holdings; Copy Trader on copied-wallet tasks. The same account and permission checks apply to every role. detach removes the specialist; it does not stop bot automation.

Read the result, not just the reply

• Read: returned balances, tasks or quotes are observations with their own freshness.
• Prepared: an operation has parameters to review. Nothing is proven submitted yet.
• Submitted or pending: execution has started but the final result is not known.
• Confirmed, failed or unknown: use the recorded backend state and transaction reference. A confident sentence is not a receipt.

Never paste private keys, seed phrases, Telegram passwords or API credentials into the terminal. Import wallets and export private keys or seed phrases only through @elisisnipebot in Telegram. These operations are excluded from the website and its external API.

Elisia Guide

Bot Capabilities

This reference lists 80 bot operations. Most are used from the website after Telegram sign-in. The ones marked “in Telegram” are done only in @elisisnipebot, and wallet import and key/seed export never pass through the website.

Two ways to use a capability

Account screens expose the website operations. Every change is confirmed by you on the site, with a confirmation tied to its exact arguments; withdrawals, bridge requests, HyperEVM transfers, wallet creation and deletion, live mode and risk-filter changes are also confirmed in Telegram. Import wallets and export private keys or seed phrases only in @elisisnipebot. The chat assistant has read tools only: it cannot submit or confirm an action.

Complete operation reference

What the marks mean

“In Telegram” operations are done only in @elisisnipebot. “Not on the website” operations are not offered here: a submitted trade cannot be cancelled from the website, and the bot’s chain-index catalogue is replaced by the public market data in the Trade terminal. Telegram signals are a bot-owner section; regular accounts do not have it. The website answers these requests with an explicit “unsupported” or “Telegram only” result and sends nothing.

Connection boundary

Website requests resolve to the approved Telegram account and its own wallets. The website reads structured bot records; it does not scrape Telegram replies to guess balances. The Telegram bot keeps running independently of the website.

When something is unavailable

Connection unavailable, permission denied, stale data and unknown execution status are different outcomes. Preserve the operation ID when a submission times out. Check that operation before trying a new one; a timeout does not prove it failed.

Elisia Guide

Automation: AFK, Copy, Orders & Signals

These are the bot’s automation families. After Telegram sign-in, AFK, copy and order tasks are managed from the website and each change is confirmed by you. Bulk actions and signals stay in Telegram. Enabling a task is separate from opening its editor.

AFK sniping

An AFK task selects a wallet, native buy amount, maximum buy count, slippage, priority fee and anti-snipe behavior. Filters can constrain creator-buy size, creator token count, a whitelisted deployer, exact or partial token names, start/end times, blocked words and deployers. Optional automatic orders define follow-up exits.

List and inspect tasks before editing. On the website you can save a task, save a copy as a new task, enable or pause it, reset its trade counter, or delete it. Enabling or pausing all tasks at once and assigning one sniper wallet to every task are done in Telegram. Review the active state and remaining buy count after every change.

Copy trading

Choose the target address and your executing wallet. Configure exact, percentage or fixed buying, a maximum buy, trigger-size and market-cap ranges, separate buy/sell fees and slippage, follow-sells, buy-once behavior and token-count limits. First-interaction and automatic-order settings are part of the task.

On the website tasks can be read, saved, paused or enabled, and deleted one by one. Pausing every task at once or deleting all copy tasks is done in Telegram. Following a wallet does not establish that it is profitable, safe or operated by the person you expect.

Conditional orders

Orders support buy or sell conditions based on profit/loss, target or changed market cap, trailing movement, developer selling, or elapsed time. Set the wallet, token, side, buy amount or sell percentage, fee, slippage and relevant reference values. Review expiry when applicable. Listing or creating an order does not mean its trigger has fired; deleting an order cannot reverse an already submitted fill.

The bot places an order on every enabled spot wallet. The website therefore creates an order only when the chosen wallet is your single enabled spot wallet; otherwise it refuses and nothing is created.

Telegram signals

Signal buying is a bot-owner section. Regular accounts do not have it, in Telegram or on the website, and the website answers “owner only”. For the owner, the website shows signal status and sources and edits the signal-buying settings; everything else stays in Telegram:

• Connecting or disconnecting the Telegram signal account. QR codes and passwords never pass through the website.
• Adding, editing or removing signal sources.

Elisia Guide

Elysium Market Data

Market data is live and public: it needs no sign-in. The source is Elysa. Read each number together with its timestamp and coverage.

What is live

What “trending” means here

The terminal presents the source’s discovery ordering. Summed volume in a discovery sample covers only the returned pairs with available values. It is not a leaderboard of smart wallets. Missing fields stay unknown.

Fresh, stale and unavailable

Market answers are cached for a few seconds (holders for up to 30 seconds). Check both retrieval time and source time when supplied. A recent fetch does not prove that the source observation is recent. Third-party data can be delayed or wrong. If the source fails, Elisia reports the data as stale or unavailable; it never substitutes a simulated price.

Token-level checks

After sign-in, token inspection and risk checks add the bot’s own context for a token. Token addresses identify assets more reliably than names. A chart or green risk result cannot guarantee liquidity, sellability or a future price.

Global-market widgets on the Intelligence page are broader market context from other public feeds, not Elysium chain totals. Read their source labels before comparing them with Elysium observations.

Elisia Guide

Balances, Positions & PnL

The bot’s holdings and execution records are the basis for account figures. A balance, an estimated exit value and realized PnL answer different questions.

Read a position

History and reconciliation

Use trade history for recorded operations and position history for a token’s account activity. Portfolio status helps establish the accounting context. Submitted transactions, pending fills and confirmed results remain distinct. External-history estimates should remain labeled, and missing basis must not be silently treated as zero.

PnL cards and hidden positions

On the website the PnL card returns the available figures as numbers; a rendered image card is produced in Telegram. Check its basis and quote before sharing. Hiding a position is done in Telegram. It changes the display only; it does not sell the token or remove it from the wallet.

Fees and available funds

A trade can consume native funds, gas, a selected priority fee and applicable bot or route fees. Read the actual quote and operation details; this guide does not promise a fixed fee. A low token balance does not replace the native funds needed for gas.

Budget is not performance

The diagram illustrates how a daily limit set in the bot is used up by actions. It is not a live balance or a return. Limits are the bot’s own settings; the website keeps no separate allowance. Inspect the recorded status of an uncertain operation before assuming it did not count.

Elisia Guide

Terminal Reference

Shortcuts open a view or request a read. Opening a trade form, attaching a specialist or switching mode does not submit a transaction.

Start and navigate

help                 show available shortcuts
agents               list bot-focused roles
attach trader        focus the conversation
detach               clear attached roles
conversation         general assistant mode
bot                  connected account mode
login                open Telegram sign-in
status               inspect connection status
clear                clear the visible terminal

Account and market shortcuts

wallets / positions / history
quote / inspect / orders
sniping / copy trading / signals
bridge / limits / actions / presets
trending / venues

inspect 0x…          open token inspection for a full contract address

Use help for the current command spelling. Account shortcuts require Telegram sign-in and a working bot connection; if it is unavailable, the terminal says so and nothing is sent. Public market commands report the source’s observations; ordinary conversation does not silently execute a wallet operation.

Useful requests

Explain the source and age of this price.
Compare my positions only where cost basis is known.
Review the parameters of this paused copy task.
Check my existing operation before retrying it.

Workspace controls

Double Shift searches commands, agents and local files. Arrow keys browse command history; Ctrl+L clears the terminal; F2 switches mode. Local workspace files are browser-side convenience files, not wallet backups or bot records. Stopping the visible reply does not prove that an already submitted operation was cancelled.

Elisia Guide

From Quote to Receipt

A trade needs a selected wallet, exact asset and reviewed execution settings. Keep quote, confirmation, submission and final state separate.

The trading workflow

1. Inspect: confirm the token contract and available token/pool information.
2. Quote: choose buy or sell and an exact amount. Recheck a quote if the market moves.
3. Review risk: inspect the checks that are actually available. Missing tax, liquidity or simulation data is not a pass. If the bot returns risk warnings for a buy, they are shown and must be accepted explicitly before that same trade can be sent.
4. Configure: select wallet, amount or sell percentage and slippage. Priority fee and anti-snipe use your saved bot settings. Some routes require token approval.
5. Confirm: review the prepared trade and confirm it on the site. If you turned on “confirm trades” in the bot, approve it in Telegram too.
6. Submit and follow: keep the request/operation ID and inspect its recorded status and transaction reference.

Simulation and approval

Simulation is a pre-execution check, not a guarantee that a later transaction will succeed. Token approval and the trade are separate operations. Approving spending is not a purchase or sale.

Amounts and units

Human-readable amounts in the interface must map to exact integer units. Buy amount, token amount, sell percentage, slippage and priority fee are different fields. A 100% sell means the selected holding; it is not a native-currency buy amount.

Timeouts and cancellation

If a response is lost, the site reports an unknown outcome. Check the existing operation first; repeating the same confirmed trade does not create a second one. A submitted trade cannot be cancelled from the website, and a confirmed chain transaction cannot be reversed. A retry with different parameters is a new action requiring its own confirmation.

Elisia Guide

Wallets, Transfers & Bridge

Manage wallet identity and funds through dedicated account controls. Sensitive material never belongs in the chat transcript.

Wallet management

Website wallet controls list, create, rename, assign roles and delete wallets. Creating and deleting a wallet is also confirmed in Telegram, and only an empty wallet can be deleted. Assign default, spot, copy and sniper roles deliberately: changing a role changes which wallet a workflow uses. A busy wallet can be refused for deletion; review task dependencies before removing it.

Restoring a deleted wallet is done in Telegram. Restoration uses retained bot wallet records and is not a guarantee that a lost secret can be recovered.

Custody, import and export

Bot wallets are created or imported in @elisisnipebot and their keys are held by the bot service, not by your browser. Use the bot in Telegram to import a wallet or export its private key or seed phrase. The website does not accept wallet secrets or return exported keys or seeds. Do not put these values in a prompt, shared screenshot, local workspace file or PnL card.

Transfers and withdrawal

Inspect the source wallet, destination, network, amount and applicable fee. Internal transfer controls distinguish Elysium and HyperEVM. A withdrawal to an external address is separate from a transfer between your own wallets. Confirm each on the site; a withdrawal and a HyperEVM transfer are also confirmed in Telegram. Track the request after submission; the same address format does not make networks interchangeable.

Bridge requests

1. Read bridge information and supported routes.
2. Choose deposit or withdrawal with the required wallet, native amount and destination.
3. Confirm the exact request on the site, approve it in Telegram, and follow its status.
4. Use claim only when the recorded bridge request is eligible.

Bridge deposit, withdrawal and claim are separate steps. Completion times and costs depend on the returned route and state; no instant-completion promise is made.

Withdrawal address lock

The withdrawal address lock is managed only in Telegram: set a permitted withdrawal address, request its unlock, or cancel the unlock request there. The bot’s unlock flow uses a 24-hour delay. The website cannot change the lock, and the bot still applies it to withdrawals started here. A lock is an account control, not a substitute for checking the network and recipient on every transfer.

Elisia Guide

The Twelve Bot Roles

Each catalogue role is grounded in a bot function. Roles organize the conversation and account screens; they do not add capabilities that the backend lacks.

Choose a role by the job

Use Trader for trade preparation, Token Research for asset evidence, and Portfolio for holdings. AFK Sniper, Copy Trader, Signal Monitor and Limit Orders cover distinct automation mechanisms. Wallet Manager, Asset Bridge, Risk Manager, Trade History and Strategy Presets cover account controls and review.

A role is not a permission

Attaching or switching a role never activates a task, changes wallets or increases a budget. General conversations remain informational. Private tools need Telegram sign-in, and every action needs your confirmation.

Elisia Guide

Settings, Presets & Referrals

Use direct account forms for repeatable configuration. Review saved values before using them in a task or trade.

Trading preferences

Settings cover trading enablement, buy/sell/approval priority fees, buy/sell slippage, quick-buy amounts, sell percentages, anti-snipe behavior and trade confirmation. Turning on live trading is saved on its own and is also confirmed in Telegram. Automatic approval, position-display options and default automatic orders are changed in Telegram.

Risk and automation preferences

Risk controls include supported ceilings for buy amount, gas, priority fee, slippage, price impact, daily loss, daily trades, open positions and signal age. These are the bot’s own limits and apply wherever the bot trades. Turning off a risk filter is also confirmed in Telegram; tax limits are edited in Telegram. Liquidity, tax and creator-share checks depend on available data. AFK, copy, order and quick-buy settings must be reviewed with their own activation state; changing a default is not proof that every existing task was updated.

Strategy presets

The bot maps three slots, P1–P3, for sniping, buy orders, sell orders and automatic sells. On the website you can read a slot, save buy-order, sell-order and automatic-sell presets, or delete a slot; a sniping preset is saved in Telegram. A preset stores parameters; it is not a backtest, a historical result or an active order. Inspect the filled form before saving a task from a preset.

Network, routes and language

Network, RPC node and send host come from the bot configuration and are shown read-only. Manual route selection, route-specific consent and the bot language (English or Russian) are changed in Telegram. The website documentation is English, while the agent can respond in your language.

Referrals

Inspect referral status and your referral link on the website. A payout request is submitted in Telegram. Use the actual account result for eligibility, amounts and status; this documentation does not invent a commission rate or payout schedule.

The browser workspace needs no desktop installation. Local terminal files do not synchronize wallet secrets or replace the bot’s account storage.

Elisia Guide

Identity, Keys & Safety

The account, operation and confirmation must agree before a private action is allowed. Source data and model text cannot grant permission.

Identity and ownership

Sign-in binds a private Telegram approval to the originating browser. The server resolves the bot account and every request carries only that account’s reference, so you see and act on your own wallets and tasks. Pasting a user ID, address or account name into chat cannot select another user’s records.

Custody

Bot wallets are created or imported in @elisisnipebot and their keys are held by the bot service, not by your browser or this website. The website never receives, stores or displays private keys or seed phrases. Export a key or seed only in Telegram and keep your own backup.

Sensitive screens

Wallet import and private-key/seed export are Telegram-only and are refused by the website for every account. Withdrawals, bridge requests and transfers use dedicated account screens and, as listed under Confirmations, a second approval in Telegram. Confirmations are short-lived and tied to the account, operation and exact arguments. Changing an amount or recipient requires a new confirmation. Wallet secrets and Telegram passwords are excluded from agent context.

Risk checks have limits

• A simulation can fail or become outdated before submission.
• Missing liquidity, tax or ownership data stays missing; it does not imply safety.
• A copied wallet or signal source can change behavior without warning.
• Slippage and fee limits constrain requests but cannot promise a profitable fill.
• An address lock and confirmation flow reduce accidental actions; they do not reverse an on-chain transfer.

Read the risk disclosure before trading.

Sessions and records

Signing out ends the website session; it does not erase bot wallets, trade history or running tasks, and it keeps the approval you gave in the bot. Disconnect from bot in the account menu revokes that approval; revoking it in Telegram ends the website session. A disconnected browser does not stop background bot automation. Pause or delete the relevant task, then inspect its returned state.

The bot runs independently

The Telegram bot runs independently of the website. Tasks you enabled keep running when you sign out or close the browser, and the website adds no separate spending policy on top of the bot’s own limits. If the bot connection is unavailable, the site says so and nothing is sent.

Elisia Guide

Confirmations

Every action you start on the website is confirmed by you on the site. The most sensitive ones are confirmed a second time in Telegram. The website has no automatic mode.

On the site

1. Prepare the action in its account screen: wallet, token, amount and settings.
2. Review the summary. A trade is quoted and prepared first, and the prepared trade is valid only for a short time.
3. Confirm. The confirmation is tied to your account, the operation and its exact arguments. Changing an amount, token, wallet or recipient needs a new review and a new confirmation.
4. Read the recorded result and keep the operation ID.

Also confirmed in Telegram

These actions return a “Confirm in Telegram” card with a countdown. Approve or decline in @elisisnipebot. If the request is declined or expires, nothing is sent.

No automatic website mode

Automatic execution from the website is not available and cannot be enabled, and the website stores no spending policy of its own. Limits are the bot’s own settings: trade limits, risk limits and “confirm trades”. You read and edit them in Settings, and they apply wherever the bot trades.

Background tasks

AFK, copy and order tasks that you enable run in the bot after the browser tab closes, within the bot’s limits. Creating, changing, enabling or deleting a task from the website is confirmed by you. The fills of a running task are not confirmed one by one; pause or delete the task to stop it.

The chat assistant is read-only

The assistant can explain and read. It cannot submit, confirm or approve an action, and a sentence in a reply is never a confirmation. Reading positions or asking for a quote does not authorize a trade.

Uncertain results

If the answer to a submitted action is lost, the site reports an unknown outcome and lets you check the operation status. Check before retrying: repeating the same confirmed trade does not create a second one, and a declined or expired Telegram confirmation sends nothing.

Sign out, disconnect, unavailable

Signing out ends the website session and keeps the approval you gave in the bot. Disconnect from bot in the account menu revokes it. If the bot connection is unavailable, the site says so and nothing is sent. None of this reverses a submitted transaction or stops a task that is already running in the bot.