Expected behavior
When the node is running correctly, operators should be able to verify that:
- the node is actively participating in the network
- network activity (blocks, peers, messages, or tasks) is progressing
- the node is being counted by the protocol or network
- the node is eligible for incentives, rewards, or snapshots
This information should be observable through metrics, APIs, logs, or documented verification steps.
Actual behavior
Currently:
- the node process runs normally
- health checks report OK
- logs show no critical or fatal errors
However:
- no metrics expose active network participation
- no API endpoint confirms whether the node is being counted by the network
- logs do not confirm successful participation events
- operators cannot distinguish an actively participating node from an inactive or uncounted one
As a result, the node may appear healthy while not being verifiably active or recognized by the network.
This makes it impossible for operators to independently verify correct configuration or incentive eligibility.
Expected behavior
When the node is running correctly, operators should be able to verify that:
This information should be observable through metrics, APIs, logs, or documented verification steps.
Actual behavior
Currently:
However:
As a result, the node may appear healthy while not being verifiably active or recognized by the network.
This makes it impossible for operators to independently verify correct configuration or incentive eligibility.