+5
Under review

ATTN: Impending Monero v7 Hardfork

Oliver 6 years ago updated by Im TheLordOfGames 6 years ago 27

All software components of our Monero pool have now been upgraded to ensure a seamless transition to the upcoming Monero v7 Hardfork which will activate on the April 6th 2018.


To continue mining Monero after the hardfork activation, miners need to upgrade their software as well. The following miners have been updated so far:


  • XMR-Stak (Windows Nvidia, AMD, CPU Mining)
  • CastXMR (Windows AMD Mining)
  • XMRig (Linux/Windows CPU Mining)

You can mine using the updated Miners right away. Both the pool and the miners will seamlessly transition to the new PoW algorithm upon reaching the target block height for the hardfork. Be advised that older mining software which has not been updated for the v7 hardfork will stop working after the fork.


The Monero Pool Setup-Generator has been updated to work with the new version of XMR-Stak. 

+1

I use CastXMR and the latest version is supposed to be ready for v7.

Under review

Thanks Ian. Added to the list.

Anyone who updated to XMR-Stak 2.3 should update again to 2.4.1 as the former apparently had some serious problems. I've already updated all download links on the Monero Pool.

what time does the fork happen?

Block 1546000

They estimate April 6th

im using none of those progs. Do I just set up as if im a new user using the same  miner address?




Looks like the upcoming v7 fork won't do much to fend off ASICs if not modified again soon: https://github.com/curie-kief/cryptonote-heavy-design

не работает RIG_ID в файле конфигурации в XMR-Stak v2.4.1 .

для разных rig_id - см. значение по умолчанию

RIG_ID does not work in the configuration file in XMR - stack v2.4.1 .

for different rig_id see the default value

Well, it looks like the CastXMR I'm running made it through the fork just fine and transitioned to the new monero7 blocks even without me having to change the algorithm in the configuration.  All of us here mine at an awesome pool.  I'm no fan of change, though change that happens without much need of my attention I am actually OK with.


Now, we could find another block soon, that would be fine.  Like icing on the cake.

This keeps happening. https://gyazo.com/f26217bba98b703c9f4f94ad0fe933f2 I come back and my computer has gone to sleep. It was set to never sleep when plugged in, but this were changed by something (not me) Is it overheating and going to sleep or just timing out? I use core temp which should shut it down at 97 degrees after 2 seconds, Is that a safe setting forf an I7 laptop?

it just done it again, no errors though. Im going to check my power management again. Should it be spreading the load over all 4 cores?

This should be fixed now.

There has been minimal change in total network hash rate since the fork. Isn't this odd? Any ASIC or virus mining cryptonight should have dropped off.

The network hash already dropped

From at least 1 gh/s to around 500 or 600 mh/s

Coinfoundry's network hash counters are very slow, (idk how fast they update) they seem to update every some many hours.


From what ive read on the xmr reddit, the network hash counters seem to correctly update themselves with that big of a drop after a full day (720 blocks)


As you can see: 

https://www.cryptocoinsinfo.com/cryptonight-coins/monero-xmr/

The hash dropped around 6am utc today

That's good. We like it when things work like they should.

It looks like the pool lost half of our Monero H/s with this fork, and over half of our miners...  That is bad, right...

+1

I assume people are having issues with mining software. Doubt that there was any asics in our pool, since one X3 would be more than our total hash rate.

I am using XMRIG on Windows 7, Windows 10, and Ubuntu Linux 16.04.  Very easy to use and figure out.  But it was definitely a pain to do around 30 laptops, two computers and two old servers.  I highly recommend XMRIG for CPU mining, it is really easy to use.

+1

It's a combination of lower hashrates accross the board due to a slower hashing algorithm in v7 and miners still needing to update their outdated miners. Watching the live logs of the pool servers still shows tons and tons of invalid shares every second.

+1

I'm currently syncing two new Monero daemon nodes up from scratch and will switch the pool to use those later today. This has no effect on shares or balances.

I guess our issue is our hash rate isn't high enough to find blocks at the minute, even with the incredibly low difficulty?

Yep, we are probably half way or a little less to theoretically getting a block.

Going by CoinFoundry: (1/720)*(235.8MH/s) = ~327Kh/s

Going by cryptocoinsinfo.com: (1/720)*(414.8MH/s) = ~576Kh/s

This might be a stupid question, but will my wallet address still work after this fork? I never updated that? I am running a monero wallet on a server here at my office?