Summary
After running a fully synced Movement full node, there is currently no way to verify whether the node is actually recognized by the network and counted for uptime or incentives.
Expected behavior
Node operators should be able to verify that their node is:
- connected to the network
- visible and recognized
- eligible for uptime tracking.
Actual behavior
Even when the node is fully operational:
- ledger_version increases correctly
- block_height increases correctly
- API responds normally
There is no:
- node identifier
- public explorer
- uptime endpoint
- eligibility confirmation.
Impact
Node operators may run nodes for long periods without knowing whether they are contributing to the network or will be included in incentive snapshots.
This creates uncertainty and may discourage participation in the testnet.
Steps to reproduce
- Run a Movement full node following official documentation.
- Wait until the node is fully synced.
- Verify ledger_version and block_height are increasing.
- Attempt to find any method to confirm node visibility or eligibility.
Suggested solution
Provide a public method to verify node visibility, such as:
- a status endpoint
- a node explorer
- or an uptime heartbeat mechanism.
Summary
After running a fully synced Movement full node, there is currently no way to verify whether the node is actually recognized by the network and counted for uptime or incentives.
Expected behavior
Node operators should be able to verify that their node is:
Actual behavior
Even when the node is fully operational:
There is no:
Impact
Node operators may run nodes for long periods without knowing whether they are contributing to the network or will be included in incentive snapshots.
This creates uncertainty and may discourage participation in the testnet.
Steps to reproduce
Suggested solution
Provide a public method to verify node visibility, such as: