Potential Hedera staking issue regarding inactive nodes and pending rewards

Path: /hedera/core-concepts/staking/stake-hbar
Potential Hedera staking issue regarding inactive nodes and pending rewards

Description:

If an account is staked to a Hedera node, and later that node becomes inactive, removed, or no longer participates correctly in staking rewards, the account may continue pointing to the old node.

However, automatically switching the account to another node may not be safe, because changing staking configuration could cause pending rewards to be lost or handled incorrectly.

Potential impact:

* Account may remain staked to an inactive node
* Rewards may stop or behave unexpectedly
* Automatic reassignment may risk loss of pending staking rewards
* Users/applications may not have clear protocol-level visibility into the safest action

Example scenario:

1. Account stakes to Node A
2. Node A later becomes inactive
3. Account still references Node A
4. Switching to Node B may cause pending rewards to be lost
5. Leaving it unchanged may stop future rewards

Suggestion:

Please consider adding a protocol-level safeguard that does not automatically switch nodes, such as:

* clear staking status for inactive nodes
* reward-safe warning/status flag
* explicit network response showing pending reward risk
* safe claim-before-restake mechanism
* documentation for correct handling of inactive staking nodes

This would improve staking safety without risking pending reward loss.