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

MEV opportunity in forceTransmute #39

Open
boldgate0759 opened this issue May 8, 2023 · 0 comments
Open

MEV opportunity in forceTransmute #39

boldgate0759 opened this issue May 8, 2023 · 0 comments

Comments

@boldgate0759
Copy link

Hi, when investigating the contracts of NAOS, I really appreciate your great work in designing this protocol.
However, I have an issue regarding the forceTransmute function in the Transmuter contract.

function forceTransmute(address toTransmute) public runPhasedDistribution updateAccount(msg.sender) updateAccount(toTransmute) checkIfNewUser {

I can see that there is no access control on this forceTransmute function, and anyone can call it to obtain profits as tokensInBucket, which can be later withdrawn and claimed.
I understand that the purpose here is to incentive blockchain users to transmute some address which has over-filled and keep the protocol running smoothly.
However, any transaction from a normal/honest NAOS user who makes efforts to identify an over-filled address and call forceTransmut, trying to contribute to the NAOS community, making the protocol healthy, and hoping to get some additional rewards back.
But his/her transaction can be front-run by those front-running bots on the blockchain, taking away the rewards.
This would be a bad experience for honest users of NAOS.

Do you think this forceTransmute function will expose an MEV opportunity on the blockchain?

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

1 participant