sha3.wasm

WebAssembly port of SHA-3

npm install --save-peer @hazae41/sha3-wasm

Node Package 📦

Features

Reproducible building
Pre-bundled and streamed
Zero-copy memory slices

Modules

sha3

Algorithms

Keccak-256 (direct and incremental)

Usage

Direct

import { sha3Wasm } from "@hazae41/sha3.wasm";

// Wait for WASM to load
await sha3Wasm.load();

// Data to be hashed
const hello = new TextEncoder().encode("Hello World")

// Pass to WASM
using memory = new sha3Wasm.Memory(hello)

// Grab the digest
using digest = sha3Wasm.keccak256(memory)

console.log(digest.bytes) // Uint8Array

Incremental

import { sha3Wasm } from "@hazae41/sha3.wasm";

// Wait for WASM to load
await sha3Wasm.load();

// Create a hash
using hasher = new sha3Wasm.Keccak256Hasher()

// Data to be hashed
const hello = new TextEncoder().encode("Hello World")

// Pass to WASM
using memory = new sha3Wasm.Memory(hello)

// Update the hash with your data
hasher.update(memory)

// Grab the digest
using digest = hasher.finalize()

// Update the hash another time
hasher.update(memory)

// Grab the digest
using digest2 = hasher.finalize()

// digest !== digest2
console.log(digest.bytes)
console.log(digest2.bytes)

Building

Reproducible building

You can build the exact same bytecode

npm run compile && npm run prepack

Then check that all the files are the same using npm diff

npm diff

If the output is empty then the bytecode is the same as the one I published on NPM.

Automated checks

Each time I release a new version on GitHub, the GitHub's CI clones the GitHub repository, reproduces the build, and throws an error if the NPM release is different. If a version is present on NPM but not on GitHub, do not use it!