Post
Topic
Board Development & Technical Discussion
Re: Pollard's kangaroo ECDLP solver
by
WanderingPhilospher
on 02/06/2020, 20:58:10 UTC
I am working on pool to solve keys together.
It is shema how it should be:
http://i.piccy.info/i9/fc3ed817604b01fcce2f1ac851f6a2fa/1591129885/6039/1371731/Untitled_1_240.jpghttp://i.piccy.info/a3/2020-06-02-20-31/i9-13837466/240x135-r/i.gif

HelpServer and HelpClient needed to map each DP to a specific account.
As you can see in the next picture each sent DP is added to a specific account.

http://i.piccy.info/i9/1da6686eea62ecca51d891638ee52f8f/1591129917/8762/1371731/Untitled_2_240.jpghttp://i.piccy.info/a3/2020-06-02-20-31/i9-13837467/240x156-r/i.gif

So far, the biggest problem is the verification of DP. The CPU is not able to check every DP, it simply does not have enough resources for this.
As an option, in order to prevent forged DPs, HelpServer can check a few percent of the sent.
And send to the ban if the client sends the wrong points.
Maybe someone knows how to easily and effectively check points, because multiplying the distance by G is a resource-intensive process.


So is it a matter of let's say my equipment sending bad data, or me manipulating data? If it's because people may manipulate the DP data, only allow people you trust. ?