 Show Posts
|
|
Pages: [1]
|
can you tell me 156Mhash/s how many shares/hour(average, minimum?) should produce - please with formulae  At 26Mhps I'm getting around 20 shares an hour. This has ranged between 13 and 26 though just last night. Using this as a base you should be getting of the order of 120 shares per hour. |
|
|
|
Regardless, my question still stands. It always says my hash rate is higher than what I am seeing on my end.
This rate is based on how many shares you submit in a given 7 minute period to the server, rather than your actual reported rate on the client. Each share is good for about 14.2MH/s. So far you've been quite lucky it seems. |
|
|
|
|
So, for those doing a frogger between Prop. and PPS, another thing to consider is that if the rate of block discovery goes down through difficulty or lack of luck, I'm assuming the price in PPS will surely drop anyway in the long term.
PPS isn't a license to 'beat-the-market', it's there to even-out rewards at a cost of 7% to you, the miner.
In the short term, Tycho is bankrolling PPS when we have a bad run in the pool, but long-term the market demands he reduce the price of PPS unless he has deep bitpockets and a generous soul :-)
EDIT: If a block is taking around 10 mins for the network as a whole, then we're hoovering up around 8.5% of blocks at the moment. Does that compute?
|
|
|
|
|
The Pay-Per-Share seems to pay on a fairly good schedule too.
Can confirm the per-share rate change seems to work seamlessly as well.
EDIT: woo! new block :-)
|
|
|
|
Hehe, I was about to ask the exact same question. Did one share at PayPerShare before switching to Proportional for a few hours. Would be nice to see an "expected reward" field like with slush's pool to avoid confusion here, but it's not too big a deal.
I'm sure Tycho has it on the TODO list along with the pretty graphs and everything :-) Clean up this thread and it will be the help/FAQ page as well more or less. Eventually anyway. |
|
|
|
But so far even after 7-10 hours no share is showed in my account.
It says 0000000 balance only & i have not received any btc. even micros.
*snip*
Or i am the only one having problem?
The last block that paid out (the pool hit a +50BTC) was 17 hours ago. Yours shares for the last 7-10 hours will only pay out when the pool hits a new +50BTC. Simples. :-) |
|
|
|
After using the Pay-Per-Share for a few hours it seems to be working just pukka, apart from a slightly odd behaviour in the Account Balance ( http://deepbit.net/acc.php) It appears to track each new share perfectly in the balance sometimes, then will 'rewind' to an earlier value. Possibly in conjunction with an hourly balance update? |
|
|
|
* Connection #0 to host www.deepbit.net left intact
JSON decode failed(1): '[' or '{' expected near '<'
json_rpc_call failed, retry after 30 seconds Any ideas? Wouldn't be surprised if the response was HTML (404 or 503 error) instead of JSON. Other than that not sure. |
|
|
|
It can't be compared directly with 3% fee because it's 10% of unknown value for me. It may be more and may be less, comparing to proportional mode. If some block takes longer to find, this will be more than in Proportional.
I'm already 2 bitcents richer sucka! Should I spend it on crack or hoes, I wonder? It's fun and interesting to try these things out :-) |
|
|
|
*snip*
At your rate of around 100Kh/s you should see a hit every 11-12h by my count.
If the RPC failures increase, check you have the latest clients that persist connections nicely, rather than fire-hosing the server with connection attempts :-) You are right. I was wrong again. When that is the hash rate, one can expect solutions every that often. Now I have a 1Mhash/sec rate (gcc -O3) so I should get solutions approximately every 70 minutes. There wasn't one single correct thing in what I posted! No, there was! For the "fire-hosing" problem, I simply reduced the "getwork" call frequency from once every 5 seconds to once every 20 seconds. Not wrong, just learning, and quickly :-) The fire-hose thing was more of a problem with the official client until recently and applies less to what you're doing I think. |
|
|
|
Sorry, the number of bits is 32. My mistake. I'm new. The probability is one in 2^32. Should take around 5-6 hours on average if that hash rate is correct.
The benchmark/avg. is currently 1 share every 5 minutes at 14200Kh/s. At your rate of around 100Kh/s you should see a hit every 11-12h by my count. If the RPC failures increase, check you have the latest clients that persist connections nicely, rather than fire-hosing the server with connection attempts :-) And hi and welcome etc.  |
|
|
|
This might be a noobish question, but I've been receiving shares for a while now, but my account is on 0.0000000 bitcoins still...
Looking at http://deepbit.net/stats.php , the last payout for a successful find was around 3:19pm on the 26th Feb. If you started submitting shares after this then there is no payout, yet :-) - Thanks for setting this up Tycho. Nice, simple start is good :-) Let me know if you need any gfx/design to pimp up the deepbit.net site at any point as that is in my line. |
|
|
|
|
