Crypto KOL Radar

Wake-up KOL alarms do not require a contract address: some tokens live on their own PoW / custom chains. A very strong signal is still 3+ distinct channels (after any aliases) mentioning the same token within 1h with at least one fresh call; contract is optional.

Pushover wake alarms go through a shared sender script on my computer: title, message, optional URL, priority (default 2 = emergency). It downgrades priority during a configured daily quiet window and while a mute_until timestamp file is in the future.

In KOL notifications, show signal strength (how many distinct channels mentioned a contract address or $TICKER in the last 1h, 6h and 24h, strongest first). Any token mentioned by 2 or more channels should always be reported, and each channel should be marked as a first or repeat mention of the token that week.

Monitor the owner's Telegram KOL folder in real time (reacting to new message batches, not just periodic digests), judging each message and notifying only about genuinely important information while silently skipping spam and useless content.

Automatically follow changes to the watched Telegram folder (channels added or removed) without the owner having to notify the assistant.

Very strong KOL signals should trigger a loud night-time wake-up via Pushover, loud enough to break through iPhone Sleep Focus (Critical Alerts or a Sleep Focus exception).

Prefer mute and unmute of alarms with clickable chat buttons (mute for 2h / unmute) and send a fresh button card after each click.

When the Telegram listener runs on the owner's VPS (not my computer), keep the hourly box health-check paused, and never run session-sharing scripts on my computer that can kill the remote listener.

Optional channel aliases (same people = one source for signal strength) are set by the owner during setup if needed; do not hardcode any specific channel pairs.

Use on the first conversation with a new owner after they import this Telegram KOL watcher template.

Use when a Telethon Telegram user-session listener on the assistant's computer cannot keep a raw MTProto TCP connection (HTTPS-only egress proxy, repeated disconnects, wrong session ID, or Server closed the connection), and you need MTProto-over-WebSocket plus a self-watchdog.

Fires when the Telegram listener posts a new message batch; judges signal strength and alerts only on what matters.

Hourly check that the on-box Telegram listener is alive; silent when healthy, alerts the owner when it needs attention.