Cross-platform support — Python unified version (v3.0)

[BaumerCrypto]

The current oracle-monitor.sh is Linux-only (bash, systemctl, pgrep, free, etc.). Many oracle operators run Windows or macOS.

Options:

1. PowerShell script (.ps1) for Windows — same logic, Windows-native commands, digibyte-cli.exe
2. macOS bash variant — minor tweaks to existing script (no systemctl, different free syntax)
3. Python cross-platform version — single script runs on Linux, Windows, macOS. Python available everywhere, digibyte-cli RPC works the same, Discord webhooks are just HTTP POST.

The Python approach is likely the best long-term solution — one codebase, all platforms. But it's the biggest build.

Could start with a Windows PowerShell port since that's where the demand is, then consider Python for a unified v3.0.

Version: v3.0

[BaumerCrypto]

Options 1 and 2 are shipped.

Windows PowerShell port — oracle-monitor.ps1 (v2.2-win.1) + config.template.ps1. Runs on Windows PowerShell 5.1 (preinstalled on every Win 10/11) and PS 7. Zero dependencies — no jq needed, PowerShell parses JSON natively. Get-Process / Get-CimInstance / Get-PSDrive / w32tm stand in for pgrep / free / df / timedatectl, Task Scheduler stands in for cron. Handles the PS 5.1 traps: ships UTF-8 with BOM, forces TLS 1.2, sends the webhook body as UTF-8 bytes so the emoji survive.

macOS port — oracle-monitor-macos.sh (v2.2-macos.1) + config-macos.template. Written for the stock bash 3.2 every Mac ships with — no Homebrew bash needed, jq is the only dependency. vm_stat + sysctl replace free, df -g replaces df -BG, an sntp offset query replaces timedatectl, optional launchctl check replaces systemctl. The cron-on-macOS gotchas (full paths, Full Disk Access, sleeping laptops) are documented in the script header.

Both are faithful ports of Linux v2.2, not rewrites: heartbeat-based quorum counting, anti-flap cooldown + hysteresis, single quorum_state file, escalation always immediate, identical alert text. The function structure mirrors the bash script 1:1 so all three can be diffed side by side. Both also pick up two small improvements: node version is read via getnetworkinfo RPC instead of invoking the daemon binary, and the watched process name is configurable (DAEMON_PROCESS) for operators running the Qt wallet instead of headless digibyted.

Both ports also add something the Linux original doesn't have yet: a watch mode (-Watch on Windows, --watch on macOS) — a live console dashboard that redraws the full 11-check status every 60s. It runs alert-free and state-free, so it's safe to leave a window open alongside the scheduled checks. Coming back upstream to the Linux script in the next release.

Setup for both platforms: CROSS_PLATFORM_SETUP.md.

Testing status: the macOS script's logic has been exercised end-to-end in a mock harness (fake vm_stat/sysctl/df/sntp/pgrep + canned RC44 RPC responses) — every alert path, recovery, one-shot dedup, and the full quorum anti-flap machine including hysteresis dead zone and cooldown expiry. The PowerShell port follows that same verified logic 1:1 and is hand-audited against the PS 5.1 traps, but hasn't executed on a real Windows box yet. Neither has run against a live node on real Apple/Microsoft hardware. I run the Linux version in production on my own oracle; field reports from real Windows/Mac setups are what these need next — if you run one, report anything weird here.

Option 3 (Python unified) stays on the roadmap as v3.0 — keeping this issue open to track it. Once all three native versions have settled, one Python codebase replaces them.

Version: v3.0