How ton-blockchain/mytonctrl works
Project type and purpose
• MyTonCtrl is primarily a console-based node/validator management application for the TON blockchain.
• It acts as a wrapper around external TON tooling (fift, lite-client, validator-engine-console) and also provides installer functionality (mytoninstaller), core business logic (modules), and a core API library (mytoncore).
File structure
• Top‐level directories:
• functions/ – small standalone utility functions (e.g., session statistics).
• modules/ – command implementations covering alerting, backups, pool/nominator/validator management, telemetry, Prometheus, wallets, etc.
• mytoncore/ – core Python library exposing abstractions over Fift, lite‐client, contracts, telemetry, models, and scanner.
• mytonctrl/ – CLI front‐end application that ties together modules and mytoncore to present user commands and an installer mode.
• mytoninstaller/ – installer front‐end for setting up TON node or validator, packaging systemd, JSON-RPC, toncenter, and related scripts.
• scripts/ and tools/ – miscellaneous shell and Python scripts for installation, backups, key injection, etc.
• tests/ – integration/functional tests for block scanning, TPS load, bounce tests.
• Notice patterns:
• A layered architecture (CLI → modules → core library → external executables & contracts).
• An installer sub‐application with its own configuration and scripts.
• Subdirectories for contracts under mytoncore/contracts indicating embedded smart-contract artifacts.
README for additional insights
• Confirms console application wrapping Fift, lite-client, validator console.
• Describes two installation modes: liteserver or validator.
• Mentions telemetry to toncenter.com and optional web admin panel / local toncenter copy.
• application modules in another,
• external executables in a third,
• external services/endpoints in a fourth.
• Notes on deployment: Linux environment, Python interpreter, systemd.