That's my guess to, but i have to ask.
It was our hopper-detection that found the user, as he begin mining at the start of a round.
So it has to be intentional, either from his or from pirateat40's side.
It was our hopper-detection that found the user, as he begin mining at the start of a round.
So it has to be intentional, either from his or from pirateat40's side.
As someone who has, in the past, purchased shares on your pool specifically, as a buyer, we have no way of timing a purchase. The shares I purchase sit in a queue if other purchases were made before me. I've earned BTC on purchases, I've lost BTC on purchases.... on your pool.
That being said, most of us who purchase shares WOULD VERY MUCH like for things to start at the beginning of a round, however this will never be possible, because every purchaser would follow suit and try it.
Many assurances have been given to us users of the service that there is no backend bitcoind, no hashes are being proxied to pools UNLESS someone has purchased shares. No hopping. bitHopper cannot handle the getworks. I trust pirateat40 implicitly about the that statement: "no backend proxies, no bitcoind's". Someone paid BTC to mine your pool.
even if they had a bitcoind in the backend, they would be paying miners X amount per share, which is about 40% above what they would get from the blocks mined.... they would be rolling the dice just like the purchases are doing.
)
