nodejs-keccak256

Node.js crypto.createHash('sha3-256') uses the NIST SHA3 standard, not Ethereum's Keccak-256, causing silent hashing mismatches in function selectors and signatures. You must use Keccak-256-aware libraries like ethers, viem, or web3 instead to ensure correct Ethereum compatibility.

Keccak-256 is the original hashing algorithm adopted by Ethereum, while SHA3-256 is a NIST-standardized variant with different padding. Using Node's crypto.createHash('sha3-256') produces incorrect hashes for Ethereum data like event topics and storage slot derivations.

To correctly generate Keccak-256 hashes in TypeScript, use Ethereum-aware libraries such as ethers, viem, or web3 instead of Node's built-in crypto module. These libraries implement the correct Keccak-256 algorithm for Ethereum function selectors, event topics, and address derivations.

No, the Node.js crypto module does not work for Ethereum address generation because its sha3-256 implementation differs from Ethereum's Keccak-256. Using it leads to incorrect address derivations; you should use ethers, viem, or web3 libraries to ensure proper Keccak-256 hashing.

You need to avoid Node's sha3-256 whenever performing Ethereum-specific hashing tasks such as deriving function selectors, event topics, signatures, Merkle proofs, or storage slots. Always use Keccak-256-aware libraries like ethers or viem to prevent silent hashing bugs in JS/TS projects.

Yes, you can use viem or web3 for Keccak-256 hashing as they correctly implement Ethereum's Keccak-256 standard. Any of these three libraries properly handles Ethereum hashing tasks like function selectors and address generation, whereas Node's crypto.createHash does not.