-
Notifications
You must be signed in to change notification settings - Fork 42
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 Waltz support for CNv0 #223
Comments
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
@Patrickdurbin
Could you please elaborate a bit? In particular, what will prevent Nicehash from implementing CN-GPU in 1-2 month from now? |
This comment was marked as abuse.
This comment was marked as abuse.
There is absolutely nothing that you can do to prevent NiceHash from creating a market for a given coin, but that isn't the issue or even the objective. The issue is that we don't want GRAFT to be vulnerable to 51% attacks that are made easy and cheap via NiceHash, which means either:
Option 2 is actually the better option here: NiceHash does provide a useful tool to allow mining by people without their own mining hardware. Option 1, however, is more likely: it isn't worth NiceHash's time to add an algorithm that only two small coins (GRAFT and RYO) are using. The CN-heavy market has never been a big success, and the CN-light, CN-haven, CN-Masari algorithms never made it to NiceHash at all because, although there are multiple coins on each of them, there just isn't enough hashrate on those coins overall to make it worthwhile. NiceHash is only interested in pursuing big fish, and Graft isn't a big fish. If the GRFT price and hashrate explode and NiceHash decides to open a CN-GPU market, then good: we'll be in option 2 — NiceHash supplements the network hashrate without allowing overwhelming it, which is the ideal place to be. |
Can't agree more. And for this exact reason we want to consider it thoroughly before investing significant engineering time into the merge and, especially, testing. So far, I found somewhat different opinions here: Cryptonight variant 4 aka CryptonightR. A quote:
It seems no-one knows how exactly it behaves. I doubt we have luxury of running into at least a week of development/testing without further investigation. What do you guys think? |
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
@sebseb7 not clear what you mean with it. If it's your proposal for new PoW, thanks, but we would like to get more information about it, cryptographical analysis, stats, comparison with other algorithms. Simple link submitting means nothing. And more likely, we won't spend time investigating it.
@Patrickdurbin, if you asked the Graft Core Team, then no. However, we glad that @sebseb7 (or anyone else) tries to propose something, even if these proposals won't use in the development. |
It is Cuckaroo (from Grin coin’s PoW), hot in cryptoworld, implemented by Seb for CN coins. |
This comment was marked as abuse.
This comment was marked as abuse.
read the whitepaper: https://github.com/tromp/cuckoo/blob/master/doc/cuckoo.pdf |
only grins personal variant of it available on nicehash. Not my variant or other variants. |
floating point for consensous? not a good idea! http://www.yosoygames.com.ar/wp/2013/07/on-floating-point-determinism/ |
I came up with a solution to prevent 51% attacks, but I could not get people to use my product, so I shut it down. You will have the same problems, over and over, as long as you allow 1 pool to hold more than 50% of the traffic. Your currency, like so many others, fails in that regard. Not only do you need to worry about the algo... you also need a way to prevent everyone from bunching up on the same server. |
@randygrolemund, thanks. We'll look at it. However, not for this fork, I think. |
CryptoNight Waltz support for CNv0 needs to be added and tested.
Development team has limited exposure to mining realities right now and believes that active miners are better suited to select the algorithm. We will rely on the miner community to select and test the algorithm (with veto voting power to prevent manipulations.)
For more details see #216
The text was updated successfully, but these errors were encountered: