bug (hubble): onChainSigners aren't consistent across hubs

[manan19]

What is the bug? Found an example of onChainSigners which aren't consistent across hubs https://lamia.farcaster.xyz:2281/v1/onChainSignersByFid?fid=788624 has the SIGNER_EVENT_TYPE_ADD event vs. https://hoyt.farcaster.xyz:2281/v1/onChainSignersByFid?fid=788624 doesn't have the signer event Neynar hub doesn't have the SIGNER_EVENT_TYPE_ADD event either

How can it be reproduced? (optional) Include steps, code samples, replits, screenshots and anything else that would be helpful to reproduce the problem.

Additional context (optional) Add any other context about the problem here.

[Rufusemmanuel]

It seems like there's inconsistency in the “onChainSigners” data across different hubs when querying the same file identifier(FID). This inconsistency suggests a potential bug or discrepancy in how the data is being handled or propagated across these different hubs.

POTENTIAL REMEDIES TO ISSUE:

Check if the hubs are using the same version of the underlying software or API.

Verify if there are any differences in how events are queried for “onChainSigners” data across these hubs.

Review the data processing steps for “onChainSigners” to identify any potential points of divergence.

Ensure that the events are being recorded and queried correctly across all hubs to maintain consistency in the data.

Addressing this issue may involve debugging the data pipeline or API endpoints used by the hubs to ensure they are synchronized and correctly reflecting the expected events for any given FID. This should be treated with urgency.