No for multiple reasons:

1) block change times on a pool are the #1 priority - slowing that down (by delaying work changes) is how you lose blocks and get orphans

2) the work base for each miner is different, so you can't send a miner the work base of the other miner that found the block
 If the work bases weren't different, then miners would be wasting time mining the same work and getting the same results

3) there's no guarantee that 2 miners will find the same block with the same work since their speed and mining code may increment the extranonce differently or to a different level (due to speed)

Incorrect.

Withholding is done by the miner - they simply don't return the particular share that is a block, they just return (some or) all other shares.
Even if they do this, the person renting out their hardware gets paid and so does the renting service.
You can't know in advance which work contains a block, you only know when you find a particular share that is better than network difficulty.

It has nothing to do with where you get your hashes from except the obvious that: if it was your own miner and you were solo mining you'd be throwing away your own block

See, with NH;  they are trying to solve a block with your transaction;  so a different hash all together.  Theres no way for a renter to withhold blocks like that...   you can see the live submissions/hashrate coming through the solo pool.  I don't see that being faked at all.... unless the hash renter feeds garbage data to the pool (I would assume the pool would invalidate bad work?)

My one recommendation to people going for rented hash:

Its smarter and more statistically probable if you rent as much hash as possible and run it at once.

More workers working on the same block == greater chance of solving _your_ block in a given amount of time.

If you just space out the hash in smaller amounts over time;  you have less hash to find that block in a given time and it is somewhat wasteful.

In the same sense that pointing two antminers at two different BTC payout addresses, will both have the same probability of finding a block;  whereas if they are both mining to the same address, they stand twice the chance as find a block as when they are working independent.

I hope people grasp this idea.....

The more hash you cram in that "10 min" gives you a higher actual probability of finding a block.

To some of the regular posters here, I'm curious about reaction to this https://bitcointalk.org/index.php?topic=441465.msg13062153#msg13062153

If you don't want to follow the link, apparently 6 * Difficulty shares have been pointed at Eligius from Nicehash and not one block solve yet. Relevant here I think because many of us use Nice/Westhash to gamble.

Plenty of people have found blocks here using NH/WH and MRR.  I'm not sure what's going on over at Eligius...

Guys I have a point to discus , But plz philip dont understand me wrong , Its just a point

If we pay a fee to you to manage this rental, and you only create an fixed order then you go . anyone can do that

I think your main work is to rent @ best cheap price like 0.0071 or 0.0072 and monitor this order to ensure that it alive .

But you just create fixed order @ 0.0076 . we can save more and got about 2 extra hours if we rent @ 0.0072

My idea is to create fixed order @ 100 TH  AND create another standard order 600TH  @ 0.0071 and monitor it

Wow! Congratulations!

But man, you must have solid brass clankers to pull that off. You risked almost 28 BTC to get 50 back. Nice luck there.

Congrats to    1LPWZ9AskyF8Ux384cXoYbvNRTKgLooGh3

Edit: @ck: Poolmessage is cool now!

Question regarding the Bestshare.
The bestshare shown by my miner is totally different than when I view it through the weblink of the pool.

Is that normal?

By default it will mine on eligius at the burn in address associated with your account. The account will already contain any coins the unit might have mined during the HF burn in testing. In my case around 70 mBTC. It is running @ 422 GH/s

For factory testing an initial Bitcoin wallet was generated on this device in order to perform a live test of your product.  As a gift to you, we are providing you this wallet so you can claim any mining proceeds from the mining pool (Eligius) that may have accrued, but we do not imply that any have accured, or that the mining pool, which is beyond our control, will release any proceeds.

101xx and still only status "paid" (Payment date 11/06). Got the same standard answer from support like posted here before, to contact them again on friday.

You might want to hold onto that email.

Though you can bet they are going to move heaven and earth to get shipping labels in the system for every batch 1 order by midnight honolulu time.

I tried during the account fiasco... and didn't get thru for the first time in half a dozen calls over the past few months...   but others did... Cypher got thu.. and others...  just when the answering machine is on, the line is either busy, or they are closed...  You gotta know by now there are hundreds of people calling every hour trying to talk to KNC...   and during a incident like that...thousands...
It's like trying to be caller #9 on Santana Tickets... lol

We'd like to take a moment to address sharpspoon's concerns:
 
Firstly - we would like to apologize to sharpspoon for any miscommunication or lack of communication on CoinTerra’s part. We’ve already reached out to him directly this evening via a Private Message and a senior member of the management team will look into his specific situation and resolve it as quickly as possible.

Secondly - and this is not a "the dog ate my homework" excuse - but we've done some investigation and we *think* we know why sharpspoon's issue wasn't responded to when it was supposedly escalated to senior management. I was reluctant to go into the details but in the interest of transparency here goes:  When our Tier 2 (escalated) customer service expert cc'd (it's a blind cc, only viewable internally) a member of the management team asking him to personally look into the issue, he left the ticket 'open' (as opposed to 'resolved', which is what we do when we close a ticket). It appears that in our Customer Support software, when you do that, the ticket stays in ‘open’ limbo and doesn't forward the cc until the ticket is finally closed (resolved) - which only happens when the issue has been fixed satisfactorily for the customer. We are going to look into this and find a solution, if it is indeed what I suspect the problem is.

Thirdly - yes it is true that we have been inundated with inquiries over the past two weeks, due to the massive surge in world-wide interest in the Bitcoin ecosystem as the BTC price has skyrocketed, and that has directed a huge amount of traffic to CoinTerra: This has been very much a double-edged sword!

As soon as we saw the surge in inquiries we took action to add significantly to our Customer Service team, both on phone support and web/email tickets.  However, it does take a little time to train new staff up to be able to respond to issues, and the fact that the more senior customer service team members needed to spend time training the new members meant that they weren't able to be as effective as they normally are at responding to issues.

In response to that situation we had more senior staff roll up their sleeves to help to clear the backlog. Those of you with open tickets may well have noticed our responses through the Thanksgiving holiday, and we have now caught up to the point where there are no "unassigned" tickets up to Wednesday evening when we officially closed for the holidays.  There are still a number of escalated tickets where additional steps are required to resolve the matter (e.g. if someone made a mistake on their wire transfer such as a misspelling or wrong address, which requires investigation.)  We shall endeavor to be fully caught-up on these as quickly as possible when the offices re-open on Monday.

Finally, we'd like to thank sharpspoon for pointing out that we did not, in fact, delete any of his posts on our forum. We will occasionally move a post if it is in the wrong sub-forum (or should be in a more appropriate sub-forum), and we will, of course, remove any spam that gets through or any content that is illegal/profane/highly offensive - normal forum moderation stuff. But we do not have a policy of censoring free speech.

We hope this goes some way to explain the situation. Of course, actions speak louder than words, so we would hope that sharpspoon will let the community know when he's been in contact with our senior management, and when his issue has been resolved.
 
Have a happy Rest-Of-Thanksgiving weekend!
 
 == The CoinTerra Support Team ==