Curretnly, we are detecting terravaloper... from transaction by regular expression for detecting which validator should be updated. Validators are doing oracle votes per 5 heights and because of this, collector is doing excessive updates.
Update
Since Oracle has nothing to do with validator statistics we are displaying, we can filter out tx that has oracle/ message inside.
Problem
Curretnly, we are detecting terravaloper... from transaction by regular expression for detecting which validator should be updated. Validators are doing oracle votes per 5 heights and because of this, collector is doing excessive updates.
Update
Since Oracle has nothing to do with validator statistics we are displaying, we can filter out tx that has
oracle/
message inside.