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

FinalizedWithdrawRequest confusing semantics #219

Open
jac18281828 opened this issue Apr 12, 2024 · 1 comment
Open

FinalizedWithdrawRequest confusing semantics #219

jac18281828 opened this issue Apr 12, 2024 · 1 comment
Labels
low low priority

Comments

@jac18281828
Copy link
Contributor

there are multiple withdrawal settlement/finalization IDs, and there is enough ETH in the contract for the finalizations to take place. However, when we run the job, only one finalization (ID) is settled, the rest remain in the same status. Our understanding is that if there is enough ETH, all the IDs should have been settled.

The issue appears to be with the below referenced code. The finalization is somewhat confusing because each finalized Id is not reported. The FinalizedWithdrawRequest(uint) event indicates the highest requestId plus 1 that was finalized. It would make sense to report each requestId that has been finalized. It appears that the finalization is working properly but this ticket indicates that the implementation is confusing.

if (requestId > nextRequestIdToFinalize) {

@jac18281828
Copy link
Contributor Author

@vagpm 👀

@jac18281828 jac18281828 added the low low priority label Apr 12, 2024
@jac18281828 jac18281828 changed the title finalization id investigation FinalizedWithdrawRequest confusing semantics Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low low priority
Projects
None yet
Development

No branches or pull requests

1 participant