fix: use hashtree for ssz benchmark

ChainSafe · Jun 12, 2024 · 00f8a99 · 00f8a99
1 parent 321a0e5
commit 00f8a99
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/packages/persistent-merkle-tree/src/hasher/hashtree.ts b/packages/persistent-merkle-tree/src/hasher/hashtree.ts
@@ -53,7 +53,7 @@ export const hasher: Hasher = {
 
       for (const [i, out] of output.entries()) {
         const offset = i * 32;
-        out.applyHash(byteArrayToHashObject(result.slice(offset, offset + 32)));
+        out.applyHash(byteArrayToHashObject(result.subarray(offset, offset + 32)));
       }
     }
   },

diff --git a/setHasher.mjs b/setHasher.mjs
@@ -1,5 +1,5 @@
-// Set the hasher to as-sha256
-// Used to run benchmarks with with visibility into as-sha256 performance, useful for Lodestar
+// Set the hasher to hashtree
+// Used to run benchmarks with with visibility into hashtree performance, useful for Lodestar
 import {setHasher} from "@chainsafe/persistent-merkle-tree/lib/hasher/index.js";
-import {hasher} from "@chainsafe/persistent-merkle-tree/lib/hasher/as-sha256.js";
+import {hasher} from "@chainsafe/persistent-merkle-tree/lib/hasher/hashtree.js";
 setHasher(hasher);