Similar names do not make two digest algorithms interchangeable.
LET’S PICTURE IT
Two machines can belong to the same family while using different settings.
SEE IT FOR YOURSELF
From exact bytes to a Keccak-256 fingerprintStep 1 / 4
The text hello is a particular sequence of characters. Case or text normalization can change the encoded bytes.
The text hello is a particular sequence of characters. Case or text normalization can change the encoded bytes.UTF-8 hello is the five-byte sequence 68 65 6c 6c 6f. The 0x prefix is display notation.The algorithm maps the input to a fixed thirty-two-byte output. This is a fingerprint operation, not reversible encryption.For hello, the digest begins 1c8aff95 and ends 36deac8. The local hash tool displays the complete result and lets you edit the input.
Animated local teaching model. No wallet, RPC or live blockchain data. Some labels and hashes are abbreviated for readability.
Name the required algorithm
Many Ethereum conventions use Keccak-256. Finalized SHA3-256 differs in domain-padding details, so selecting it solely because the name looks familiar gives a different result.
Compare identical payload bytes
Use the exact UTF-8 bytes of hello in both algorithms. A fair comparison changes the algorithm while keeping the input encoding fixed.
Connect the difference to interfaces
A function selector or event signature calculated with the wrong digest will not match the intended Ethereum convention, even if the canonical signature text is correct.
Use explicit library functions
Choose an implementation that names the required variant clearly. Record both algorithm and input bytes in test fixtures instead of documenting only a generic hash function.