SEDA Protocol: Attacker can exploits batch sender role to block result Submissions via fee transfer reversion

SEDA's SedaCoreV1 lets any address post a validator-signed batch and become its batch sender, which later entitles them to batchFee rewards paid in native tokens. Because the batch sender is set to msg.sender with no allowlist, an attacker can front-run a legi …