Ok was just asking as I have never heard of that before. Is there a special reason why you decided to go with that algorithm for your coin?
Cryply - CPU only coin
then we need CPU algo
yescrypt - cpu algo but Claus make miner for this algo...
Now you can mine with GPU another cpu coins like yenten elicoin etc
As for you, how mach time need to made GPU miner for this algo and how profit it will be.
A huge amount of time and effort will go into writing such a miner for video cards. And the result will be almost zero. Video cards will earn very few coins.
Aren't video cards much stronger in mining than most CPUs? I thought they always produce a higher hash rate.
The uniqueness of YesPoWer's algorithm is that video cards are very difficult to give out more than the weakest processor.
The cryply. team is sure that the video cards will never get coins, and with the arrival of the asik miners the network is waiting for an immediate hard fork
You say it is very difficult, but if a good programmer invests a lot of time would it be possible to come up with a mining program that is efficient for GPUs?
good programmer can't make any free software I think)
maybe small module of software
this is take a lot of time
for explain - you can check github repos
many repos don't working without sex
lol
Without sex? I doubt I understand what you are talking about but the strong developers in this space have a lot of power due to their knowledge and they could build mining software for some coins.
Changes in YesPoWer version 1.0 is not only a requirement for RAM.
In these five points, the basis for protection from video cards
1. Now we use 96 KiB S-boxes instead of 128 KiB (and both -
in total). The number of S-boxes increased from 2 to 3, in the same way as in
yescrypt 1.0. This made it possible to eliminate the drop in speed at
two-socket servers.
2. The number of records in the S-box'y doubled.
3. Entries in S-boxes are distributed so that the need for speculative
implementation and possible re-execution, or in a preliminary
verification, arose 8 times more often than before. (On the CPU this is implemented
hardware, and with parallel implementation on the GPU will be required
additional instructions)
4. The use of Salsa20 and
SHA-256 (which almost did not give anything to protect from the GPU, but needed for
guarantee of cryptographic properties of the whole scheme as a whole).
5. The implementation uses a different approach for combining the two versions
algorithm, with the specialization code separately for each. (Outside this is not
noticeably, the API remained the same.)
Without sex? - It means that many applications of github do not work out of the box. And they require a serious revision of the code when starting
