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

Optimize gas usage in ecpair precompile #46

Open
birchmd opened this issue Apr 28, 2021 · 2 comments · Fixed by #540
Open

Optimize gas usage in ecpair precompile #46

birchmd opened this issue Apr 28, 2021 · 2 comments · Fixed by #540
Labels
C-bug Category: Something isn't working. C-enhancement Category: New feature or request

Comments

@birchmd
Copy link
Member

birchmd commented Apr 28, 2021

Currently the ecpair precompile cannot be executed because it uses up more than 200 Tgas by itself. The purpose of this issue is to get this number down so that it becomes usable.

See #41 for information about measuring gas usage in pre-compiles.

@birchmd birchmd added C-bug Category: Something isn't working. C-enhancement Category: New feature or request labels Apr 28, 2021
@joshuajbouw
Copy link
Contributor

Considering that the backend is widely used and regarded, and when I went through it was quite straight forward, I worry that this may be an issue until Math API is pulled in near/nearcore#3954.

@birchmd
Copy link
Member Author

birchmd commented Sep 14, 2021

The ecpair precompile was not included in any performance improvement at the nearcore level. It still does not work because it consumes too much NEAR gas. The test_ecpair function in our standard_precompiles contract currently takes almost 2000 Tgas (that's not a typo, I really mean two-thousand teragas!).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: Something isn't working. C-enhancement Category: New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants