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

[slush]

Please set your getwork request period to 5 seconds of you are using longer one.

Do you check validity of submitted shares? I mean, does your json interface return "false" when the share has older prevhash than the current bitcoin block is?

Originally I counted everything, but changed it right because those miners with very long ask period...

[friendsofkim]

Based on the last block generated, the payout per share was ((0.97 * 50)/105149 shares) = 0.000461250... BTC per share.

At the moment, the pay-per-share option pays you 0.00080949.... BTC per share, meaning it pays twice as well on the pay-per-share option, unless I'm mistaken.

I'm not sure I understand this - with pay per share, isn't the operator taking a greater risk by guaranteeing a fixed payout with uncertainty about how much time will be needed to create a new block. Therefore the price per share would be expected to be lower than the proportional payout, because the operator is hedging against risk.

I've switched to pay-per-share for now 

[[Tycho]]

I'm not sure I understand this - with pay per share, isn't the operator taking a greater risk by guaranteeing a fixed payout with uncertainty about how much time will be needed to create a new block.

Yes, i do :)
Moreover, currently i also take the risk of paying for unconfirmed blocks, one of which was found today and will be paid to my customers as normal one.

[[Tycho]]

Update: Minimum payment threshold is 0.01 BTC now. I recommend setting it higher to prevent flooding the network with small transactions.

[BitLex]

Therefore the price per share would be expected to be lower than the proportional payout, because the operator is hedging against risk.

propotional payout should be
((0.97 * 50)/55590 shares) = 0.00087246
though that's on average, it varies a lot from block to block, if pool needs more shares to solve a block, proportional payout will be smaller,
if pools needs less shares to solve a block, proportional payout will be higher.

in your example, you took a block that needed a lot more than on average, so payout was a lot smaller.
on other blocks the pool solved, the payout was a lot higher.

here's some other examples that look quite different to yours:
01.03.2011 06:11:38 shares: 29398 = 0.00164977
01.03.2011 04:27:58 shares: 27938 = 0.00173599
28.02.2011 12:13:30 shares: 40899 = 0.00118585

in the end proportional mode depends on "pooled luck", pay-per-share doesn't.

[friendsofkim]

in your example, you took a block that needed a lot more than on average, so payout was a lot smaller.

True. I based it on the most recent block. Mostly, I am interested in how pay-per-share is determined. Based on the last block it would seem the operator would have lost out. Then there is the risk of unconfirmed blocks being paid out as well.

Not picking at all by the way, just fascinated by how it works.

[slush]

Mostly, I am interested in how pay-per-share is determined.

One share in pay-per-share mode is 45 BTC / (current difficulty)

[friendsofkim]

One share in pay-per-share mode is 45 BTC / (current difficulty)

Blocks which take longer than statistically expected (give current difficulty) cost the operator more if he is paying out fixed pay-per-share (since it would be cheaper to pay proportionally, than by share at said rate.)

So faster than expected blocks benefit the operator, to the extent that he has fixed liabilities based on price-per-share of 45 BTC / current difficulty.

[songchen]

Has anyone else had trouble connecting to deepbit.net?

I've done a bunch of cache clearing, router powercycling, and DNS juggling, but I still cannot ping or trace route to deepbit.net.

Anybody have an idea as to what the problem is? Am I being blocked at the ISP level or something?

update: working now! thanks, whatever you did tycho.

[Neereus]

Connecting fine here.
Do you mean the site(port 80) or mining(port 8332)?

[[Tycho]]

Has anyone else had trouble connecting to deepbit.net?
I've done a bunch of cache clearing, router powercycling, and DNS juggling, but I still cannot ping or trace route to deepbit.net.
Anybody have an idea as to what the problem is? Am I being blocked at the ISP level or something?

Send me your IP address in PM, i'll check it.

[cactusbin]

Suggestions:

1) Display the server time on the site. It is useful to know the relative time the last block was completed without have to do time zone conversions.

2) Make the "average speed" calculation the average over an hour or more. Currently, the statistic fluctuates 20MH/s every couple minutes for me, which is not useful at all. Perhaps make two or three averages? Current (7 minutes), Recent (couple hours), Lifetime (not including downtime).

[sc8nt4u]

Just joined with my 2x5970s as I was losing close to 2% of my blocks due to invalid/stale blocks. I hope your pool is as reliable as Slush's pool.

[JWU42]

So far so good for me - but remember it is _BETA_

[[Tycho]]

Suggestions:
1) Display the server time on the site. It is useful to know the relative time the last block was completed without have to do time zone conversions.
2) Make the "average speed" calculation the average over an hour or more. Currently, the statistic fluctuates 20MH/s every couple minutes for me, which is not useful at all. Perhaps make two or three averages? Current (7 minutes), Recent (couple hours), Lifetime (not including downtime).

1) Yes i was planning to do something about this. Server's time is GMT(UTC), so i didn't mentioned it before.
2) The point of the "luck meter" is to show current speed, so user can see if his miner is working correctly. I will think about adding hour average, just didn't wanted to stuff the pagee with too much info :)

[planalpha]

Tycho
I was wondering if you were planning on adding SSL to the website, at least for the login, but hopefully for it all.
That would be great since I know you have nothing better to do.

Thanks for setting all of this up!

[Neereus]

Tycho
I was wondering if you were planning on adding SSL to the website, at least for the login, but hopefully for it all.
That would be great since I know you have nothing better to do.

Thanks for setting all of this up!

I would be inclined to agree. While minimal damage could be done if someone else gets in, it would suck to lose our transfers to someone else because they changed the address our coins are sent to.

[[Tycho]]

I was wondering if you were planning on adding SSL to the website, at least for the login, but hopefully for it all.
That would be great since I know you have nothing better to do. :)

Yes, this is possible, i'll look into it tomorrow. May be i can also add option to lock bitcoin address or reqire e-mail confirmation for changing it.
By the way, if THEY are sniffing or MITMing your connection, how are you going to get correct SSL certs for my site ?

[planalpha]

Tycho-
You're correct if you plan on using a ssc, but that's a low risk at my house opposed to checking my stats at Starbucks.


Thanks again.

[[Tycho]]

You're correct if you plan on using a ssc, but that's a low risk at my house opposed to checking my stats at Starbucks. :)

Another option is to allow stats checking with just worker's password, without possibility to change anything.