Explain why an initial Avalanche L1 validator has no staking rewards
An L1 configured with a proof-of-stake manager can include validators introduced at conversion. Their presence and weight alone do not establish eligibility for staking rewards.
Trace the validator’s admission path
Read the converted validator set from the conversion transaction and the manager’s initialization history. Initial validators are treated as proof-of-authority members. Compare the target registration with subsequent registrations made through the staking manager. Keep validation IDs distinct even when a machine later reuses a node identity.
Initial validator: present in ConvertSubnetToL1Tx
Staking registration: initiated and completed through StakingManager
Reward attribution: identify the registration path and its start event
Start reward accounting at the relevant completion
Suppose node A entered during conversion and node B completed a later PoS registration. The staking manager can accrue rewards for B from completion, subject to its rules, while A’s initial registration is ineligible. Track continuous P-Chain fees separately: paying those fees enables active validation and does not establish a staking reward claim.