Post
Topic
Board Development & Technical Discussion
Re: Pollard's kangaroo ECDLP solver
by
HardwareCollector
on 30/05/2020, 16:20:39 UTC
How did you manage to get it down to 16 bytes per point?
@BitCrack

I am storing only 8bytes of the x-coordinate and lookup information (8bytes with HT overhead included) on how to retrieve the rest of the information in the event of a collision. This is accomplish by using a custom version of Google’s Sparse_Hash_Set in a distributed setup. The cost is network bandwidth but all clients are on a 1 GigE network.

 https://github.com/sparsehash/sparsehash