Skip to content
This repository was archived by the owner on Aug 14, 2023. It is now read-only.

Adopt SHA3 & drop usage of BLAKE3 #495

Open
neysofu opened this issue Feb 16, 2022 · 0 comments
Open

Adopt SHA3 & drop usage of BLAKE3 #495

neysofu opened this issue Feb 16, 2022 · 0 comments
Labels
good first issue Good for newcomers small Small-sized task svm

Comments

@neysofu
Copy link
Contributor

neysofu commented Feb 16, 2022

SVM currently uses BLAKE3 in all places where we need a cryptographic hash function. I believe go-spacemesh uses SHA3, which is quite a bit slower but probably fast enough for our needs. I suggest replacing BLAKE3 with SHA3 everywhere within the SVM so that both the node and SVM can perform account and template address computation using SHA3.
@neysofu neysofu changed the title Settle on a single hash function Adopt SHA3 & drop usage of BLAKE3 Feb 16, 2022
@neysofu neysofu added good first issue Good for newcomers small Small-sized task svm labels Feb 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
good first issue Good for newcomers small Small-sized task svm
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@neysofu