Topic: [DEAD] DeepBit.net PPS+Prop,instant payouts, we pay for INVALID BLOCKS too - page 312. (Read 1601343 times)

Hum, it also seems to me that we have to trust the pool owner, because he has the possibility to cheat by occasionally submitting a block on his own without rewarding users.

The last 20 hours hasn't been kind -- would have been better if doing PPS.  This was not the case yesterday, however.

I can only suggest PPS for CPU mining and even more so OLD CPUs where the potential for not submitting a share on a very short "block found" would leave you missing a reward.

@hazek

Had a couple second hiccup from the looks of it but other then that it's fine.

no, it is like mining solo - you can break any time

Is something wrong with the pool server or is it me? I keep getting

Listener for "hazek": 04/03/2011 16:31:51, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:31:57, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:32:03, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:32:09, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:32:15, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:32:21, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:32:28, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:32:34, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:32:40, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:32:46, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:32:52, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:32:58, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:33:04, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:33:10, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:33:16, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:33:22, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:33:28, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:33:34, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:33:40, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:33:46, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:33:52, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:33:58, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:34:04, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:34:10, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:34:16, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:34:22, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:34:28, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:34:34, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:34:40, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:34:46, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:34:52, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:34:58, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:35:04, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:35:10, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:35:16, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:35:22, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:35:28, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:35:34, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:35:40, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:35:46, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:35:52, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:36:36, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:36:43, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:36:49, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:36:55, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:37:01, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:37:07, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:37:13, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:37:19, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:37:25, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:37:31, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:37:37, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:37:43, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:37:49, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:37:55, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:38:01, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:38:07, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:38:13, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:38:19, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:38:25, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:38:31, Problems communicating with bitcoin RPC
Listener for "hazek": 04/03/2011 16:38:37, Problems communicating with bitcoin RPC

And if I ping you I get periods of Request time outs while if I ping anything else I don't?

Man we're unlucky atm. Yesterday there was a period when it seemed like we had god mode on and were getting blocks within 30-50min but now even with ~30% increased speed it takes us for hoooooouuuuuurrrrrssss :S

I was wondering that does it harm my rewards if i reboot computer (let it cool few hours) and shares in miner starts from beginning?
(i'm not sure how long my computer has been mining in a row)

My GPU and HDD's started to make odd sounds and fan speed is 70% ..

i never said that

Please, no sarcasm. You're right indeed, I forgot about the supply/demand rule, thanks. Time to re-think it over again, but i kindly disagree with you on the point that if it takes 3 years to generate a block at the same exchange rate, no-one will mine; let's agree to disagree on that.

what you're saying is probably incorrect

most current miners are motivated by profit,
as long as there is profit in mining, it doesn't matter, if you need 3 hours, 3 days, 3 weeks, 3 months, or 3 years to generate a block.


Why?
if you say earning == BTC per day, then you're right as far as it gets less every 2016 blocks,
but 1 BTC might have more value in 3 months than today,
you seem to know the future price already, i don't.

Thanks, seems i missed that while reading, thanks for correcting me. So, to actually depend on fees, we'll have to reach the point where the block generations rewards too little? That's too far away, so i guess we can enjoy it for a while longer than i thought .

Opps, read block as share for some reason.

^^Yeah that

I get it now.  Thanks for the explanation.

PPS is not connected to blocks. You receive your reward for submitted shares.
Your balance is updated once per hour.

It's kind of pointless because the only person seeing them knows they are you anyways.

From the Main Page:

It'd be in-line with Bitcoin's creation of a new address for every transaction. More anonymity.

I tried out the Pay-Per-Share payout method and found that it does not give any details as to how much was being paid out per block.  Is this a glitch or something that is not yet available?

What may be the purpose of this ?

Loving it, my initial connection issues are gone.

A suggestion, how about a field for a list of addresses that can be sequential/randomized and reused/consumed instead of a single one, perhaps even per-miner?