Bitcoin Forum
May 05, 2024, 12:17:01 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: New algo to combat Nicehash  (Read 349 times)
butmuncher (OP)
Full Member
***
Offline Offline

Activity: 154
Merit: 100


View Profile
November 15, 2017, 08:36:53 AM
Last edit: November 15, 2017, 09:05:19 AM by butmuncher
 #1

Last few month I've noticed bad tactics from nice hash, we all Know what they do.
They pile on the coin, destroy the difficulty , take all the coins and then cut back on hash till difficulty levels lower.

So gpu mining  algo  gets updates to make sure asics can't mine.

Well why isn't the same thing as Asic  protection happening with Nice hash. ?

Nice hash in its current form can be classed as hostile due to the way it works and it needs Tobe changed as with asics , nice hash has a unfair advantage which makes mining along side it unfair, hence why I call it hostile.

DKqZzd1CRBEy4sMgbHV7NR3toaY72UMXuC DIXIHUB
1714868221
Hero Member
*
Offline Offline

Posts: 1714868221

View Profile Personal Message (Offline)

Ignore
1714868221
Reply with quote  #2

1714868221
Report to moderator
1714868221
Hero Member
*
Offline Offline

Posts: 1714868221

View Profile Personal Message (Offline)

Ignore
1714868221
Reply with quote  #2

1714868221
Report to moderator
1714868221
Hero Member
*
Offline Offline

Posts: 1714868221

View Profile Personal Message (Offline)

Ignore
1714868221
Reply with quote  #2

1714868221
Report to moderator
The block chain is the main innovation of Bitcoin. It is the first distributed timestamping system.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714868221
Hero Member
*
Offline Offline

Posts: 1714868221

View Profile Personal Message (Offline)

Ignore
1714868221
Reply with quote  #2

1714868221
Report to moderator
bathrobehero
Legendary
*
Offline Offline

Activity: 2002
Merit: 1051


ICO? Not even once.


View Profile
November 15, 2017, 11:46:11 AM
 #2

Last few month I've noticed bad tactics from nice hash, we all Know what they do.
They pile on the coin, destroy the difficulty , take all the coins and then cut back on hash till difficulty levels lower.

So gpu mining  algo  gets updates to make sure asics can't mine.

Well why isn't the same thing as Asic  protection happening with Nice hash. ?

Nice hash in its current form can be classed as hostile due to the way it works and it needs Tobe changed as with asics , nice hash has a unfair advantage which makes mining along side it unfair, hence why I call it hostile.

Because it's trivially easy to implement support for a new algo on their pools.

Unfortunately, there isn't a solution that would prevent coins to be mined by pools. If a coin would come along that can only be solomined, that would be great but it can't be done as far as I know. Spreadcoin tried but ocminer proved them wrong because he managed to make it work on a pool.


Not your keys, not your coins!
ivakar
Hero Member
*****
Offline Offline

Activity: 756
Merit: 507



View Profile
November 15, 2017, 12:13:20 PM
 #3

Last few month I've noticed bad tactics from nice hash, we all Know what they do.
They pile on the coin, destroy the difficulty , take all the coins and then cut back on hash till difficulty levels lower.

So gpu mining  algo  gets updates to make sure asics can't mine.

Well why isn't the same thing as Asic  protection happening with Nice hash. ?

Nice hash in its current form can be classed as hostile due to the way it works and it needs Tobe changed as with asics , nice hash has a unfair advantage which makes mining along side it unfair, hence why I call it hostile.

Sometimes you can use Nicehash for good, if used wit caution
but sometimes someone stupid put the crazy order which send the diff right to the Moon
And best we can do - switch to another coin for such moments
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!