-
Notifications
You must be signed in to change notification settings - Fork 212
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
Unknown error while processing xDai -> ETH transfer #239
Comments
It seems that the issue is due to this piece of the code: It initialize the array only with one element. We see later in the log only one message when getting the signatures:
and one log message when verify the signatures:
|
If this functionality is rolled back to
the signatures are collected correctly and the withdrawal request is completed successfully. |
The reason why the following code was not working is because of how the Array constructor works const requiredSignatures = new Array(NumberOfCollectedSignatures).fill(0) From the docs: A JavaScript array is initialized with the given elements, except in the case where a single argument is passed to the Array constructor and that argument is a number in this case it returns a new JavaScript array with its length property set to that number. new Array(3) // [,,]
new Array('3') // ['3'] In our code, In our previous code, internally it was correctly parsing the string to number when assigning the value to the length property requiredSignatures.length = NumberOfCollectedSignatures |
Thanks Gerardo! So, it means that we have one more vote for having #63 to be addressed. With an e2e test when several validators are involved this behavior could be caught. Is this correct? |
Exactly, an e2e test with several validators would expose this incorrect behavior |
Today one more validator node was upgraded to the new version of oracle and it seems we have an error processing xDai -> ETH transactions.
I did a test with this tx: https://blockscout.com/poa/xdai/tx/0x79bc2884e340d7f7791e3296cc8da7bf4ef3ff6dcaacf8ef87f91fa7f1387965/internal_transactions
And it doesn't seem to be working because of an error during gas estimation:
Here is the .env file from the oracle
The text was updated successfully, but these errors were encountered: