Topic: Tecra is thinking about changing the hashing algorithm (Read 114 times)
We've got an exchange. Smaller, but it is https://stakecenter.co/client/exchange/BTC/TCR
Will the hashing function used on address/transaction generation or as mining (Proof of Work)? If it's used as mining and you wish to build "ASIC-resistant algorithm", you better use another method such as ProgPoW.
In general our changes in hash function impacts the first one - address/transaction not mining algorithmUnfortunately i don't know much about hash function for address/transaction generation, you should contact cryptography expert about it.
Will the hashing function used on address/transaction generation or as mining (Proof of Work)? If it's used as mining and you wish to build "ASIC-resistant algorithm", you better use another method such as ProgPoW.
In general our changes in hash function impacts the first one - address/transaction not mining algorithmWill the hashing function used on address/transaction generation or as mining (Proof of Work)? If it's used as mining and you wish to build "ASIC-resistant algorithm", you better use another method such as ProgPoW.
In general our changes in hash function impacts the first one - address/transaction not mining algorithmWill the hashing function used on address/transaction generation or as mining (Proof of Work)? If it's used as mining and you wish to build "ASIC-resistant algorithm", you better use another method such as ProgPoW.
In general our changes in hash function impacts the first one - address/transaction not mining algorithm I believe blake2 is good to be crunched on FPGAs. Would you please use some CPU-only algo like RandomX-family or Minotaur?
Functions are used in many places in blockchain and these functions are different. When it comes to the changes we are doing, they mainly affect the way merkle tree root is counted. Mining algo - the hash function is also calculated there, but from the block. So these are two different places. 
I believe blake2 is good to be crunched on FPGAs. Would you please use some CPU-only algo like RandomX-family or Minotaur?
It is very important for us to develop and improve our Blockchain, so we are thinking about changing the hashing algorithm from SHA256 to BLAKE2B.
As we know, in 2020, almost all computers use 64-bit processors. In turn, our hashing BLAKE2b (or just BLAKE2) is optimized for 64-bit platforms—including NEON-enabled ARMs—and produces digests of any size between 1 and 64 bytes BLAKE2 has been adopted by many projects due to its high speed, security, and simplicity.
What do you think about our changes? Is this a good idea?
Jump to: