Practical overview
When it fits
Use it when you want a self-run service to watch supported exchange markets and route trade or volume alerts to a Telegram group or channel.
Who it is for
- Developers who want to run a multi-exchange trade and volume alert app.
- Operators who want to configure watched currency pairs and alert thresholds.
Documented uses
- Monitor order books and depth charts across supported exchanges.
- Receive Telegram alerts about large trades and trading volume.
- Configure currency pairs and adjust alert limits for watched markets.
Requirements & limits
The project is published as a public repository under the GPL-3.0 license.
- Requires a PostgreSQL database and Telegram bot configuration for the documented setup.
- Currency pairs should be selected with exchange support in mind; the README recommends pairs supported by both Binance and Bitfinex.
- Raw REST API integrations may require manual stream management.
- The documented migration command deletes and recreates database tables.
- Telegram is the current documented alert medium; replacing or adding services requires code changes.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up the app and Telegram alert destination
Prepare the documented app configuration and start Crypto Whale Watcher.
Before you start
- A forked and cloned repository
- A Telegram bot token and a group or channel chat ID
- A PostgreSQL database
- Environment variables for BOT_TOKEN, CHAT_ID and DATABASE_URL
- Node.js package installation via npm
Steps
Create a Telegram bot and note its authorization token.
Create a group or channel, add the bot, and obtain the destination chat ID.
Create a PostgreSQL database and a .env file in the parent directory; add the bot token, chat ID and database URL as environment values.
Run npm install, then run npm run start.
Expected outcome
The README describes the app running locally on port 3000 and sending alerts through Telegram.
Guide limitations
- The app uses raw REST APIs and may require manual stream management.
- The README says the database migration command deletes and recreates all tables; it is not included in this setup sequence.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 15 October 2026
- Original website title
- uzair-inamdar/crypto-whale-watcher · Official homepage title · retained in its source language