Control panel · Zenon Pillar Tracker

Administrator access

Runtime settings

Node and collector

Collection

Node RPC URLs One HTTP(S) JSON-RPC endpoint per line. The first endpoint is primary; the others are used for failover. A node on this Linux host can use http://127.0.0.1:35997; use https:// when the endpoint is behind TLS. Reference reward address The pillar address used to determine the current epoch and read reward history. Poll interval (seconds) How often the collector checks the node. Pillar page size Number of pillars requested per node page. Reward page size Number of reward records requested per page. Stale grace runs Successful-looking retries allowed before a run is marked stale. Missed momentum threshold Missed checks before a pillar is marked inactive. Require sync informationOnly use nodes that report synchronization state. Allow an empty pillar listKeep a poll successful when the node returns no pillars.

Node health

Failover and retries

Maximum frontier age (seconds) Maximum age accepted for a node frontier; zero disables this check. Node failure cooldown (seconds) Time before a failed node is tested again. Sync retry window (seconds) How long a node may recover while it is syncing. Sync retry interval (seconds) Delay between synchronization checks.

Network requests

Timeouts and rate limits

HTTP timeout (seconds) Maximum time to wait for one HTTP request. RPC retries Additional attempts after a failed node request. Rate-limit max wait (seconds) Maximum wait before a rate-limited request is skipped. Telegram rate-limit retries Additional attempts after Telegram asks the bot to slow down.

Notifications

Delivery channels

Telegram channel ID Optional default channel for general Telegram notifications. Pinned message ID Message ID used for the pinned statistics update. Development channel ID Optional separate channel for development notifications. Discord webhook Optional Discord webhook used for notifications.

Restart the collector after changing collector settings.

Notification routing

All pillar subscriptions

Subscriptions are never deleted. Assign them to a user, edit them, or deactivate them.

Owner	Destinations	Pillars	Events	Status

Access control

Users

Username	Role	Status	Subscriptions	Last login

Access

Sessions

Application logs

Log rotation

Operations

Logs and audit trail

Collector service

Pillar tracker process

Checking…

Checking whether the collector is running.

Data collection Checking…

Checking the latest collector poll.

Loading collector logs…

Loading…

Admin actions

When	User	Action	Entity	Details

My subscriptions