Ethereum's main fingerprint (hash) function.
The idea: A hash function: any input in, 32 bytes out, with no way back and no known way to find two inputs with the same output. Ethereum uses it to give things short, unforgeable names: your address is part of the hash of your public key, and each block header carries hashes that pin down the entire state.
Why it matters: It creates addresses and seals the entire state of every account.
On the map: collision + preimage resistance
Keccak-256 is Ethereum's main hash function[1, 2]: it derives addresses, roots the state, transaction and receipt tries, and hashes messages before signing. Ethereum adopted it before NIST finalized SHA-3, so it differs slightly in padding from standard SHA3-256[3].
The assumption is that finding collisions or preimages is infeasible. No meaningful attack exists on the full function, and quantum computers only speed up generic attacks.
If any of these breaks, this breaks too.
If this breaks, these break with it.