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

Sort same-priced transactions by arrival time #209

Closed
ghost opened this issue Oct 19, 2021 · 4 comments
Closed

Sort same-priced transactions by arrival time #209

ghost opened this issue Oct 19, 2021 · 4 comments

Comments

@ghost
Copy link

ghost commented Oct 19, 2021

Rationale

Currently, same-priced transactions are not sorted. Because of this, back-run arbitrators have to send thousands of transactions for one arbitrage opportunity. This is the main reason why there are too many spams in the Polygon network.

ETH had the same problem and it has been solved since go-ethereum v1.9.19. I think Polygon can also have this feature to reduce the spams.

@ssandeep @Uttam-Singhh

@ferranbt
Copy link
Contributor

Hi! Thank you for opening the issue. Could you point me where go-ethereum implements this change? We usually upstream from the main repo so we should have the change applied too.

@ghost
Copy link
Author

ghost commented Oct 21, 2021

@ferranbt Please check this PR. There are similar code in Polygon code base. I'm not sure why it doesn't work like ETH.

This behavior is found by the following case:
A back-run arbitrator will monitor tx pool and then send arbTx when a profitable userTx is found.
For ETH, arbTx is usually behind userTx. Sometimes arbTx will be in front of userTx but only a very small count or zero of other txs between them.
For Polygon, there is a significantly high rate that arbTx will be in front of userTx. And there will be many other txs between them, sometimes hundreds.

@ghost
Copy link
Author

ghost commented Nov 17, 2021

close this issue since no one care about this.

@ghost ghost closed this as completed Nov 17, 2021
@ajb
Copy link

ajb commented Jan 1, 2022

The reason that the expected "first in first out" behavior doesn't work on Polygon is because of the sentry / validator architecture.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants