Is there any limit to the length of the string after which hashing should be avoided. Also can the hashing solutions be easily hacked in contests ?
| № | Пользователь | Рейтинг |
|---|---|---|
| 1 | Benq | 3676 |
| 2 | jiangly | 3670 |
| 3 | Kevin114514 | 3657 |
| 4 | maroonrk | 3355 |
| 5 | Um_nik | 3353 |
| 6 | squareOf105 | 3346 |
| 7 | tourist | 3343 |
| 8 | strapple | 3324 |
| 9 | heuristica | 3322 |
| 10 | jiangbowen | 3291 |
| Страны | Города | Организации | Всё → |
| № | Пользователь | Вклад |
|---|---|---|
| 1 | Qingyu | 158 |
| 2 | nik_exists | 150 |
| 2 | maspy | 150 |
| 4 | AmShZ | 144 |
| 5 | Um_nik | 141 |
| 6 | Errichto | 139 |
| 7 | adamant | 137 |
| 8 | BledDest | 134 |
| 9 | maroonrk | 133 |
| 10 | qwexd | 130 |
Is there any limit to the length of the string after which hashing should be avoided. Also can the hashing solutions be easily hacked in contests ?
| Название |
|---|



According to the birthday paradox, if m = 1e9 + 9, we can random about 200000 strings and the possibility of collisions is more than 99.9999%!
Simple code can calculate the possibility:
Also, if you want to make your hashing become hard to hack, there are two possible choice:
use a long long prime as m
use two or more hash functions
Sorry for my poor English, I hope this can help you:)
Well, that might make it a bit harder to hack, but still hackable. You should also make your base randomized.