During a keyper set transaction, generally two keyper sets will be online, the old and the new one (potentially with some overlap). Currently, both will try to send the new batch config to Shuttermint. However, messages from the new set will be rejected because Shuttermint doesn't recognize them as keypers yet. This results in the keyper crashing.
Keypers should
not send messages if they know that it will be rejected, ie only send messages if it is a member of at least the old set, or both the old and the new set.
probably don't crash if the message gets rejected. We should however make sure that sending a message is retried. Crashing and relying on restarts via docker might be the easiest way to ensure this, albeit quite ugly.
jannikluhn
commented
16 hours ago
During a keyper set transaction, generally two keyper sets will be online, the old and the new one (potentially with some overlap). Currently, both will try to send the new batch config to Shuttermint. However, messages from the new set will be rejected because Shuttermint doesn't recognize them as keypers yet. This results in the keyper crashing.
Keypers should