Settings & Configuration
Advanced Configuration
Advanced settings for power users who want fine-grained control over Sentinel's behavior.
Configuration Files
Sentinel stores its configuration in JSON files that can be edited directly.
scraper_config.json
Global scraper settings:
{
"api_id": "YOUR_API_ID",
"api_hash": "YOUR_API_HASH",
"keywords": ["CA:", "contract:", "mint:"],
"puzzle_solving": true,
"audio_processing": true
}chats_config.json
Chat-specific monitoring configuration:
{
"chats": [
{
"link": "https://t.me/groupname",
"enabled": true,
"keywords": ["specific", "keywords"]
}
]
}Changes to these files are picked up by the config server and synced to the scraper.
Config Server
The config server runs as a WebSocket server that bridges the Chrome Extension and the scraper engine. It starts automatically when you run START_SENTINEL.sh.
- Listens for configuration changes from the Extension
- Pushes updated settings to the scraper in real time
- No manual configuration needed
TDLib Settings
The Telegram Forwarder uses TDLib (tdjson.dylib on macOS, tdjson.dll on Windows). Advanced TDLib parameters can be configured for:
- Custom database directory
- Log verbosity level
- Proxy settings
Troubleshooting with Logs
If you experience issues, check the scraper logs:
- Logs are output to the terminal where
START_SENTINEL.shis running - Increase log verbosity by modifying the scraper configuration
- Common issues:
- Auth errors: Re-enter credentials in the Extension
- Connection drops: Check internet stability
- Missing detections: Review keyword configuration
File Structure
sentinel/
├── Extension/ # Chrome Extension
│ ├── manifest.json
│ ├── popup.html
│ └── ...
├── native-host/ # Native messaging host
│ ├── install.sh
│ └── ...
├── config_server # WebSocket config server
├── telegram_forwarder # Main scraper engine
├── tdjson.dylib # TDLib (macOS)
├── scraper_config.json # Global settings
├── chats_config.json # Chat configuration
└── START_SENTINEL.sh # Launch script