Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: Use current validator for tracked shards check (#11828)
See #11821 for context. Check if this is a current validator using current epoch info, not merely the fact that validator key exists. # Testing ## Current Mainnet (protocol version 67) Pre-requirements for the check to kick-in: * `tracked_shards=[]` in `config.json` * `validator_key.json` exists Tested with different validator IDs: * `node` - dummy validator ID, it **did not** crash * `gritsly.poolv1.near` - existing validator with the lowest stake, not marked as `CP` in the debug page, it **did not** crash * `solidstate.poolv1.near` - existing validator with the lowest stake that was marked as `CP` in the debug page, it **crashed** ## Current Testnet (protocol version 69) Pre-requirements for the check to kick-in: * `tracked_shards=[0]` in `config.json` * `validator_key.json` exists Tested with different validator IDs: * `node` - dummy validator ID, it **did not** crash * `lavenderfive.pool.f863973.m0` - existing validator with the lowest stake, not marked as `CV` in the debug page, it **did not** crash * `snsmlnn.pool.f863973.m0` - existing validator with the lowest stake that was marked as `CV` in the debug page, it **crashed**
- Loading branch information