You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Currently, there are cases where the relayers continuously call the already executed ExecuteCall transaction for the following two reasons:
If there are multiple executor relayers running.
If the txn is not finalized within the set confirmation interval in the relayer but is finalized later in the chain. In this case, relayer interprets the txn as failed but infact in the chain if it is passed, then the relayer keeps retrying the already finalized txn which keeps failing continuously.
For the SOLANA, without making any changes in the contract side, it looks like relayer can query for existence of proxy request account and decide either to execute the ExecuteCall txn or not. This way spamming can be prevented.
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently, there are cases where the relayers continuously call the already executed
ExecuteCall
transaction for the following two reasons:For the SOLANA, without making any changes in the contract side, it looks like relayer can query for existence of proxy request account and decide either to execute the
ExecuteCall
txn or not. This way spamming can be prevented.To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: