Coral Wallet Tracking Limits and Chat Destinations

How does the follow limit apply across users and chats?

The personal allowance belongs to a person within a chat, so the published cap does not describe a pooled room-wide wallet list. The /following command lists the wallets you follow in the chat where you run it. This capacity limit concerns active subscriptions, rather than the number of trades a monitored wallet makes. Administrator-managed roster alerts follow a different accounting rule.

Personal messages and shared channel alerts

The alert destination determines who receives a followed wallet’s trade report, while the subscription type determines how the follow uses personal capacity. A direct conversation supports personal delivery without requiring a server. Channel delivery places the report in a shared room and requires an administrator to set up that follow.

Personal delivery

Personal follows send wallet trade alerts to direct messages. Telegram requires the user to open the bot’s direct conversation so it can send those messages. This prerequisite applies to personal delivery, even when the bot already operates in a group the user belongs to.

The console also supports choosing an alert destination.

Administrator-managed delivery

An administrator can establish a channel follow for everyone in the room. For the curated roster or a token-specific top-wallet roster, an administrator’s group subscription uses nobody’s personal follow slots. Any administrator can stop the curated channel roster with /unfollow top. This exception belongs to that shared roster mode; it does not turn every personal subscription into a free channel follow.

View image file

Individual addresses and roster subscriptions

An individual wallet follow tracks the address you choose, while a roster subscription groups selected wallets behind a single follow entry. The /follow top command selects the curated roster. A personal subscription to the curated top-wallet roster occupies one follow slot. The number of wallets inside that roster therefore differs from its cost in personal follow capacity.

A token-specific roster follows a token’s largest holders who also trade it. The command /follow top accepts a ticker or contract address and also counts as one personal follow. Token-specific rosters cover Base, Robinhood Chain, and Solana. Roster membership updates automatically, so a roster subscription serves a changing selection rather than a permanently fixed address list. The removal form /unfollow top targets the corresponding token-specific roster.

The information behind a trade notification

A wallet alert combines the observed trade with a token assessment and the traded wallet’s record, giving context for deciding which subscriptions remain useful. Token readings include the Coral Score and applicable safety checks, covering holder concentration, honeypot concerns, and liquidity-pool status. A honeypot warning concerns restrictions on selling; liquidity-pool checks may report whether liquidity is locked or burned. Available scan data determines which details appear.

The traded wallet’s record can include its tier, community-follow status, and realized profit and loss where available. A token grade describes the token; the wallet record describes the address’s observed trading history. A favorable wallet record does not resolve a contract warning about the token involved in its trade.

When two followed wallets buy the same token within an hour, Coral sends one coordinated alert, which can include a convergence line. A first-call receipt appears when the service flagged the token first. Coordinated buying does not establish that the addresses made independent decisions.

Browser management and wallet selection

The browser console provides a second management surface for adding wallets, pausing alerts, and organizing follows with tags. The /web command in Telegram or Discord supplies access to that console, while the bot continues delivering notifications in chat. A browser control and a chat destination have different jobs: one manages the selection, and the other carries the trade report.

Wallet history helps determine whether an address deserves continued monitoring. Hit rate needs its sample size alongside it, and last-active information gives context for a quiet address. An address with few recorded trades offers less history for interpreting its hit rate.

The console supports pausing notifications; /unfollow ends a wallet follow.

Subscription changes and information visibility

A follow command supplies a wallet address together with chat-platform information the service receives, including the sender, chat, and timestamp. Public blockchain history supplies the activity being monitored. Posting a tracking instruction in a shared room also makes that instruction visible within the room, so the choice of destination affects both where requests appear and who sees subsequent alerts.

Unfollowing changes the monitoring subscription without changing the wallet’s public blockchain history. Historical analytical records follow the service’s retention rules, separately from the active follow list. Personal messages keep alerts outside the group while the service handles their delivery data. A channel subscription changes the audience: wallet trade reports become shared information for the room.