Boole on Telegram

/trade — open the Trading Terminal#

Boole replies with a launcher — "⚡ Trading Terminal — Tap to open. This button remains usable after your trading computer sleeps." — and one button:

Tap it and the full Trade Terminal opens inside Telegram, signed in as you. In a group, use /b terminal instead.

/withdraw — fast withdrawalInstant · no AI#

The order matters — asset, then amount, then address. The full sequence:

1. Whitelist the destination once: /whitelist ADDRESS (below). Skipping this answers "That destination is not whitelisted yet. Send /whitelist … once, then repeat this withdrawal command."
2. Send the command. Boole builds a live preview of the exact route and shows it with ✅ Confirm withdrawal / Cancel.
3. Confirm within 5 minutes — the button works exactly once, then expires.
4. Watch the status line: "Withdrawal accepted — submitting securely. Do not repeat it; confirmation will appear here." It updates in place with the final result.

/whitelist — allow a destinationInstant · no AI#

• Exactly one address, no extra words. A label, a second address, or any prose makes the whole line invalid and Boole re-shows the help card.
• It activates immediately and can then be used by /withdraw and the /withdraw_to flows.
• Only you can do this, from your own private chat — "the AI cannot add or change addresses." Only whitelist an address you control or fully trust.

/credits — balance and top upInstant · no AI#

The buying sequence is always: /credits → ➕ Get more → 💰 From your Boole wallet → pick or type an amount → Confirm $X.XX. On the amount screen you can type freely — 2, $1.50, 1 buck. Purchases run $1 to $100 and settle from one chain. Full details in Adding credit.

/referral — your invite linkInstant · no AI#

Answers with your personal invite link, Copy link and Share buttons, and your earnings once you have invitees — 20% of their trading fees to you, 10% back to them. Everything you share from Boole already carries the link. Details in Invites & referrals.

Sending a contract addressInstant · no AI#

No command needed — pasting a contract address opens the full live token panel for that exact contract: price, liquidity, your position, trade controls, auto-refresh, and quick-buy settings (see Search & token panels). For a name or ticker instead, use $TICKER or /search pepe — instant matches across Hyperliquid and every major chain.

Charting a contract#

fcb and fce are one-tap Bitcoin and Ethereum charts. For anything richer — timeframes, indicators, comparisons — just ask the agent in plain English:chart 0x6982…1933 against BTC over 7 days with RSI. It composes the image using any of the fifteen chart types, with markers and levels.

Instant by design#

Everything routine answers instantly. Menus, price alerts, wallet cards, token lookups, live market charts — they respond in under a second, because they never wait on an AI model. These surfaces are marked Instant · no AI throughout this book, and they never spend a cent of your AI credit. Tap around as much as you like.

Everything intelligent is yours alone. Every Boole account comes with its own dedicated, always-on trading computer, created the moment you sign up. Your wallets, sessions, strategies and creations live there — not on some pooled backend. When you ask for actual thinking — research, analysis, a trade worked out in plain English — your personal agent takes over and streams its reply straight into the chat. These paths are marked Agent turn.

The result is a desk you can lean on all day: browsing costs nothing, and intelligence is spent only when you actually ask for it.

What people see before pressing Start#

The bot profile shown to anyone who opens the bot before starting it:

Short description: "Research, chart, build, share and trade with an AI trading desk inside Telegram." Both are refreshed on every deploy.

Trading-grade reliability#

A chat that can move money has to behave like trading infrastructure, not like a chatbot. Boole is built to a few promises you can feel:

• Nothing ever runs twice. A request is executed once, period. And when Boole genuinely can't confirm an outcome, it tells you instead of guessing: "I could not confirm whether that request completed. Do not repeat it yet—check your status or positions first."
• Always in order. Your messages are handled in the order you sent them — an older request can never jump the queue on a newer one.
• The newest message wins. Change your mind mid-reply and just say so — the new message cleanly takes over, exactly like it does in web chat.
• Never left hanging. If an answer takes more than a few seconds you see "Waking your Boole agent — your request is safely queued." — and the notice tidies itself away once the reply lands.
• Picks up where it left off. If a reply is interrupted, the recovered part is delivered once and clearly labelled — never silently lost, never repeated.

One desk, every screen#

Telegram and the web app are the same desk: same sessions, same transcript, same tools, same trading mode. Start a conversation on your phone in Telegram and it's already there when you open the web app. Paper or live is one switch shared everywhere — your agent, the web app and the Trade Terminal can never trade different books.

/startInstant · no AI#

/start is pre-acknowledged before any database work, so the first reply is instant even while an account is being created. The full sequence for a new user:

1. If signup verification is enabled and you are unverified, the human check comes first (below).
2. The interest picker appears (below).
3. Your dedicated trading computer and wallets begin setting up in the background — you never wait on them.
4. You are auto-connected to the default Boole account, and to your referrer if you arrived through a referral link.
5. After you finish the interest picker, the welcome message, wallet card and one-time key backup arrive.

/start also accepts deep-link payloads:

Human verificationGated off#

When signup CAPTCHA is enabled, an unverified /start gets a welcome plus one quick human check before anything is created:

A one-button keyboard labelled Verify I'm human opens a Cloudflare Turnstile check inside Telegram. On success: "Human verified — Your private Boole account is being prepared now.", and onboarding continues normally. Distinct failure copy exists for an expired link, a locked account after too many attempts (wait an hour), a provider outage (retry shortly, nothing was created) and rate limiting.

Anything an unverified user tries — messages or button taps — is answered with "Complete verification before using Boole." The raw verification proof is never stored durably; a crash asks you to retry rather than replaying it.

The interest pickerInstant · no AI#

Fourteen toggles in two columns, each flipping between unselected and selected on tap: Stocks, Crypto, Geopolitics, Solana trenches, Funding rates, Liquidations, Mean reversion, Breakouts, Prediction markets, Unusual Poly volume, Copy top traders, Trump tweets, Daily market digest, and Position & risk alerts. The bottom row shows Skip for now until something is selected, then Done · N selected.

Selection state is carried inside the buttons themselves (a bitmask in the callback data), so toggling is stateless and survives bot restarts; only Done writes anything. Your choices drive the morning digest (see Morning digest) and are also pushed into your agent's context — so it knows your interests without an AI turn being spent. The picker is re-openable any time from Settings, where saving confirms with "Your Boole interests are updated."

Wallet creation and the backup card#

After Done or Skip, three things arrive in order:

1. The welcome — "Welcome to Boole … Your private Boole account is being prepared … Take the short tour, or use the menu below whenever you are ready." — with the fixed bottom keyboard attached.
2. The wallet card (see Wallet & funds) with your EVM and Solana addresses. The bot polls for up to ~90 seconds if minting is still in flight.
3. The one-time private key backup:

The card is sent with forwarding and screenshot-save blocked, and the claim is consumed atomically before Telegram ever sees a secret — it can only happen once. If you ever paste one of those exact keys back into chat, it is redacted to "[private wallet key removed before storage]" before being stored or forwarded anywhere.

The tourInstant · no AI#

/tour, the Take the 30-second live tour button on the wallet card, or typing "what can you do" all open the same card:

Each button jumps straight into the real feature; Finish tour closes with "You're ready. Use the menu below or tell Boole what you want in plain English."

The full private-chat menu#

Group chats expose exactly two commands: /b and /boole, both described as "Ask your Boole agent" (see Groups). The private menu is re-pushed to every known chat on boot so new commands autocomplete immediately.

Working aliases and unlisted commands#

Any unrecognized /command falls through to your agent as plain text — which is also how your own custom commands resolve.

Instant commands in detailInstant · no AI#

The instant commands each open a menu or card documented in its own chapter:/search and $TICKER in Search & token panels;/charts, /fc, /fcb, /fce in Charts;/wallet, /deposit, /whitelist, /withdraw, /wallet_activity in Wallet & funds;/alert, /notifications in Price alerts;/snipers in Launch alerts;/connect, /follow, /unfollow, /connections in Connections & sharing;/settings in Settings; and/start, /tour in Getting started.

Session commands#

Plain text always lands in the pinned active session (falling back to the most recent, then a new one). Opening a reminder Mini App re-pins the session that scheduled it, so your next reply lands in the right conversation.

The two kinds#

• Prompt commands run an agent turn with the saved text; anything you type after the command is appended. Agent turn
• Script commands run a JavaScript file from your workspace under the same sandbox as the agent's own shell: 25-second timeout (75 s for trade-executing scripts), 64 KB output cap, at most 4 Telegram messages then "…output truncated (N more messages suppressed)." No output reads "/x ran with no output."; a failure reads "/x failed: …".Instant · no AI

Scripts can emit one structured message with its own inline keyboard. Only known-safe button types are relayed — recognized callback actions, https links, https web-apps and copy buttons; anything else is rejected before it reaches Telegram.

Lifecycle and limits#

• Adding pins it: "Pinned /x to your command bar — tap it below anytime." Removal: "Removed /x from your command bar."
• Telegram caps a bot at 100 commands total; Boole reserves the built-ins and leaves the rest — around 55 slots — for your own. Names must be lowercase letters, digits and underscores.
• Built-ins and platform commands cannot be shadowed: "/x is a built-in command and can't be overridden."
• Custom commands also appear as keyboard buttons beneath the fixed rows — see The fixed keyboard.

Agent tools behind this#

Two tools power the surface. telegram_menu edits the customer section of the persistent keyboard (set, add, remove, clear — the fixed Boole rows are immutable). Tapping a persistent button literally sends its text as a message, so the guidance is to name buttons like good prompts: "Refresh war-risk chart", "My positions". If a keyboard edit produced no reply text, the turn ends with "Custom buttons updated."

telegram_buttons attaches per-message inline buttons of three kinds: prompt (re-runs the agent with that text), trade (executes a real venue order on tap), and token (opens the contract-pinned token panel). Up to 3 per row.

Layout#

The keyboard resizes to content and can be collapsed — it deliberately avoids Telegram's "persistent" hint, which would make it uncollapsible. Hide it entirely with /keyboard off.

What each button does#

Two more labels appear on box-issued keyboards: 🛒 Buy and 💵 Sell (currently placeholdered — see the note in the command reference).

The customer section#

• Up to 24 custom buttons, 3 per row, appended beneath the fixed rows; labels are sanitized and capped at 32 characters.
• Custom /commands also appear as buttons; platform commands never become customer UI.
• Retired platform labels from older accounts (old Build/Research/Alerts buttons) are filtered out and never resurrect.
• Individual buttons and commands can be hidden per user.

SearchInstant · no AI#

Four ways in, all answered without AI:

• /search PEPE or bare search PEPE — ticker or name lookup.
• $PEPE — the leading dollar sign marks it as a search so ordinary one-word chat is never hijacked.
• A pasted EVM contract (0x + 40 hex) or Solana mint — goes straight to the full token panel.
• Bare /search — replies with usage: "Send /search TOKEN, or paste an EVM/Solana contract address."

Ticker search runs Hyperliquid and DexScreener in parallel (1.8 s budget, 30 s cache) and returns a fast match card — up to 4 on-chain tokens and 3 perps across ethereum, base, arbitrum, polygon, bsc, optimism, avalanche, solana and robinhood:

Buttons read Trade SYM (Solana and Robinhood chains) or Inspect SYM (other chains) for on-chain tokens, and SYM · Hyperliquid for perps. If nothing matches, the query falls back to your agent's full search.

Token panels#

A token panel is a live card for one exact contract: price, liquidity, your position, and trade controls. Its buttons all work instantly, without waking the AI:

Quick-buy amounts and slippage#

Each panel exposes two quick-buy amounts and buy/sell slippage. Tapping one sends a reply-to form: "Set quick-buy amount 1 in ETH — enter one number greater than 0 and up to 1,000. Reply to this message with only the number." Slippage accepts 0.01–10% (0.01–3% on Robinhood).

The form is bound to the exact prompt message, expires after 10 minutes, works once, and is invalidated by a restart — a stale or forged reply can never change your settings. Invalid input re-prompts with "That value was invalid."

Live-order safety#

When you tap a live execution button on a token card, three things happen at once:

1. The tap is acknowledged immediately — "Request accepted — preparing your live order…" — even if your trading computer is still waking up.
2. Every button is stripped off that card so the one-shot intent cannot be double-fired.
3. A durable status line is posted in chat: "Order accepted by Boole — preparing the secure on-chain submission. A confirmed result will follow here."

Fast candle chartsInstant · no AI#

fc BTC (slash optional), fcb for Bitcoin, fce for Ethereum. Bare fc prints the usage card: "Fast candle charts — no AI … For a shitcoin, send its ticker or exact contract after fc."

• Resolution order: an exact Hyperliquid perp ticker always wins (so fc BTC can never resolve to a copycat token), then DexScreener across all indexed chains ranked by relevance, liquidity and volume.
• Output: the last 72 hourly candles, titled "SYMBOL — $price · ±x.xx%", with a volume pane when the source provides volume. Results cache for 30 seconds.
• Failures are explicit: "No exact perp or indexed on-chain token matched X. Try the full contract address."

Live heatmap presetsInstant · no AI#

The 📈 Chart button and /charts open the preset menu:

Presets cache for 90 seconds and are also persisted into your transcript as "Generated directly from live market data." with the image attached, so the agent has context if you ask a follow-up. Old preset buttons from years-old messages still work — legacy ids are mapped forward. An expired unknown one answers "This chart option expired. Tap 📈 Chart again."

AI-built charts — the fifteen typesAgent turn#

Ask for any chart in plain English and the agent composes it server-side, then sends it as an image. All fifteen chart types are available from Telegram:

Charts can carry buy/sell markers and dashed SL/TP level lines. Every chart sent to Telegram arrives with a 👍 / Share / 👎 row — Share renders a clean PNG behind a public 24-hour link plus a Telegram share sheet.

The agent is explicitly forbidden from approximating charts with ASCII or Unicode blocks in chat — if it can be drawn, it is drawn properly and sent as an image.

Opening it#

• ⚡ Trade on the fixed keyboard → an inline Open Trading Terminal button carrying fresh Telegram auth.
• The Trade menu button beside the message input.
• In groups, /b terminal → Open My Terminal, which opens inside Telegram signed into your own account (or hands off to your private chat if the direct Mini App is not configured).

Sessions last 24 hours and renew on a heartbeat while the app is open; a foreground terminal also keeps your trading computer awake. If it's asleep you see "Execution agent is waking back up… Your terminal and open ticket will stay right where you left them." An expired session reads "This Telegram session expired. Close and reopen Trade from Boole."

Markets home#

• Header: total equity, a 24h delta pill, the PAPER/LIVE mode chip (tap to switch venue) and a Deposit button.
• Market search with an empty state and clear control.
• Weekly top traders band — rank, avatar, handle, top pick and 7-day PnL — replaced by your own positions band once you hold any.
• Tabs: Stocks · Perps · Portfolio · Watchlist.
• Long-press any market for a context sheet: Add/Remove watchlist, Open market, Long, Short.

The Portfolio tab adds the accounting block: all-time P&L, traded volume, a stepped realized-PnL curve ("it steps when a trade closes and holds flat in between"), and your strategies with per-strategy PnL and volume — scoped to the active venue.

Instrument screen#

• Always-visible exposure strip: side and leverage, size, notional, liquidation price, unrealized PnL and ROE — or "No position · resting orders" when only orders exist.
• Price block with 24h change and open interest; candle chart with 1H · 4H · 1D · 1W · 1M · 3M ranges.
• Content tabs: Position (details grid, TP/SL block, actions: Share · Flip · Decrease · Close half · Close, and AI analysis), Orders (each with a Cancel button → "Order cancelled"), Analysis, and About (volume, OI, funding, max leverage, venue notes).
• Bottom bar: Short and Long.

The Analysis tab is deterministic microstructure, refreshed each open: regime (trending / mean-reverting / choppy), 1h RSI, stretch from VWAP in sigma, range position, return autocorrelation, streak and acceleration, order flow (buyers lifting / sellers hitting / balanced), flow toxicity, venue-relative percentiles for momentum, volatility and flow, and up to six "moves like" correlated peers you can jump to.

Order ticket#

• Order type: Market ("Execute now at the best price") or Limit ("Rest at your price until it fills").
• Size entry with keypad and quick chips ($15 / $50 / $100 / $300), leverage wheel up to the venue max with a "high liquidation risk" warning, live liquidation-price and entry estimates.
• Take profit and Stop loss cells on market orders; presets are % return on margin.
• Slide-to-submit — the control is a deliberate slider, not a button. Inline validation covers minimums (an $11 floor), maximums, balance and TP/SL sanity.
• Backing out is guarded: "Tap back again to discard the order".

The result sheet reports honestly: "Long opened", "Limit order placed", "Order submitted" or "Order rejected" — a venue acknowledgment is never reported as a fill. Attached TP/SL legs are placed only after a confirmed entry (stop first); if a leg fails you get a loud unprotected-position warning rather than silence.

Managing positions#

AI position reviewAgent turn#

The AI analysis button runs a read-only review of your book: "Analysing your book — Read-only · nothing is traded", with visible stages (reading your book, pulling 4 timeframes, scoring signals, checking guardrails, writing the call). Limited to 3 runs per minute because each one reads four timeframes plus signals for every position.

Top traders and copy portfolio#

Tapping a trader opens their detail screen: all-time PnL, account value, month/week/today grid, an equity chart (All / 1M / 1W / 1D) and their open positions. The footer is Clone portfolio:

You pick the amount ($50 / $100 / $500 chips), preview every leg live, and confirm. Legs are split by weight with a minimum of $11 each.

Venues and modes#

The venue sheet is two-step — a row selects, the footer commits ("Use real funds"). Live venues require enablement on your account; otherwise the terminal is paper-only and a live attempt answers "Live trading is not enabled on this box." The paper/live choice is shared with /mode and the web app.

Limits you can hit#

Orders 12/min · venue switches 10/min · portfolio recomputes 6/min ("each run replays every recorded fill") · AI analysis 3/min · state reads 30/min. Solana RPC rate limits are translated honestly: "Solana RPC rate-limited (429) … Nothing was placed."

Sharing wins#

Every verified full close with positive PnL is automatically sent to your bot chat as a rendered share card — "ASSET closed +12.4% — $84. Tap to share your win." — with a Share button. Losses stay private unless you share them yourself from the app; a manual share toasts "Card sent to BooleBot — you can share it."

The three Mini App surfaces#

• Market Intel — the Discover market screen, opened from the fixed keyboard.
• Trade Terminal — the full trading app (previous chapter).
• Agent-built interfaces — anything you ask the agent to build (dashboards, trackers, tools) is delivered as a card with an Open {title} button that opens inside Telegram.

Reminder interfaces arrive as ⏰ {title} — "Reminder — tap to open inside Telegram" — and opening one re-pins the session that scheduled it.

How auth works#

Opening a Mini App is a three-hop handshake: an unauthenticated shell that reveals nothing, a proof step that verifies Telegram's signed initData (HMAC against the bot token, 24-hour max age, and the user id must be the owner), and a token-gated content fetch. Inside the app, a capability shim attaches the token only to same-origin interface calls — never to an external URL. Buttons inside an interface can only invoke actions the agent pre-registered by name; the iframe can never supply trade parameters itself.

Opened outside Telegram, the shell says "Open this from inside Telegram."; a failed proof says "Could not open — reopen it from your Boole chat."

Sharing is disabledDisabled#

Mini Apps are owner-only. They are never publishable, sharable, broadcastable or forwardable, and old share links are dead. Attempts answer "Mini App sharing is disabled for security. Share a chart or image instead." A response containing only a private Mini App cannot be shared at all. In groups, web-app buttons are stripped from replies entirely, because a Mini App URL can carry the owner's credential.

The live thinking card#

While the agent works you see one draft message, edited about every 1.6 seconds, rendered as a quote block headed by the current activity — the tool being used, or "Thinking", starting with "Working on it…". When the turn completes, the draft is deleted and the full reply is sent cleanly.

Telegram receives assistant text, charts and questions only — never internal reasoning, tool arguments or tool results. That redaction is by omission: those streams are simply not wired to Telegram.

Formatting, tables and long replies#

• Markdown is converted to native Telegram formatting: headings and bold, italics, strikethrough, links, bullets, and real code blocks.
• Tables adapt to phones. Narrow tables render as aligned monospace; anything wider than 2 columns or 38 characters becomes stacked label/value cards instead of a horizontal scroll.
• Long replies are chunked at ~3,800 characters on line boundaries, with code blocks carried across the cut so both halves stay well-formed. Buttons attach only to the final chunk.
• If Telegram rejects the formatting, the reply is re-sent as plain text — a reply is never lost to a conversion bug.
• The model is instructed to put a blank line between distinct statements, and to never hand-write web URLs or approximate charts as text.

Questions and feedback buttons#

When the agent asks you something, the options become tap buttons under the question, with a suffix telling you how to answer: "(or just reply in text)", or in groups "(reply with /b followed by your answer)". Expired buttons answer "That button expired — reply in text instead."

Replies carry a 👍 / Share / 👎 row. Tapping records the rating and edits the row to show a check — "Thanks — marked helpful." Artifacts (strategies, snapshots, interfaces) also get a Broadcast to followers row.

Sending photosAgent turn#

Send any photo and it enters the same vision path as web chat; the caption becomes the prompt, defaulting to "Describe and analyze this image. Call out anything important or actionable." A failed download asks you to send it again. Non-photo file attachments are not supported yet: "Photos are supported, or use the web chat for other files."

Why the agent remembers menu taps#

Every instant message Boole sends — menus, cards, alerts — is mirrored into your agent's hidden session history as plain text, without waking it. Button taps are mirrored by their visible label. So when you tap around menus and then ask a question, the model has seen exactly what you saw. Deliberate exclusions: private keys (never), the human-check flow, timer-driven panel refreshes, and shared images (only the caption is mirrored, never the bytes).

Notifications get the same treatment: alerts delivered since your last message are injected with their age ("[2m ago] …") so "close it" works — with the standing instruction to ask before acting if a money-moving reference is unclear.

Error surfaces#

The credit screenInstant · no AI#

/credits opens it directly. It's also reachable from Settings (AI credit & usage), the Home card, the 💳 Credits keyboard button where shown, and it appears automatically the moment a turn is refused on the daily cap.

• Refresh re-reads usage in place. If usage cannot be read safely, no estimate is shown — "Your current usage could not be read safely, so no estimate is shown. … Your trading funds are unaffected."
• How credit works: deterministic menu taps don't use the allowance; trading funds are separate; the included allowance resets daily at 00:00 UTC.

Adding creditInstant · no AI#

➕ Get more opens the top-up screen, which is explicit about what you're buying: "Paid credit is a balance, not a daily limit. It carries over, and is used only after the day's included allowance." Two payment methods:

Paying from your wallet, step by step:

1. Boole reads your live balances. If more than one chain holds funds, a Pay with picker chooses which balance pays — a charge settles on one chain, so balances never combine.
2. Pick an amount — presets from $1 to $25 filtered to what that balance affords — or just type one: 2, $1.50, even 1 buck. Purchases run $1.00 to $100.00.
3. Confirm $X.XX — the screen states the exact cost first. Gas is covered; if a swap is needed, the extra is capped and stated. "Confirming moves the funds once. This can take up to a minute to settle."
4. Settlement is reported honestly: "$X.XX of credit added — purchased balance is now $Y.YY" on success, distinct in-between states while a transfer settles, and on failure "Nothing is charged unless the transfer settles, so the wallet is untouched." A double-tap answers "This payment is already being processed, so it has not been sent twice."

Free text works end to end too — "top up $5 of credit" jumps straight to the confirmation, and /start topup deep-links here. Card checkout ships behind a flag and shows "Card payment is not available yet. Paying from your Boole wallet works now." until it's enabled.

What gating looks like#

• Image analysis before an active deposit: "Image analysis is available after an active deposit. Use /deposit, then ask Boole to check your balance before sending the image again."
• Allowance exhausted: "Today's Boole Lite research allowance has been used … available again at {reset}."
• Managed alerts cap at 3 on Lite: "You're at your Boole Lite alert limit. Upgrade to Boole Pro for unlimited alerts."

Creating an alertInstant · no AI#

/alert BTC above 70000 — or just type alert ETH below 2500 with no slash. The grammar is <asset> <above|below|over|under|>|>=|<|<=|hits|reaches> <price>, anchored to the whole message so prose like "what does BTC above 70k mean" never triggers it. Bare /alert shows the help card.

Unparseable input answers with the format hint; the Lite cap (3 managed alerts) answers with the Pro upgrade line.

Managing alertsInstant · no AI#

/notifications lists everything with an N-of-max counter; each row is a button opening the detail card ("BTC — above $70,000 · active"):

• Pause / Resume toggles delivery without losing the alert.
• −5% … +5% nudge the trigger price; Flip direction swaps above/below.
• Time reminders get snooze buttons instead: +10m / +1h / +1d.
• An Undo button appears when an earlier version is saved.
• /noty2 jumps straight to alert #2.

Agent remindersAgent turn#

Ask the agent to remind you of anything ("remind me to check funding at 8pm") and it uses its reminder tool — important on Lite, where your trading computer sleeps between turns. When a reminder fires, its turn re-runs in the exact session that created it, and reminder interfaces arrive as ⏰ Mini App cards.

The menuInstant · no AI#

/snipers (aliases /snipe, /sniper) opens Token launch alerts — "Get a Telegram alert when our AI detects a monitored launch going live." Each watched launch is a toggle row; the detail screen explains that the watcher validates the real factory event on-chain rather than trusting a ticker or lookalike contract, and that "An alert is informational—not an automatic buy."

The alert itself#

Up to two buttons — Open explorer and Official source — only ever validated https links. Delivery is paced platform-wide, and the alert text is mirrored into your agent's context so a follow-up question has something to stand on.

What arrives#

1. One or more photo albums of 900×520 live panels, one per selected interest, captioned "Your 24h market map — swipe through N separate live charts."
2. A summary — "Morning map · date · N charts selected for {timezone}" — with two buttons: 📈 More charts and 🎯 Change interests.
3. Yesterday's digest is deleted only after today's succeeded, so you never wake to a gap.

A panel that fails renders as a clean placeholder card — "Live panel unavailable for this refresh … Boole will try this section again in the next scheduled refresh." — never a broken album, and the summary notes how many sections will retry tomorrow.

The fourteen panels#

Change tomorrow's mix any time from Settings → What do you care about?

The full set#

Connecting and followingInstant · no AI#

Every new signup is auto-connected to the default Boole account, and to their referrer when they arrived through a referral link.

The connections & privacy screenInstant · no AI#

Sections: requests on/off, following, followers, connections, incoming requests and blocked — each row with its action buttons (Accept, Decline, Block, Remove, Unblock), plus a syntax crib at the bottom covering send @username your idea, broadcast your idea and the rest. A toggle blocks all new requests. Accepting notifies the other side: "@you accepted your connection request. You can now send ideas with send @username your idea."

Sending and broadcasting ideas#

Free text does the sending: send @user your idea delivers a full idea to one connection's bot; broadcast your idea goes one-way to every follower. Attach a photo with the same text as its caption and it travels with the idea. From any chart or response the agent produced, the share flow offers:

• Share with a Boole connection expands into one button per connection (up to 30) and confirms "Shared the complete response with @x."
• Broadcast to followers confirms with the delivered count.
• Send on Telegram opens the native share sheet for someone not on Boole yet; image cards can also just be forwarded natively.
• Share menus expire after 30 minutes and only work for the person who opened them.

Receiving an idea — the quarantine#

A shared idea arrives as a card (images first, then the body):

Analyse this opportunity opens the idea in a fresh, isolated session — "The shared card itself stays out of your existing sessions." The sender's raw text and image travel only in quarantined metadata: another user's words are treated as untrusted context, never as instructions to your agent, and the analysis runs with a research-only tool whitelist. An idea can be claimed once; if extraction fails safely, you see "Nothing from it was added to your agent chat."

Your invite linkInstant · no AI#

/referral (aliases /ref, /invite, /referrals) answers instantly with your personal link:

That last line is literal: every chart or idea you send onward from Boole ends with "Join with https://t.me/…", so sharing your work is sharing your link. Copies your recipients receive carry branding only — your link is never re-attributed to them. The invite block also appears on your wallet card with a 🎁 Copy invite link button.

What you earn#

• You: 20% of the Boole trading fees paid by everyone who joined with your link.
• Them: 10% of their own fees back.
• Rates are read live from the referral program, so the card always shows current terms.

Once you have invitees, the same card grows a ledger — Invited (with how many have activated), Fees they paid, and Your earnings, including any amount still pending activation.

What your friend sees#

1. Opening your link shows the entry card — "Someone invited you to Boole — an AI trading desk that turns market ideas into live research, charts and useful tools."
2. On Start, the attribution is confirmed out loud: "🎁 Invite applied." — followed by "Boole Lite is ready. Use the menu below or ask me anything."
3. They're automatically connected to you on Boole, so ideas can flow both ways from day one.

Links are signed — a forged or edited code quietly resolves to no referrer rather than a wrong one. And if a friend's invite gets lost between apps, pasting the link text into the bot chat applies it just the same.

Using /bGroups#

Only /b your request and /boole your request reach an agent — all other group chatter is ignored entirely. Bare /b prints the group help:

• /b terminal (or "trade") opens your own Trading Terminal, signed into your account.
• /b stop and /b new map to /stop and /new.
• Replying to someone else's message with /b … attaches that message as explicitly untrusted context — the agent treats it as material to analyze, never as authorization. Photos on either message travel too.
• When the bot is added to a group, it posts the help card automatically.

Privacy in groups#

• Each member gets a private per-group session titled "Group · {name}"; replies are threaded to the invoking message.
• Group turns carry standing instructions: reply for a public audience; never reveal wallets, balances, keys, history or alerts. Direct attempts get "Keeping that private. Open your direct chat with Boole for account, wallet, session, settings, or command details."
• Question buttons and Mini App buttons are suppressed or stripped in groups; only explicitly-authored https links survive, with self-origin URLs scrubbed of query strings.
• Withdrawal whitelists are never applied to group turns.

Members without an account#

A member who hasn't met Boole gets a private-onboarding card — "Hi @x — we haven't met yet. Open the bot, tap Start, then come back and use /b again." — with a Start Boole button. If signup verification is on, unverified members are routed to the private human check first via a Verify with Boole button.

/walletInstant · no AI#

Copy buttons work without a round trip. If minting hasn't finished: "Your wallet is still being prepared. Try /wallet again in a few seconds."The card also carries your invite link with a 🎁 Copy invite link button. Recovery-anchor buttons (email / EVM / SOL) and the secure key-export link exist on this card but are currently gated off. Gated off

/depositInstant · no AI#

Lists deposit addresses for EVM (Ethereum / Base / Arbitrum), Solana, and Polymarket (USDC on Polygon), ending "Send each asset only on its matching network." The Trade Terminal's deposit screen shows the same addresses with QR codes and Copy/Share.

Withdrawal whitelistInstant · no AI#

/whitelist ADDRESS allows an EVM or Solana destination for withdrawals. The parser is deliberately strict — exactly one address, no labels or prose; EVM addresses are normalized and the zero address rejected; Solana addresses must decode cleanly. Success:

The help card closes with the warning: "Only whitelist an address you control or fully trust." Whitelisting is personal by design — "the AI cannot add or change addresses" — and the agent only ever sees destinations through a signed, 60-second-fresh snapshot: raw chat input can never inject one, and group turns never receive it.

Withdrawals#

Fast withdrawals Instant · no AI — /withdraw sol 0.1 ADDRESS sends SOL from your Solana wallet; /withdraw eth 0.001 ADDRESS sends ETH on Robinhood Chain. No AI is involved at any step. The destination must be whitelisted first — if it isn't: "That destination is not whitelisted yet. Send /whitelist … once, then repeat this withdrawal command."

Boole then prepares a live preview of the exact route and shows it with two buttons:

• Confirmations are one-shot and expire after 5 minutes; a stale or re-used button answers "This withdrawal confirmation expired. Run /withdraw again."
• On confirm: "Withdrawal accepted — submitting securely. Do not repeat it; confirmation will appear here." — and that status line is edited in place with the final result.
• If the outcome can't be verified, Boole says so honestly and points you at /wallet_activity rather than guessing.

The Withdraw To… menu Instant · no AI — /withdraw_to opens the destination chooser: My Boole Wallet, Whitelisted Address, Another Trading App, Withdrawal Activity. Browsing it is instant; picking a source hands to your agent, which reads the live balance, asks for the exact amount, shows a full preview, and requires an explicit confirmation before anything moves.

Moving & tracking funds#

/move_funds offers one-tap routes — Hyperliquid to Phoenix (and back), Wallet to Hyperliquid, Wallet to Robinhood, or a custom route — with the standing promise: "Nothing moves from this menu: Boole checks balances and fees, asks for the exact amount, and shows a confirmation preview first."Plain English works too ("move $200 to Hyperliquid").

/wallet_management is the hub tying it together — Add Funds, Withdraw To…, Move Between Apps, activity and balances — with the same rule stated up front: "Every withdrawal is previewed first and still requires an explicit confirmation."

/wallet_activity Instant · no AI shows your last six deposits and six withdrawals with live status. Destination addresses and transaction secrets are never shown in the feed, by design.

/settingsInstant · no AI#

Each entry opens the screen documented elsewhere in this book: AI credit & tiers, the interest picker, the withdrawal whitelist, and connections & privacy. Every sub-screen carries a back button to Settings.

Ownership and identity#

• A message becomes agent input only from the owner's own private chat — everything else is silently dropped before it gets anywhere near your account.
• Mini Apps verify Telegram's signed identity on every open; the user id must be the owner's, and proofs expire after 24 hours.
• Chart attribution uses the verified Telegram username from the owner-gated update — never a name supplied by a model or a payload.

Key handling#

• Private keys appear exactly once — in the backup card, spoiler-hidden, forward-blocked, with the claim consumed atomically before Telegram sees a secret. Only fingerprints are retained.
• If a key you were given is ever pasted back into any chat, it is redacted before storage or forwarding — and if the fingerprint registry is unreachable, redaction fails closed on anything key-shaped.
• The agent cannot see the backup message, by construction: it bypasses the context-mirroring path entirely.

Untrusted content boundaries#

• Shared ideas travel in quarantined metadata; the recipient's agent analyzes them in an isolated session with research-only tools. Another user's text is never treated as instructions.
• Group reply-context is injected with an explicit untrusted label — material to analyze, not authorization.
• Shared images enter model context by caption only; the bytes stay out unless you explicitly analyze them.
• Withdrawal destinations come only from a signed snapshot no older than 60 seconds (see whitelist).

Delivery discipline#

• At-most-once execution everywhere; duplicates replay the recorded verdict instead of re-running.
• A restart mid-processing parks the update for review rather than silently replaying it — the deliberate posture for a money-adjacent channel.
• Ambiguous outcomes are stated, not guessed: "I could not confirm whether that request completed. Do not repeat it yet—check your status or positions first."
• Conversation replies deliberately skip the notification deduplicator — saying "yes" twice must send twice.
• One-shot forms (quick-buy amounts, slippage) are message-bound, single-use, 10-minute-expiring, and invalidated by restarts.

Caps in one place#