Network Halted When Running Nodes with Different Versions

[kmlbgn]

Description

The KIRA Network halts when nodes are run with different versions (Genesis validator with sekaid v0.3.45 and other nodes with sekaid v0.3.44).

Steps to Reproduce

1. Run Genesis validator with sekaid v0.3.45.
2. Run other nodes with sekaid v0.3.44.
3. Assign a role to one of the validators.
4. Join the set with one of the validators.

Expected Behavior

A validator with a different version should panic or fail immediately after getting the genesis.json.

Actual Behavior

1. For validators: Consensus failed.
2. For genesis: The network stopped as it's not possible to get a quorum.

Logs from the halt event:

May 14 13:33:47 devnet sekaid[2471]: 1:33PM INF No addresses to dial. Falling back to seeds module=pex
May 14 13:34:17 devnet sekaid[2471]: 1:34PM INF Saving AddrBook to file book=/home/chaos/sekai/config/addrbook.json module=p2p size=4
May 14 13:34:17 devnet sekaid[2471]: 1:34PM INF Ensure peers module=pex numDialing=0 numInPeers=4 numOutPeers=0 numToDial=32
May 14 13:34:17 devnet sekaid[2471]: 1:34PM INF We need more addresses. Sending pexRequest to random peer module=pex peer="Peer{MConn{192.168.88.123:51090} 77f8bdaee841f4b0ac231d3a307f729cd9bcdb0c in}"

[kiragpg]

A validator with a different version should panic or fail immediately after getting the genesis.json.

Did you try this with pure sekai or used interx and kira manager tool as well? This should be prevented on kira manager tool, sekai does not have ability to check it - this is common on all cosmos chains