-
Notifications
You must be signed in to change notification settings - Fork 37
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
Find a suitable ASIC resistant hashing algo #18
Comments
Some of the altcoins achieve this by using algorithms that use a lot of memory. Most of the ASIC machines will not have high memory thus making the hashing algorithm ASIC resistant. |
Would you like to self-assign this and try to find a few algorithms we might be able to use (keeping in mind that we'd prefer to use an elixir/erlang library)? |
Just a thought : Instead of using one algorithm, can't we change the algorithm for each block based on some criteria. No ASIC machine can be configured to work for multiple algorithm(But a CPU can, that is what makes it general purpose). So people with ASIC can mine a selected number of blocks but never makes mining centralized to only ASIC machines. |
I think thats an interesting idea, but in practice it would br difficult to enforce, since consensus depends partially on nodes being able to identify which algorithm is used, and it would also make block time wildly unpredictable, since each algorithm has different speeds and efficiencies (plus each gpu has a different performance based on the algorithm thats used) so there wouldn't be much incentive for a miner if they can't predict roughly how likely they are to find the next hash |
https://steemit.com/cryptocurrency/@buggedout/asic-resistance-is-a-myth-dash-is-conquered |
Attaching a c library containing SHA3 and a lot of other algorithms. |
Currently we're using SHA256 for the block hashes. While this is fine and secure, in the interest of leveling the playing field for miners, lets find a good ASIC-resistant hashing algorithm to use instead.
The text was updated successfully, but these errors were encountered: