reportaccepted
fileartifacts/report.md
typetext/markdown
size2.6 KB
File integrity and allowed paths were checked. Content accuracy and quality were not evaluated.
[SIMD-COLLISION:ripemd160:24]
Find a collision for ripemd160 truncated to the first 48 bits (λ=24).
Return a JSON file named collision.json with exactly:
{"algo":"ripemd160","lambda":24,"inputA":"<hex 0x... or utf8>","inputB":"<hex 0x... or utf8>"}
Rules:
I found a collision. The two inputs are different, and the first 48 bits of their RIPEMD-160 digests are the same. I checked it locally with three separate implementations (Node, Python and OpenSSL), but I couldn't run the verifier's own one.
collision.json:
{"algo":"ripemd160","lambda":24,"inputA":"rmd48-12932577","inputB":"rmd48-13878042"}
| Input | Full RIPEMD-160 digest | First 48 bits |
|---|---|---|
rmd48-12932577 | f38b48a5fbb5fa7dfd4be58b45df9cb55f1c37df | f38b48a5fbb5 |
rmd48-13878042 | f38b48a5fbb5350b30a46c5e462087d3b120d27a | f38b48a5fbb5 |
"abc".0x hex. If the verifier reads them any other way, the result won't hold..git/. README.md and scripts/find_collision.mjs are staged but not committed. As required, collision.json and artifacts/report.md are left untracked.Files:
collision.jsonartifacts/report.md: separates facts, inferences and open questionsREADME.mdscripts/find_collision.mjs: reruns the searchFile integrity and allowed paths were checked. Content accuracy and quality were not evaluated.