-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cryptonight algo tweak/ ASIC resistant algo #91
Comments
Supposedly I've heard that integer division is slow on ASICs. Also, I've heard that operations on big numbers (arbitrary sized integers) is also slow. One idea could be to divide the final result by some large scalar. This would also slow down GPUs, but in the case of GPUs a miner could simply batch up several results and do the final step on the CPU. It's likely my idea is either insane or requires a lot of tweaks, but here it is. |
Thanks Phillip! |
A little tech background of the little data we have: Baikal Giant N: 20 KH/s @ 60 W - $3600.
Now, CN was thought to resist ASICs by being memory-intensive (the scratchpad, about 2 MB if i'm correct and 1 MB for lite). Another solution as proposed before is using divisions. |
What would be your estimate as to how many dividers can be ran in parallel on a decent FPGA (signed division, 64 bit dividend / 32 bit divisor)? |
@curie-kief That size isn't in xilinx's spec sheet, however let's take the most approximate one. |
One more question. If we assume that the devices are using only on-chip memory, what's ballpark number that they can have available? |
Smallest starts at 1.5 MB and the top model gets up to 9.5 MB. Keep in mind that a top model price is 5 digits. |
Is there a graph or something somewhere that shows the price/mb relationship? |
I think Madame Curie :) was creating one last night. |
You can use a parts supplier, start at https://www.digikey.com/products/en/integrated-circuits-ics/embedded-fpgas-field-programmable-gate-array/696 |
Just do a multi-algorithm approach like x16r. |
Might it not be a good idea to then create a full blown mini-VM like bf if we go that route? |
Madame curie ( @curie-kief ) will be pushing within the next couple of days (hopefully within the weekend). |
Consider some way to let Algorithm/Protocol to be changed automatically every month/season? Also, Need to let Wallet/Pool/Mining software supported. Could add into Roadmap by serval steps, then the ASICs will not able to follow up. |
Hopefully the new algo being built will keep ASICs away for a couple of years (they always catch up eventually) so no need to fork periodically. Wallet, pool and mining software will of course be released before the fork. |
Is the difficulty algorithm going to be upgraded in the fork? I have another issue that is open here and that recommends my algorithm that a lot of Monero clones are going to. |
Since the need to fork to an asic resistant algo seems to be the only way to go atm, I am opening this for suggestions and discussion.
An integer division step is tried to be included but it seems to be killing GPUs as well.
The text was updated successfully, but these errors were encountered: