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.

Sign up for GitHub

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

Jump to bottom

Add BLAKE2b support to the Math API #3953

Closed
artob opened this issue Feb 12, 2021 · 0 comments
Closed

Add BLAKE2b support to the Math API #3953

artob opened this issue Feb 12, 2021 · 0 comments
Labels
A-cryptography Area: Cryptography A-EVM Area: Native EVM implementation and support A-transaction-runtime Area: transaction runtime (transaction and receipts processing, state transition, etc) C-enhancement Category: An issue proposing an enhancement or a PR with one. T-Aurora Team: issues relevant to the Aurora team

Comments

@artob
Copy link
Contributor

artob commented Feb 12, 2021 •
edited
Loading

To speed up and lower the cost of the EVM-as-a-contract implementation, we will need to add blake2b() as a Math API primitive so that the EVM contract itself will not need to implement this hash function.

References:
@artob artob added A-cryptography Area: Cryptography C-enhancement Category: An issue proposing an enhancement or a PR with one. A-EVM Area: Native EVM implementation and support T-public-interfaces Team: issues relevant to the public interfaces team A-transaction-runtime Area: transaction runtime (transaction and receipts processing, state transition, etc) labels Feb 12, 2021
@artob artob mentioned this issue Feb 12, 2021
Closed
@bowenwang1996 bowenwang1996 added T-core Team: issues relevant to the core team T-contract-runtime Team: issues relevant to the contract runtime team T-Aurora Team: issues relevant to the Aurora team and removed T-public-interfaces Team: issues relevant to the public interfaces team T-contract-runtime Team: issues relevant to the contract runtime team T-core Team: issues relevant to the core team labels Jun 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-cryptography Area: Cryptography A-EVM Area: Native EVM implementation and support A-transaction-runtime Area: transaction runtime (transaction and receipts processing, state transition, etc) C-enhancement Category: An issue proposing an enhancement or a PR with one. T-Aurora Team: issues relevant to the Aurora team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@artob @joshuajbouw @bowenwang1996