Telegram bot
One bot for the whole product. Create it in @BotFather and paste the token here.
The token is stored encrypted and is never shown again. Leave empty to keep the current one.
Outgoing email
The mailbox letters to clients are sent from: password resets, email confirmations and account security notices.
This is what the client sees in the From field. Most relays only accept an address of their own domain.
Port 465 — TLS right away; 587 or 25 — STARTTLS. There is no separate switch: the port decides.
The password is stored encrypted and is never shown again. Leave empty to keep the current one.
Delivery queue and failures
What is waiting to be sent in each channel, what failed in the last 24 hours, and how long the oldest notification has been waiting.
| Channel | Waiting | Deferred | Sending | Failed, 24 h | Oldest ready since |
|---|
| When | Recipient | Notification | Attempts | Error | Actions |
|---|
Notification log
Every notification: terminal events, account letters, broadcasts, the daily report. Open a report to see who got it and what failed.
| When | Notification | Recipients | Delivered | Status | Actions |
|---|
| Recipient | Channel | Status | Attempts | Error | Sent | Actions |
|---|
Notification types and channels
Changes apply to the next notification right away. Password and email letters, terminal events and the test notification cannot be turned off as a type — their delivery is set per topic and channel below.
How long notifications are kept
The bell of the client's terminal keeps a notification for the hours below; older entries disappear within 5 minutes. The event log and delivery report for staff are kept for the days below. The bell cannot outlive the history.
Types
| Notification | Active |
|---|
Topics × channels
«Always» — people cannot turn it off. «On / off by default» applies to people who have not chosen themselves. «Closed» means nobody gets it through this channel, even those who turned it on.
Notification texts
Pick a notification and a language. Variables in {{double braces}} are filled in when the notification is sent. Empty language — people get the English text.
Preview on made-up data — the link is fake.
Connected clients
Only these receive broadcasts. The bot cannot message anyone who has not pressed Start.
| Client | Telegram | State | News and offers | Connected |
|---|
New broadcast
Channels
News and offers go only to people who opted in. Service messages go to everyone, through every chosen channel they have.
Sent broadcasts
| When | Internal title | Kind | Status | Delivered | Actions |
|---|
| Recipient | Channel | Status | Attempts | Error | Sent |
|---|
Client requests
Everything clients write to us, in one place.
| When | Client | Subject | Status | Photos |
|---|
Sign-in email
The new address gets a confirmation email.
Change password
All other sessions will be closed.
Clients
Period for PnL and partner profit
Click a header to sort (again — reverse). Partner profit is the sum of their shares from invoices issued in the period.
Payment details
The default wallet is where clients without their own address pay.
Used when a client has no own address. A client's own address is set by a superadmin on the client's «Invoices» tab.
Automatic payment reminders are off: their sender was removed together with the old subscription. The lead time and the texts below are kept but not used.
Fleet health
One screen for “who is not working, and why”. Contact comes from the enforcement check the tick already sends every box, so showing this screen does not poll the boxes. It is kept in memory: right after a panel restart boxes show “no contact yet” until the first tick.
Hosts
Dedicated hosts that run client boxes. Free places and IPs, the host's own feed bot and when the host last answered come from the panel; the boxes are asked about money only when you press «Money on the host».
Deploy
Restarts every client's box on the given image, one SSH per box. This is the biggest single action in the panel — it touches everyone's live trading bot at once.
| Client | Result | Time |
|---|
Clients
| Client | State | No answer for | Detail | Actions |
|---|
Period — invoices issued on these days (UTC)
New admin-panel user
Staff
| Role | State | Last sign-in | Actions |
|---|
Feed status
Live counters from the bot itself. “healthy” only means its HTTP server answers — read the frames and clients below to tell whether the feed is actually flowing.
The bot restarts itself: it exits and systemd brings it back. The feed is down for a few seconds and every client reconnects.
Market feed (spread-finder)
—
These apply to the shared feed — every client at once.
Exchanges on the wire
Turning one off removes it from the feed within one frame; connections stay warm, so turning it back on costs nothing.
Disabled pairs
A pair listed here never enters the registry: it is not subscribed, not calculated and not shipped.
Exchanges disabled in the bot
The bot stops processing a disabled exchange and stops talking to it, live.
Announcements
Dates are usually parsed out of the announcement text, not published by the venue — so they can be wrong.
| Effective | Exchange | Symbol | Market | Date from | Announcement | Actions |
|---|
Restart required
Read-only here: changing these needs a restart of the bot.
| Setting | Value |
|---|
Documentation
Instructions and notes for the team. Anyone on staff can read them; the superadmin writes and edits.
Audit log
| When | Who | From where | Action | Object |
|---|