Topic: [28 TH] pool.itzod.ru - RSMPPS/LongPoll/JSON API/Websockets/No Invalids/Stratum - page 10. (Read 50893 times)
April 08, 2013, 01:05:01 PM
April 08, 2013, 10:58:58 AM
April 08, 2013, 10:39:49 AM
RSMPPS implements the shared risks model. Risks shared between current and future users.
http://eligius.st/wiki/index.php/Shared_Maximum_PPS
There is a rounds queue. Rounds are closing according to LIFO rule.
Quote from: coinnewb
Although by looking at the graphics (https://pool.itzod.ru/graphs.php), it seems like payments are being made toward future payment. But it seems like it always stays relatively high and has never reached close to 0 in the last one year.
It can reach zero or even negative values in any moment. Quote from: coinnewb
When the block takes a long time to solve, not all of it is paid -> increased future payment
When the block takes a short time to solve, no payment is made toward future payment
When the block takes a short time to solve, no payment is made toward future payment
http://eligius.st/wiki/index.php/Shared_Maximum_PPS
Quote
Recent SMPPS (RSMPPS)
The order of issued "extra credit" is remembered, and rewards are given starting at the most recent shares first. Therefore, the current round's shares are rewarded PPS in full first, and only after that are unpaid shares from the previous round considered. If there is still remaining reward to be distributed, this continues to go back round by round paying for underpaid shares.
This system aims to prioritize the most recent miners first.
The order of issued "extra credit" is remembered, and rewards are given starting at the most recent shares first. Therefore, the current round's shares are rewarded PPS in full first, and only after that are unpaid shares from the previous round considered. If there is still remaining reward to be distributed, this continues to go back round by round paying for underpaid shares.
This system aims to prioritize the most recent miners first.
There is a rounds queue. Rounds are closing according to LIFO rule.
Thanks for taking the time to explain!
April 07, 2013, 04:09:59 PM
RSMPPS implements the shared risks model. Risks shared between current and future users.
http://eligius.st/wiki/index.php/Shared_Maximum_PPS
There is a rounds queue. Rounds are closing according to LIFO rule.
Quote from: coinnewb
Although by looking at the graphics (https://pool.itzod.ru/graphs.php), it seems like payments are being made toward future payment. But it seems like it always stays relatively high and has never reached close to 0 in the last one year.
It can reach zero or even negative values in any moment. Quote from: coinnewb
When the block takes a long time to solve, not all of it is paid -> increased future payment
When the block takes a short time to solve, no payment is made toward future payment
When the block takes a short time to solve, no payment is made toward future payment
http://eligius.st/wiki/index.php/Shared_Maximum_PPS
Quote
Recent SMPPS (RSMPPS)
The order of issued "extra credit" is remembered, and rewards are given starting at the most recent shares first. Therefore, the current round's shares are rewarded PPS in full first, and only after that are unpaid shares from the previous round considered. If there is still remaining reward to be distributed, this continues to go back round by round paying for underpaid shares.
This system aims to prioritize the most recent miners first.
The order of issued "extra credit" is remembered, and rewards are given starting at the most recent shares first. Therefore, the current round's shares are rewarded PPS in full first, and only after that are unpaid shares from the previous round considered. If there is still remaining reward to be distributed, this continues to go back round by round paying for underpaid shares.
This system aims to prioritize the most recent miners first.
There is a rounds queue. Rounds are closing according to LIFO rule.
April 07, 2013, 04:05:35 PM
What was said was that:
When the block takes a long time to solve, not all of it is paid -> increased future payment
When the block takes a short time to solve, no payment is made toward future payment
Although by looking at the graphics (https://pool.itzod.ru/graphs.php), it seems like payments are being made toward future payment. But it seems like it always stays relatively high and has never reached close to 0 in the last one year.
When the block takes a long time to solve, not all of it is paid -> increased future payment
When the block takes a short time to solve, no payment is made toward future payment
Although by looking at the graphics (https://pool.itzod.ru/graphs.php), it seems like payments are being made toward future payment. But it seems like it always stays relatively high and has never reached close to 0 in the last one year.
April 07, 2013, 03:46:34 AM
Hi,
what about future round payments? Is there any problem?
Since (around) the last invalid block, it goes only up and not down on short rounds.
I got NO extra payment on short rounds!
Also I got no payment for the last invalid block, although I've stated that you pay for invalids too.
Thanks
what about future round payments? Is there any problem?
Since (around) the last invalid block, it goes only up and not down on short rounds.
I got NO extra payment on short rounds!
Also I got no payment for the last invalid block, although I've stated that you pay for invalids too.
Thanks
Was there an answer to this question? Sorry if I missed it.
I don't understand the question. That might be why it wasn't answered already. Can you paraphrase it?
April 07, 2013, 12:50:37 AM
Hi,
what about future round payments? Is there any problem?
Since (around) the last invalid block, it goes only up and not down on short rounds.
I got NO extra payment on short rounds!
Also I got no payment for the last invalid block, although I've stated that you pay for invalids too.
Thanks
what about future round payments? Is there any problem?
Since (around) the last invalid block, it goes only up and not down on short rounds.
I got NO extra payment on short rounds!
Also I got no payment for the last invalid block, although I've stated that you pay for invalids too.
Thanks
Was there an answer to this question? Sorry if I missed it.
March 24, 2013, 01:36:26 PM
Testing fixes at testnet, will apply it soon.
March 23, 2013, 04:14:50 PM
That's correct, problem will be fixed tomorrow. 
March 22, 2013, 05:37:57 AM
there seems to be some problems with the last CGMiner 2.11.3, they implemented a new version of stratum (that is what i`ve heard on IRC)
March 20, 2013, 02:39:26 AM
The first ASIC user in our pool. Congratulations to avalon from miners toplist.
March 12, 2013, 05:18:56 AM
Everything is OK now, pool is back to operation. Withdrawals enabled.
March 12, 2013, 01:48:50 AM
Block chain download is in progress, 120k blocks received.
March 12, 2013, 12:01:09 AM
Mining and withdrawals is stopped until chain download and database rebuilding are in progress. I'm sorry. 
March 11, 2013, 09:37:24 PM
Bitcoin fork are we on .7 or prior because .8 is bugged.
February 26, 2013, 01:55:44 AM
Welcome. I guess that it's your email in my inbox. Answered yesterday. 
February 24, 2013, 03:35:58 AM
Just joined, put all my stuff into this pool! Going to upgrade soon probably.
January 30, 2013, 12:46:11 PM
Some cosmetic changes in order to rationalize.
- Default threshold for automatic withdrawal was set to 5 BTC.
- For existing accounts without defined automatic withdrawal threshold it also will be set to 5 BTC.
- The upper limit of the threshold for an automatic withdrawal introduced, now it's 10 BTC. Users can't set higher value.
January 26, 2013, 02:02:25 PM
Quote
Average pool speed for 10 minutes ~ 612.12 Gh/s.
January 26, 2013, 04:36:08 AM
520 GHash/s. 
Jump to: