You don't get paid the instant the block gets found, it needs verifying first.  e.g. a VTC block was found about 4 hours ago and it wasn't completely verified until about 15 minutes ago.

One thing to also try is setting your difficulty the next level up, as I have done in my thread over here: http://poolmining.userecho.com/forums/1-general/topics/221-theory-on-issues-with-lyra-coins/

I don't have enough data to know if it has made a difference or not.

You're mining on supportxmr not here :)

Excavator displays a better hash rate (about 10%), but (as above) the difficulty tanks very quickly for me so I think ccminer will give a better return.  The Vertcoin One Click miner seems to give a similar hashrate to Excavator (on P2Pools) but doesn't seem to work here.

Thanks for the reply :)

Been doing some more testing, hHave been using :3097 for the past couple of hours now, along with the ccminer having the 'submit-stale' option set.

The has leveled out the difficulty at around 33, and it's getting shares fairly frequently and only shows 634/660 accepted - rather than the 100% accept rate with ccminer working around stale jobs - and I can live with that ratio.

So seems to be better :)

Might try excavator on :3097 as well to see if that also has a reduced failure rate.

EDIT: In Excavator it doesn't take long for the difficulty to take a nosedive so back to CCMiner :)

I would say reverse the Memory OC and give some of the extra to the core, as Lyra2rev2 likes using the core more than the memory.  My 1080 runs at about 42MH/s for

Power -15

Core +200

Mem -486 (note - not +).

The hashrate difference is the first item in the FAQ: https://poolmining.org/faq   Basically it's based on an average of the reported shares over the past 10 minutes, so sometimes can show higher or lower.

I'm not sure how much I was affected, but there were 0 blocks found when I started mining VTC here (after about 12 hours of mining on P2Pool - giving me about 1.2VTC).. and so far here only got just over 0.5VTC (excluding latest block) - with mining almost constantly since starting.

However, I realise the P2Pools work on faster payouts and have a larger base.

But here's mine anyway:

VgfJeZKaU4NR1P3N64a6Q5UxDEwyUjq4fJ

:)

If you're mining alone (not using a pool, or nicehash or whatever), you only get the reward (the coin you're mining) once a block is found and validated, which can take days, weeks, months or years depending on the difficulty - but you get all of the reward - e.g. VTC is currently 50VTC (worth about ~$430 currently), and you'd get to keep that all to yourself.  However, for most people solo mining would take a very long time to get a reward.

Huge pools like what nicehash was, were finding blocks very quickly, which meant even small contributors were getting a trickle of funds throughout their time, so they would see the fruits of their labour pretty quickly.

Smaller pools (like this one), generally take a lot longer to find blocks, and can be a bit erratic.  Once a block is found and validated the reward is spread among those who contributed to finding the block.

I think the error response handling is a bug in Excavator, I'm guessing NiceHash made it mainly to work with the pools first.

I've done some monitoring with Wireshark and the response from the pool is for example:

{"result":false,"error":{"code":21,"message":"job not found","data":null},"id":10}

Which as far as I can tell from the stratum specs I can find is correct, it should be an Object with those things not an array (like Excavator is complaining about).

That's not to say that the underlying cause of the "job not found" bug isn't on the pool side.   Given that ccminer enables a stale jobs workaround - potentially due to an underlying issue in miningcore?

Sounds good. I would say maybe have a tooltip (like on the hash rate) that shows the actual shares from the miner and a short explanation that the figure is based on shares received multiplied by difficulty?