RayBot: an alert is a filtered interpretation of chain activity

The short answer

RayBot is a multi-chain monitoring platform for wallets, token activity, grouped wallet signals, accumulation patterns, related-wallet flows, alerts, and developer integrations. Its public site currently describes 18 supported chains and delivery through Telegram, Discord, web, API, and webhooks. Some features remain chain-specific, so verify the live network and parser before relying on a signal.

RayBot parses transactions into event labels

Raw transactions do not arrive labeled “buy,” “insider,” “first entry,” or “accumulation.” RayBot watches supported chains, parses program interactions, prices assets, attaches wallet labels, and routes selected events. It documents filters for swaps, transfers, liquidity actions, token creation, migrations, DCA, perps, NFTs, source platforms, values, token age, wallet age, and other attributes.

Each parser and filter is a possible blind spot. A new program can appear as unknown, a transfer can look like a trade, a price can come from thin liquidity, and “first buy” depends on indexed history. Open the transaction before treating the alert description as the event itself.

Multi Wallet and Accumulation measure patterns in your selected set

Multi Wallet can alert when several tracked wallets buy the same token within a chosen window, with filters for wallet count, buy size, total size, market cap, token age, and tags. Accumulation measures repeated buys, total value, time, and the percentage still held. These features answer whether a configured subset met a rule. They do not prove independent traders or coordinated intent.

Several addresses can belong to one controller, copy the same public caller, or be funded from a shared service. Conversely, linked actors can avoid the tracked set. Keep the wallet list and labels as part of the signal record, inspect funding and transfers, and evaluate the group as an economic entity rather than counting addresses.

Funding links support hypotheses, not identity claims

Related Wallets maps Solana inflows and outflows. Auto Add can begin tracking a new, previously empty wallet after it receives SOL from a watched address within configured bounds. This is useful for finding possible operational branches and following fund flows.

A transfer proves a transfer. It does not prove beneficial ownership: exchanges, payment services, OTC counterparties, market makers, payroll, and friends also send funds. Record the amount, timing, intervening service, later behavior, and alternative explanations before applying a controller label.

Detection time and message time are different clocks

RayBot's documentation acknowledges Telegram rate limits, bot load, per-minute and daily plan limits, auto-paused high-volume wallets, and alerts that may be delayed or dropped. Backup and dedicated bots can reduce some delivery pressure, but group-wide limits and provider outages remain possible.

Record block time, RayBot detection time, message time, and the time you opened the trade. A fast-looking notification can still arrive after price and liquidity have moved. Never infer entry price, remaining position, or current conviction from the alert alone; refresh the wallet and pool onchain.

The built-in payment wallet is a hot wallet

Tracking public addresses does not require their private keys. Separately, RayBot says it creates an exportable built-in wallet for subscriptions and referral payouts, and recommends treating it as a hot wallet. The same guide also says RayBot never has access to funds without fully documenting the wallet-generation and key-storage architecture.

Keep only subscription money or rewards there, export recovery material through the official bot, store it offline, and move excess SOL to a separate wallet. Secure Telegram sessions and use only bot identities listed in official docs. Do not confuse a watched address with the RayBot payment wallet or any Bloom execution wallet.

Pricing buys capacity, not signal truth

RayBot offers a free tier and paid plans that raise wallet, token, notification, group, Discord, dedicated-bot, and Multi Wallet limits. Prices and limits differ between the current site and older help pages, so use the live pricing page before paying. A higher tier can reduce queues or unlock routing options; it cannot validate labels or make a delayed alert tradable.

A safer evaluation workflow

1. Start from official RayBot links. Verify the exact bot, web app, support bot, group, and subscription destination.
2. Add a wallet you control. Create known swaps, transfers, and failures, then compare every alert with explorer evidence.
3. Build filters in layers. Begin with a broad feed, then document what each global, wallet, source, and advanced filter removes.
4. Measure delivery. Track block, detection, and message times during normal and high-volume periods.
5. Rebuild grouped signals. Check every counted wallet, funding path, prior holding, actual buy, and controller hypothesis.
6. Separate monitoring from execution. Leave external buttons and Bloom Auto Buy off until a capped end-to-end test is justified.

What belongs in the journal

Record chain, tracked addresses and tags, parser label, enabled and disabled filters, signal rule, counted wallets, funding evidence, token and pool, block time, delivery time, plan or bot load, explorer transaction, external action button, Bloom rule if any, and the conclusion you drew. Preserve the original alert before settings change.

Primary sources