svm
svm copied to clipboard
Adopt SHA3 & drop usage of BLAKE3
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.