How relayers vote for proposal?

[Kvenessa]

1. In a multiple relayer setup with 2-3 relayers, does all relayers listen and receive the proposal event?

2. How relayer votes for the proposal, and what conditions are checked before accepting/voting for proposal?

3. After sufficient proposal which relayer from these group of 2-3 relayer submit the proposal?

[waymobetta]

Hi @Kvenessa,

1. In a multiple relayer setup with 2-3 relayers, does all relayers listen and receive the proposal event?

Yes, all of the relayers listen and receive the proposal event.

2. How relayer votes for the proposal, and what conditions are checked before accepting/voting for proposal?

Currently, the relayers all default to passing the vote, though this can be configured based on your own custom logic for deciding what conditions are to be passed.

shouldVote perfoms a few checks on conditions such as, hasVoted and proposalIsComplete but can include additional logic if deemed necessary.

3. After sufficient proposal which relayer from these group of 2-3 relayer submit the proposal?

The relayers all execute proposals (votes) unless certain conditions are not met that prevent them from voting, but the relayerThreshold is considered during this step, as only relayerThreshold relayers is required for the vote to pass.

[Kvenessa]

The relayers all execute proposals (votes) unless certain conditions are not met that prevent them from voting, but the relayerThreshold is considered during this step, as only relayerThreshold relayers is required for the vote to pass.

In this case there are 3 relayers relayer1,2,3 and relayer1 proposes the proposal and other relayers also tries to propose in that case since for this token transfer deposit data proposal is already created by relayer1 ,relayer2,3's votes will be recorded and once relayerThereshold is reached(say 3votes required) the proposalfinalized event is raised thus notifying the relayers, relayer1 will execute transaction for deposit on chainB (i.e. triggering appropriate handler and releasing requested tokens in chainB ) since proposal was initiated by relayer1 it will execute it and will have to pay gas fees for chainB transaction and not relayer2,3.

@waymobetta Is this understanding correct?

[waymobetta]

In this case, all relayers will be paying gas fees for transactions, though the transactions will fail if another relayer's transaction was mined first, which is started via a non-blocking process to watch for certain events, shown here within the scope of a goroutine.