Skip to content
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

Monero v7 PoW change status #434

Closed
10 tasks done
xmrig opened this issue Mar 8, 2018 · 38 comments
Closed
10 tasks done

Monero v7 PoW change status #434

xmrig opened this issue Mar 8, 2018 · 38 comments
Assignees

Comments

@xmrig
Copy link
Owner

xmrig commented Mar 8, 2018

Monero will change PoW on April 6, that means Monero cryptonight will not compatible with other cryptonight based coins. Also small hashrate drop expected.

You will require update miners to continue mine Monero. As soon as version 2.5 released you can update miners don't need do it on April 6, new version fully compatible with current Monero network.

New miner also can be continue use with other cryptonight coins without changes, I checked ETN, SUMO and ITNS. If you get compatible issues please report it, also you have 2 ways to disable new algorithm:

  1. Use new option "variant": 0 or --variant 0 on each pool. Example:
        {
            "url": "YOUR_POOL:3333",
            "user": "YOUR_WALLET",
            "pass": "x",
            "keepalive": true,
            "nicehash": false,
            "variant": 0
        },
  1. Use xmrig-proxy to override variant option, in proxy config for each pool set variant option. This option will be supported in proxy v2.5, this version currently available in dev branch. Example:
        {
            "url": "YOUR_POOL:3333",
            "user": "YOUR_WALLET",
            "pass": "x",
            "coin": "SUMO",
            "variant": 0
        },

Current progress:

@xmrig xmrig self-assigned this Mar 8, 2018
@Umiiii
Copy link

Umiiii commented Mar 9, 2018

Is that means when I use xmrig and xmrig-proxy v2.5 before March 28 and it will automatically changed its mining strategy when March 28 Monero hard fork come and after that?

@xmrig
Copy link
Owner Author

xmrig commented Mar 9, 2018

That right, xmrig v2.5 will work before and after hard fork without changes, algorithm will change automatically no need do anything. Actually proxy update is not mandatory, old version continue work, but in v2.5 many new features added.
Thank you.

@2010phenix
Copy link

and that all be nice.... i think need some love and to classic C miner too ;)

@xmrig
Copy link
Owner Author

xmrig commented Mar 9, 2018

Added classic miner to checklist.
Thank you.

@xmrig xmrig mentioned this issue Mar 11, 2018
22 tasks
@xmrig
Copy link
Owner Author

xmrig commented Mar 11, 2018

Monero v7 implemented in all miners (in dev branches currently) and in classic C miner (classic branch).

@xmrig
Copy link
Owner Author

xmrig commented Mar 12, 2018

Release delayed, AEON will change PoW too #426
Thank you.

@xmrig
Copy link
Owner Author

xmrig commented Mar 12, 2018

Instead of option monero will be added more flexible option variant.
Possible values:

  • -1 Autodetect, should work fine with Monero, AEON and others coins until their network not updated to v7. Used by default.
  • 0 Force use original cryptonight algorithm.
  • 1 Force use new Monero v1 PoW.

Please note, this option applied on each pool separately. When use xmrig-proxy, miner can switch between 0 and 1 on each job.

@tarris034
Copy link

How often will the new version check which algo to use ? on every work ? what will be the overhead of this checking procedure ? will it have impact on the hashrate ?

@xmrig
Copy link
Owner Author

xmrig commented Mar 13, 2018

Depends of miner, on each platform checking is different, but overhead for this is near zero. When use old algorithm hashrate should be same as before. But new algorithm itself is a few % slower.
Thank you.

@jsonnentag
Copy link

Will mining for MoneroV option be added as well?

@xmrig
Copy link
Owner Author

xmrig commented Mar 14, 2018

I don't know what will be use MoneroV, it they will use new PoW with same version with Monero, anything should work fine.
Thank you.

@xmrig
Copy link
Owner Author

xmrig commented Mar 14, 2018

GRAFT already use v7 network, but original algorithm, so you must use option "variant": 0 on each GRAFT pool. Algorithm detection will not work with this coin.

Example:

{
    "url": "pool.graft.hashvault.pro:7777",
    "user": "WALLET_ADDRESS",
    "pass": "x",
    "keepalive": true,
    "nicehash": false,
    "variant": 0
},

@xmrig xmrig mentioned this issue Mar 14, 2018
@serisman
Copy link

Can you build/push a new version of your docker image (https://hub.docker.com/r/xmrig/xmrig/) that contains these changes?

@xmrig
Copy link
Owner Author

xmrig commented Mar 14, 2018

It not my docker image, I'm not related to https://hub.docker.com/r/xmrig/ in any way.
Thank you.

@serisman
Copy link

Interesting. Thanks for the reply. I assumed it was yours based on the name. I'll look around for a suitable replacement or create one.

@sebseb7
Copy link

sebseb7 commented Mar 15, 2018

it there a v7 testpool already?

@xmrig
Copy link
Owner Author

xmrig commented Mar 15, 2018

http://killallasics.moneroworld.com/

@sebseb7
Copy link

sebseb7 commented Mar 15, 2018

and is there a testnet with v7 also?

@sterkederk
Copy link

On testpool mining works, but my hashrate dropped by half?

@xmrig
Copy link
Owner Author

xmrig commented Mar 15, 2018

@sebseb7 Not sure, latest Monero daemon was use v8 when I last check it, mentioned pool use v7.
@sterkederk Please open separated issue with proper details about your hardware, old and new hashrate.
Thank you.

@oliverw
Copy link

oliverw commented Mar 15, 2018

@xmrig May I ask where you got the information about the necessary changes to the PoW algorithm to support V7?

@xmrig
Copy link
Owner Author

xmrig commented Mar 15, 2018

Reference implementation was submitted by @vtnerd via pull request #426
Thank you.

@oliverw
Copy link

oliverw commented Mar 15, 2018

@xmrig Thanks a lot!

@2010phenix
Copy link

@xmrig thx for some love to classic one...
Implement changes in classic xmrig (C version).

they to have autodetect V7 version already or only first version support from Mar 11?

@xmrig
Copy link
Owner Author

xmrig commented Mar 15, 2018

Since this commit 3394459 V7 supported, autodetect work too.

@guigeddos
Copy link

@xmrig Why some of them have 2 CPU. Xmrig can only recognize and read 1 CPU. How to solve this. Stak mining tools can be identified. But xmrig can't recognize it. There are a lot of problems. Is there a way to solve it

@nssy
Copy link

nssy commented Mar 16, 2018

Works fine for me on the testpool. No noticeable change in Hash Rate. Thanks for patching things up early.

@2010phenix
Copy link

@guigeddos i think it can be next to fix... look on #86

@xmrig thx, add by hands in few day and try to check

@guigeddos
Copy link

tim 20180316221500
@xmrig 2.5.0 This is the case? What's the matter

@xmrig
Copy link
Owner Author

xmrig commented Mar 16, 2018

@guigeddos such errors can happen by a lot of reasons, includes troubles with pool. Not issue in this case.
Thank you.

@SQZSoft
Copy link

SQZSoft commented Mar 17, 2018

Is that possible to include binary file in the new release for both armv7 and armv8? (rep to 32bit and 64bit)

@xmrig
Copy link
Owner Author

xmrig commented Mar 17, 2018

Binary ARM build is complicated, different platforms and many different hardware especially for ARMv7, build from source for target platform is not too hard.
Thank you.

@xmrig
Copy link
Owner Author

xmrig commented Mar 19, 2018

monero-project/monero#3424 PoW change delayed to around April 6.
Thank you.

@xmrig
Copy link
Owner Author

xmrig commented Mar 29, 2018

I close this issue, use #482 for future details.
Thank you.

@xmrig xmrig closed this as completed Mar 29, 2018
@xmrig
Copy link
Owner Author

xmrig commented Apr 3, 2018

If you have plans to mine Monero or other coins in list #482 you should update miner.
Thank you.

@svoutlokk
Copy link

qual versão do Xmring esta atualizado com a versão cryptonightv7?

@globeone
Copy link

The current master is still 2.4 and many pools are demanding 2.5 because of this bug report. would it be possible to please edit the bug report to say 2.4 as this change was already performed in 2.3
schermafdruk van 2018-08-20 00-46-38

@xmrig
Copy link
Owner Author

xmrig commented Aug 20, 2018

@globeone but current master is v2.6.4 https://github.com/xmrig/xmrig/blob/master/src/version.h#L30
Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests