CirrusD nodes also needs to validate whether blocks that they receive contain valid commitment height, otherwise they are potentially relaying invalid block. This is causing these nodes to get banned incorrectly.
So the approach here is the split the commitment height check into its own rule so that CirrusD and CirrusDnsD run just that and then the miners the full set of checks.
CirrusD nodes also needs to validate whether blocks that they receive contain valid commitment height, otherwise they are potentially relaying invalid block. This is causing these nodes to get banned incorrectly.
So the approach here is the split the commitment height check into its own rule so that CirrusD and CirrusDnsD run just that and then the miners the full set of checks.