Quote from: agentcash on April 03, 2017, 06:12:05 AM

Quote from: kano on April 01, 2017, 09:43:43 PM

Quote from: Hippie Tech on April 01, 2017, 09:17:38 PM

...
The stolen shares are, in most cases, far above.. NOT below the current difficulty. Think about it. If you found a share that was hundreds of times the current difficulty, wouldn't you want to save it ?
...

Lulz no idea what you been smoking to confuse you, but a share is only worth the value of the work it was generated for, and a valid block share is only worth a block no matter what difficulty it is (as long as it's a block).
... and if a block is not submitted immediately, it's worth nothing if someone else finds a block while you procrastinate, so no you wouldn't save it - that's stupid.

If a share is worse than the requested work difficulty, it's worth nothing.
If a share is better than or equal to the requested work difficulty, it's only worth the requested work difficulty.

I didn't see his full post, but what is to stop someone from opening multiple connections and submitting shares just above the work diff? Say you have a miner that avgs 10k diff, open two more connections to submit all work from 5k-9999 and four more connections for all work from 2.5k-4,999, etc. This miner would be making the same as an honest miner, in addition to all the proceeds from submitting his lower shares on the other connections.

Seems even easier to take advantage of on pools that allow you to set your own difficulty. Open up a bunch of ranges and get paid huge amounts for rarer high hashes, while still getting paid on as low hashes as your connection speed allows.

I asked about this before, but I think I confused the issue previously by asking about connection 'cookies' or individual connection nonces to try to prevent this.

It would be obvious from statistics of course, but it still seems ripe for exploit on pools that don't pay much attention.

You can't.

A share is associated with a work item - and it can't pretend to be associated with a different one.
That work item has a difficulty that the pool assigns.
The work item is of course also unique per 'worker'.
Edit: and by 'worker' I mean a connection to the pool (which may be a miner or a proxy)