Connecting fine here.
Do you mean the site(port 80) or mining(port 8332)?
Topic: [DEAD] DeepBit.net PPS+Prop,instant payouts, we pay for INVALID BLOCKS too - page 318. (Read 1601343 times)
March 01, 2011, 07:12:38 PM
March 01, 2011, 06:56:30 PM
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.
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.
March 01, 2011, 05:53:49 PM
Quote
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.
March 01, 2011, 05:45:56 PM
Mostly, I am interested in how pay-per-share is determined.
One share in pay-per-share mode is 45 BTC / (current difficulty)
March 01, 2011, 05:43:35 PM
Quote
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.
March 01, 2011, 05:34:13 PM
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.
March 01, 2011, 05:28:30 PM
Update: Minimum payment threshold is 0.01 BTC now. I recommend setting it higher to prevent flooding the network with small transactions.
March 01, 2011, 05:24:47 PM
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.
March 01, 2011, 05:01:59 PM
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
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
March 01, 2011, 04:45:45 PM
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...
March 01, 2011, 04:08:03 PM
Hello, people.
Please set your getwork request period to 5 seconds if you are using longer one.
Please set your getwork request period to 5 seconds if you are using longer one.
March 01, 2011, 02:23:17 PM
Have recently joined the pool - nice work.
A couple of things I noticed:
In the "My Account" section, my Mhash/s is sometimes reported 10x what my miner says it is, which is interesting. A lot of the time though, I'm getting 0 for all the stats except balance - even though I'm generating shares in the miner.
I thought it would be useful to see the number of shares generated by each worker in the web interface - I am mining from a work PC. It would be nice to log in and check the number of shares from home.
I was also interested in knowing how you calculate the per-share rate, if it's not sensitive information of course.
Thanks
A couple of things I noticed:
In the "My Account" section, my Mhash/s is sometimes reported 10x what my miner says it is, which is interesting. A lot of the time though, I'm getting 0 for all the stats except balance - even though I'm generating shares in the miner.
I thought it would be useful to see the number of shares generated by each worker in the web interface - I am mining from a work PC. It would be nice to log in and check the number of shares from home.
I was also interested in knowing how you calculate the per-share rate, if it's not sensitive information of course.
Thanks
The Mhash/s reported is the actualized Mhash/s determined by the number of shares passed to the server averaged over the last 7 minutes. The rate you see on your computer is the amount of work your actually doing. I would assume the reason you are seeing 0 is you have a low Mhash/s rate and therefore when you find a share your shares/7 minutes skyrockets but most of the time your shares/7 minutes is 0. This question was answered on the first page of the thread BTW.
March 01, 2011, 02:04:47 PM
Have recently joined the pool - nice work.
A couple of things I noticed:
In the "My Account" section, my Mhash/s is sometimes reported 10x what my miner says it is, which is interesting. A lot of the time though, I'm getting 0 for all the stats except balance - even though I'm generating shares in the miner.
I thought it would be useful to see the number of shares generated by each worker in the web interface - I am mining from a work PC. It would be nice to log in and check the number of shares from home.
I was also interested in knowing how you calculate the per-share rate, if it's not sensitive information of course.
Thanks
A couple of things I noticed:
In the "My Account" section, my Mhash/s is sometimes reported 10x what my miner says it is, which is interesting. A lot of the time though, I'm getting 0 for all the stats except balance - even though I'm generating shares in the miner.
I thought it would be useful to see the number of shares generated by each worker in the web interface - I am mining from a work PC. It would be nice to log in and check the number of shares from home.
I was also interested in knowing how you calculate the per-share rate, if it's not sensitive information of course.
Thanks
March 01, 2011, 10:10:32 AM
@[Tycho],
Have you been tweaking the server? I cannot login suddenly?
Have you been tweaking the server? I cannot login suddenly?
February 28, 2011, 11:09:15 PM
Every time I try to use this pool, it works for awhile. But, every time I come back and check up on my mining rig I see the RPC communication error. It seems to work for a number of hours and then just completely stop.
I have had some "Problems communicating with bitcoin RPC" with poclbm now and then, but nothing serious. Have you come up with a means of automatically switching to another server when that occurs? I'm currently working on some Perl that switches to my local bitcoind and checks the pool connection every 30 seconds when I get those errors. February 28, 2011, 10:48:01 PM
Every time I try to use this pool, it works for awhile. But, every time I come back and check up on my mining rig I see the RPC communication error. It seems to work for a number of hours and then just completely stop.
Looks like your miner can't recover from communication errors. 
February 28, 2011, 10:25:47 PM
Every time I try to use this pool, it works for awhile. But, every time I come back and check up on my mining rig I see the RPC communication error. It seems to work for a number of hours and then just completely stop.
February 28, 2011, 10:21:38 PM
I might be wrong, but as far as I can tell, when you use proportional, the shares you made with proportional stay proportional. Same with PPS.
True, but at least by sticking with Proportional <58061, you can cash in on a quick block jackpot. Once you go above 58601 hashes, the value of each hash solved with proportional will fall below the value of a hash solved with PPS. Therefore you can limit the losses in value by switching modes for shares solved after 58601.
Good point.
Oh well, I'll stick with PPS because I like quick feedback. lol
February 28, 2011, 10:00:00 PM
I switched to PPS today and glad I did 
February 28, 2011, 08:31:39 PM
I might be wrong, but as far as I can tell, when you use proportional, the shares you made with proportional stay proportional. Same with PPS.
True, but at least by sticking with Proportional <58061, you can cash in on a quick block jackpot. Once you go above 58601 hashes, the value of each hash solved with proportional will fall below the value of a hash solved with PPS. Therefore you can limit the losses in value by switching modes for shares solved after 58601.
Jump to: