OBHOD

Telegram bot over MTProto that manages the server it runs on and hands out post quantum VLESS subscriptions. It never talks to another machine over SSH: the management channel is loopback only, every agent is a local argv.

Install

curl -fsSL https://raw.githubusercontent.com/i-execute/OBHOD/main/get.sh | sudo bash

Root only, installs into /opt/obhod, state in /var/lib/obhod, runs as obhod.service. The installer reads the bot token with read -r -s, writes /etc/obhod/obhod.env as 0600 inside a 0700 directory and drops the variables from the shell, so a key never reaches the process list, the history or a log.

Cores

Nothing is hardcoded to one engine. BOT/cores.py is a registry, the home screen is a summary of every core that is registered, and every button lands on a concrete core.

Both answer through the same proto 3 envelope, so one code path parses them. They run side by side and…