Vigi Miner
Vigi Miner is a native desktop application that installs the verified VigiChain node, supervises it and reports what the operating system is actually enforcing. Consensus stays inside Core: the application operates the node, it never decides what a valid block is.
Testnet only. Mainnet appears in the interface and is refused by the backend until the Core launch gate opens. There is no signed public release yet: Windows and Linux builds are produced on every push to the development branch, and this page will carry them the day they are signed.
The application, captured
Real captures of the running application, in English. Three of its six views; the others are added as they are taken.
What it supervises
It starts and stops the signed node process, holds the reward address and the thread count, and shows the real process state — running, stopped, contained, with the process identifier when there is one. Every consensus rule stays where it belongs, inside VigiChain Core.
Nothing unverified is installed
The install action performs the same verification as the one-line installer: the detached signature over the binary, the signed checksum manifest, the signed build provenance that binds that exact digest to one source commit, and the software bill of materials. A missing verifier is a failure, not a warning.
Isolation you can read
Private directories, a cleared environment, process-tree containment through a Windows Job Object and a hard ceiling on CPU. The interface prints the containment level it actually obtained and names it — it will not call a private directory a sandbox.
Telemetry without guesswork
Read-only signals are accepted only from the local telemetry contract. When the Core is not answering, the panel says so and leaves dashes rather than inventing numbers, and it refuses to mix readings from two different networks.
Vigi Compact
Canonical node data is compressed losslessly, restored byte-for-byte and hash-verified before it is used. Nothing is discarded and nothing is summarised: a compacted node can still answer for every block it holds.
Every control is drawn by the application
The language picker and the CPU ceiling are components of this interface rather than system form widgets, with the listbox and slider semantics a screen reader needs. The layout is fluid as well: on a laptop the column of readings stays on screen instead of being cut off the edge.
Builds