[DEAD] DeepBit.net PPS+Prop,instant payouts, we pay for INVALID BLOCKS too

[DeepBit]

These 2 blocks were orphaned and reported by blockchain as originating from deepbit. I know blockchain isnt all that reliable, so it could be wrong, but since they dont show up on blockorigin at all, you may want to check if indeed those blocks werent yours:

00000000000008f768a2d460398108897d26ec3f99d9017463162116e720a5f4
0000000000000a840c96d0bd6555aa98a18fd380873ed1192db59f3ea6cc71b3

This issue can't be related to invalid blocks at all, it only affects stats collection.
As for those blocks, you can check if they are present in the stats table or not, block hashes are provided there.

[1575969832]

1575969832

[1575969832]

1575969832

[hi]

It appears that deepbit has had bad luck for last few months...my workers are not getting their daily avg of BTC for quite some time now. 

[rjk]

It appears that deepbit has had bad luck for last few months...my workers are not getting their daily avg of BTC for quite some time now. 

If you are using proportional scoring, your "bad luck" would be due to pool hoppers taking the profits. The only thing that changes the PPS price (if you are using that) is the difficulty.

[[Tycho]]

It appears that deepbit has had bad luck for last few months...my workers are not getting their daily avg of BTC for quite some time now.

Yes, there was a bad luck run some weeks ago, but looks like it's back to normal again.

[DeepBit]

We are experiencing some internal connectivity issues, I'm working on this.

UPDATE: Solved.

[DeepBit]

Some additional issues were caused by that bug with missed round ends. Sometimes a small amount of shares may be accounted for next blocks in the stats table instead of just finished one. No shares were or will be lost, but for someone this may be important.
Now I found out what should be done to prevent this and working on the fix.

Sorry for inconvenience.

[dlasher]

Deepbit/Inc : Any 'official' thoughts on this thread?

https://bitcointalk.org/index.php?topic=86129.0

[Graet]

Deepbit/Inc : Any 'official' thoughts on this thread?

https://bitcointalk.org/index.php?topic=86129.0

yes a site inaccurately reporting pools stats requires the pool to explain?
its a blockchain info problem - as stated more than 1 time in that thread
or you need deepbit to say the same yet again?

though it is rather amusing at times, like the day it showed Ozcoin (~8% of the network) as the biggest pool....

whats that old saying?
lies,damn lies and statistics,
statistics based on incorrect info will give.....?

[DeepBit]

Thanks, Graet. Comments posted.
(Nothing really wrong happened, BTW)

[dlasher]

Thanks, Graet. Comments posted.
(Nothing really wrong happened, BTW)

That depends on your perspective I guess.

The largest pool is choosing to not process transactions that don't meet their required minimum fee included with each transaction, thereby creating an artificial transaction backlog for the entire network.

[DeepBit]

That depends on your perspective I guess.

The largest pool is choosing to not process transactions that don't meet their required minimum fee included with each transaction, thereby creating an artificial transaction backlog for the entire network.

Depends on your perspective. Our fee policy is published (you didn't read it), we are trying to protect the blockchain from flooding (and optimizing our blocks).

Your information is not correct. We are processing transactions even with zero fees. Fees are only mandatory for TXes that are less likely to be personal or those that are over our optimal block size.
May be I'll change this fee policy because of those "1dice" transactions.

[rjk]

The fee is there for a reason and is designed into the network. There is no requirement to include transactions, even if they do pay a fee. Refusing to include ones that don't meet an arbitrary threshold is not evil.

[dlasher]

Our fee policy is published (you didn't read it), we are trying to protect the blockchain from flooding (and optimizing our blocks).

Did read it, but I'll include it here for those who didn't.

Deepbit's transaction fee policy
(This is not related to the pool's payments to our users)
We think that free transactions are very important for the Bitcoin system so we are including as much free transactions as possible into our blocks, possibly more than anyone else. But sometimes a fee may be useful, so here is our fee policy:
A transaction is considered to be 'free' if the offered fee is less than 0.01 BTC. Free transactions are only accepted if they are less than 2000 bytes in size and have no more than 5 outputs. Outputs less than 0.01 BTC are not allowed in free transactions. The minimum fee for non-free transaction is 0.01 BTC for each started 1000 bytes.

As I read that policy, anything less than 0.01BTC transaction fee (200x greater than what the bitcoin client considers the minimum) is considered "free" (unless it's payments to your users) falling into a bin of indeterminate behavior on Deepbit's part. Today you process a percentage of "free", choosing to not process some percentage of "free".

You're correct. That's your right. It's your hardware, it's your bandwidth, it's your money spend to offer the pool as a service to your users.

I'm just saying, given the current distribution of transaction fees, this choice is causing some transactions to take a lot longer than others, because somewhere between 30%-40% of the networks hashing rate (depending on the day) may choose not to process your transaction, because it doesn't pay them well enough.

Not saying evil, just saying.. It is what it is. And people should be aware

[Dalkore]

Did anyone notice they removed that current difficulty you are mining at (pool luck aka variance).   I really enjoyed seeing that, any reason why it was removed?

[DeepBit]

Did anyone notice they removed that current difficulty you are mining at (pool luck aka variance).   I really enjoyed seeing that, any reason why it was removed?

1. Current difficulty is always in the right column of the stats page. It's not removed.

2. This question is asked exactly each 2016 blocks (approx. 2 weeks), but looks like no one ever tried to read a few pages back :)
Luck information is removed automatically each time after the difficulty adjustment until enough stats are collected.

[eleuthria]

2. This question is asked exactly each 2016 blocks (approx. 2 weeks), but looks like no one ever tried to read a few pages back
Luck information is removed automatically each time after the difficulty adjustment until enough stats are collected.

To be fair, NOBODY reads anything but the first post and last page on a thread .  Expecting otherwise is like expecting somebody to read a EULA.  My recommendation:  Put up a placeholder/statement when luck isn't being shown, should reduce the question to every 5-6 diff changes instead of each one .

[DeepBit]

My recommendation:  Put up a placeholder/statement when luck isn't being shown, should reduce the question to every 5-6 diff changes instead of each one

Great idea, thanks :)

[Fiyasko]

Could we please get the "block found in" status report to actually exsist? I would actually like to look at how frequently Deepbit finds a block, And weather or not ENITRE blocks could be just simply NOT added to that list, And allowing Tycho (good man, Im not sayin he would do this, Im just saying that he Could while the "block found in" stat is broken) or someone with highpower in deepbit to run off with 50bitcoins that people Other than him spent xyz hours hashing... And no, Im not sure that it would be easy to just Yank a block like that.. But i think it's possible, And even if it's not, I think the freaking "block found in" statistic has been down for long enough!
Bring it backonline already!

[luffy]

do we have an attack or connection problems? i see pool rate way done!

[Quantus]

I got a red warning screen saying the sites certificate was out of date. Now i can't connect at all.  

EDIT: Fixed