@cass_on_mars: Quorum casts not posting or replicating to Farcaster fork

Submit
@cass_on_mars
@cass_on_mars

We are aware that casts on Quorum are not successfully posting, nor replicating to the farcaster fork. We are currently diagnosing. So far, we have confirmed: the snapchain mempool topic, which our node previously was meshed with without issue, suddenly no longer can mesh with them. We have done typical diagnostics and procedures – we cannot get it to peer. We do not know yet if this is intentional from the NS side, but we are working to resolve the issue as soon as possible. There is no indication of protocol incompatibility being the root cause, rather, some kind of configuration change, not on our part.

Cassie Heart (@cass_on_mars)

@thefaketomato we're trying to diagnose this, but what we're currently seeing is that casts sent to haatz (the endpoint quorum uses) are not getting accepted in the forwarding to snapchain. can't confirm yet, but it's acting as if they blocked our peer from forwarding messages. f…

x.com

@cass_on_mars: Quorum casts not posting or replicating to Farcaster fork

AI summary of the linked article

Quorum, a Farcaster fork, reports that casts are neither posting nor replicating to the Farcaster fork, and it is currently diagnosing the problem. Its confirmed finding is that its node, which had previously meshed without issue with the snapchain mempool topic, can no longer mesh with it, and standard diagnostics have not restored peering. Quorum does not yet know whether the NS side intentionally caused this, but it says there is no sign of protocol incompatibility and suspects a configuration change not made on its end.

No comments yetWhat caught your eye? Start the discussion.