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

IBC transaction gas costs #1923

Closed
Tracked by #2019 ...
sug0 opened this issue Sep 22, 2023 · 2 comments · Fixed by #2091
Closed
Tracked by #2019 ...

IBC transaction gas costs #1923

sug0 opened this issue Sep 22, 2023 · 2 comments · Fixed by #2091

Comments

@sug0
Copy link
Contributor

sug0 commented Sep 22, 2023

Especially after #1904 is merged, IBC transactions will not pay many (if any) gas fees. Updating Namada's state machine with an IBC transaction is somewhat expensive, as validation and storage modifications do the exact same amount of work (i.e. validation is not cheaper, the same code is executed for wasm as is for the native VP).

We should assign a constant gas price to invoking the IBC tx actions host function, and some other cost to executing the IBC native VP. These values should be determined based on the computational effort of running the associated IBC code, with benchmarks.

@sug0
Copy link
Contributor Author

sug0 commented Sep 22, 2023

cc @grarco @yito88 @tzemanovic

@grarco
Copy link
Contributor

grarco commented Sep 22, 2023

Just as a note, I think this pattern should be shared across all native vps given the impossibility of tracking their execution at runtime. If a native vp is computationally expensive (access to storage are already correctly tracked though host functions, so no need to care about them) we should extract the complex part out to a host function to which we can assign a gas cost

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants