-
Notifications
You must be signed in to change notification settings - Fork 249
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
chore(wallet)_: include l1 fees info (for the tx and approval) in the response #6271
base: develop
Are you sure you want to change the base?
Conversation
Initiative for this PR is coming from this comment status-im/status-mobile#21876 (comment) |
Jenkins BuildsClick to see older builds (19)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have u confirmed the value makes sense?
I did not. Expect people from the mobile team to check and respond to that. |
@saledjenic thank you for the PR. Could you please check the ISSUE 1 identified in corresponding mobile PR? |
67b8da3
to
214e425
Compare
@pavloburykh could you try again now? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changes look good, waiting for confirmation that the values actually make sense
thank you @saledjenic! @VolodLytvynenko will be able to pick it up tomorrow, as I will be off. Also, I see some builds failed in this PR, is it related to changes of some infra issues? |
Should not be up to the changes here, something must be stuck, will push again later and see. |
214e425
to
39ed123
Compare
@antdanchenko could you please help on this, cause functional tests must be failing due to missing |
… response While ago we've disabled l1 info cause the estimated L1 fees were significantly higher than they should have been (if I remember well, the L1 fees were about 1000 times higher than they should have been). From this point, that wrong value might be coming from unreliable pokt calls/values, these changes bring them back.
39ed123
to
3a81b49
Compare
A while ago we disabled l1 info cause the estimated L1 fees were significantly higher than they should have been (if I remember well, the L1 fees were about 1000 times higher than they should have been).
From this point, that wrong value might be coming from unreliable pokt calls/values, these changes bring them back.