Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check if proxy request account exits or not before execute Call in SOLANA. #454

Open
sherpalden opened this issue Dec 6, 2024 · 0 comments · May be fixed by #456
Open

Check if proxy request account exits or not before execute Call in SOLANA. #454

sherpalden opened this issue Dec 6, 2024 · 0 comments · May be fixed by #456
Assignees
Labels

Comments

@sherpalden
Copy link
Collaborator

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:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. 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.

@sherpalden sherpalden self-assigned this Dec 6, 2024
@sherpalden sherpalden linked a pull request Dec 9, 2024 that will close this issue
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant