Hey Guys,

 I just updated my XMR-Stack version, keep getting block rejections.

Is there something obvious I'm not doing or have not set up?

Have pool set as

"pool_list" :
[
 {"pool_address" : "stratum+tcp://xmr.coinfoundry.org:3034", "wallet_address" : "48KXbQ5ggAe3Pq9fAYqGdqdCWvkAz5xyz7p4uvWWcdmmQacEWvxfqUZXsh8WCr7SU3Zpr1vf95WWKGiGGKjYXFT537zSVvy.april", "rig_id" : "", "pool_password" : "", "use_nicehash" : false, "use_tls" : false, "tls_fingerprint" : "", "pool_weight" : 1 },
],

If I do a regular ping to xmr.coinfoundry.org (resolves to 97.107.139.34) I get 45ms ping time.  However all of my miners are bouncing all over the place from 400ms - 4000ms.

Same results on Windows 7, Windows 10, Linux...

I have restarted the miners, network devices, and cable modem.

Any ideas?

If you want me to change the IP address of the server how should I put it in XMRIG.  I currently have it as xmr.coinfoundry.org

Thank you for your help.

Oliver, check out the LTC pool, because it works really weird. It is not good and the connection with the pool is cut every two minutes more, or less.

I come across to xvg blake2s mining pool at https://cryptocartel.one and read their bulletin

VERGE NETWORK RESTORED!
ALL BUGS PATCHED BY VERGE DEV COMMUNITY!

05.04.2018 13:00 (GMT+7) - Attack Verge network.
05.04.2018 22:00 (GMT+7) - The Verge network has been restored. Pool works in the normal mode.
06.04.2018 13:00 (GMT+7) - Again Attack Verge network.
06.04.2018 17:00 (GMT+7) - The Verge network has been restored. Pool works in the normal mode.
07.04.2018 05:00 (GMT+7) - 1st bugs Verge network fixed, awaiting hadrfork in 2042000 block.

So is this true? We can continue mining xvg?

Hello, all my miners for XDN Monero, 48ZxFxTBFTRNZETCbrm2PsLGweo4uSEM6764Nynp1Zmq5EiwasA3j2VY3SJoynBoje2VT2Abea7Yr5zPsXs7RhyYJ9JBie4 , are saying "Bad Hash" when you hit "r" and it keeps saying result rejected by the pool. This started yesterday evening.

core 3 of my CPU is always showing o load or close to it on core temp, ut it gets the hottest on start up and stays around the same temperature as the other 3 cores 0,1,2 9(new monero miner again)

Where is the default donation setting in the new monero minngsoftware?

I’m getting the following error on Verge B2s, but the pool seems active. My connection was fine for 2-3 days. In us, Nvidia, ccminer. Any thoughts?

stratum connection failed ... connection refused 

I been mining LTC forever -- but just switched to verge a few days ago ... 

it seems to be hashing fine -- i have 1gb of machines pointing to pool -- i seem to be sent the coins as payment -- but they do not show in address -- and my address then does not show up when searching blockchain . 

can you plz look into my friends -- i really enjoy your service and platform ! 

my address is 

DCqyH7wSo3UbGRkaAMWKYfJYxMEpe1KPd8

thx in advance my friends 

Hot on the heels of yesterday's 51% attack on the Electroneum blockchain, there was a another attack of the same category on the Verge Blockchain causing both our daemon nodes to crash and requiring a full resync to recover.

The exploited a bug in retargeting in the XVG code. Usually to successfully mine XVG blocks, every "next" block must be of a different algorithm so for example scrypt, then x17, then Lyra etc. Due to several bugs in the XVG code, you can exploit this feature by mining blocks with a spoofed timestamp. When you submit a mined block (as a malicious miner or pool) you simply set a false timestamp to this block one hour ago and XVG will then "think" the last block mined on that algo was one hour ago. Your next block, the subsequent block will then have the correct time. And since it's already an hour ago (at least that is what the network thinks) it will allow this block to be added to the main chain as well.

Full details here: https://bitcointalk.org/index.php?topic=3256693.0

Update 4: I'm currently recompiling our Verge daemons and will let them sync up from the ground over the coming night. I will re-open both verge pools for a trial run tomorrow. If nothing bad happens they will stay open.

Update 3: The attack is still going on unmitigated and won't be mitigated until today's bandaid fix kicks in at block 2040000. You can verify this yourself by paying attention to the block timestamps on the Verge explorer. Sometimes the same block number is mined multiple times per second. Overall block times are are approx. 1 second. https://verge-blockchain.info/

Update 2: The devs issued another bandaid fix for the exploit that just slightly mitigates the underlying problem. Until they come up with a proper solution, pools will remain offline. I'm with ocminer (@SuprnovaPools) on this, I cannot justify to have our miners shoulder the risk of getting scammed of their earnings by some clowns gaming the blockchain and risking the reputation of the pool.

Update: On 05. April the attacker started again and mined about another 12000 blocks:

I skimmed the logs and saw the attacker started the new attack at around block 2014060 and stopped just now at block 2026196. The second attack is ongoing. The attacker is getting one newly mined block per second and orphans other legit blocks - https://www.reddit.com/r/CryptoCurrency/comments/89t4yc/xvg_still_being_exploited_after_fix_by_dev_check/