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
L1 fees for optimism communities call #14166
Comments
I am a bot confused by the fees for Optimism. Eg. when I try to airdrop a token I have following estimations:
After the operation I check etherscan and I see this: I see some discrepancy with baseFee. Also I can't find l1 fee anwhere (or anything similar). Any idea @saledjenic |
…tions There is only one status-go call for all fees: suggested fees, gas and l1 fee. Issue #14166
@endulab yes, I've noticed the same, like L1 fee estimation is 100 times higher in magnitude than the real L1 fee for a tx placed on L2, not sure why it's like that, but that's the value we're getting from the network. |
…tions There is only one status-go call for all fees: suggested fees, gas and l1 fee. Issue #14166
…tions There is only one status-go call for all fees: suggested fees, gas and l1 fee. Issue #14166
…tions There is only one status-go call for all fees: suggested fees, gas and l1 fee. Issue #14166
Following up on:
status-im/status-go#4923
L1 fees needs to also be computed for all transaction done by communities.
Suggestion:
on top of function likes:
Create functions likes:
For the body of this function, check the above PR, it should be:
1 - build the tx
2 - call the oracle contract via the fees manager.
Which will compute L1 fees.
The L1 fees needs to be added to the fees
The text was updated successfully, but these errors were encountered: