Today my pool #ORPH lost a slot battle. Given it is approaching 200 produced blocks, this was bound to happen eventually, so kudos to the other pool for being luckier.
However, this raises an interesting question. While it is easy to figure out when you are on the losing end (lost slot battle: somebody else produced a block with the exact same slot number; lost height battle: somebody else produced a block with a higher but close slot number), is it possible to figure out when your pool is winning a slot battle or when your pool is causing somebody else to lose a height battle?
Is there a way to extract relevant information from the cardano-node logs (e.g. network fork events)?
Even if that was possible, according to my understanding, cardano-node only keeps track of network forks observed by individual relays/producers, therefore only a part of the network will ever learn of the lost blocks. Is this correct?
If yes, would it make sense to send such observed network fork events to a centralized service (e.g. similar to how tips are sent to pooltool.io to calculate propagation delays) to create a searchable database? It seems to me we are lacking such a feature that could be used to monitor the health of the network and optimize the topology (in case of height battles). Any thoughts about this?