Quote from: ripemdhash on Today at 07:41:39 PM

1NqyFopy2LAghcL4o5xjiuSaRFo3KoPNSo - after hash160 -> c51b66bced5e4491001bd702669770dccf440982
1GVXnKbEbcuUAB6iF2dvgVTUKQwpZ2NpUk - after hash160 -> c51b66bced5e4491001bd702669770dccf440982
1LRhnNWHoAfLjVZe51XXMYCuBJmvPvE1sE - after hash160 -> c51b66bced5e4491001bd702669770dccf440982

I am not sure what you wanted to show, but it completely makes no sense for me. Could you explain step by step?

Quote from: ripemdhash on Today at 03:16:04 PM

I am a new user of this forum. However, before registering, I have been reading various posts related to technical issues for a long time. I'm very curious if anyone has managed to find a collision in RIPEMD160 on Bitcoin addresses. Are there any known collision data with public keys, and if possible, with private keys as well?

Some scientific progress has been made (https://eprint.iacr.org/2023/285) but it is still very far from a simple every-day use. In other words - RIPEMD160 is still secure.