Jeez... 24 hours+ and still nothing. Has this happened before were a block has taken this long to find?
Yes, many times. Nothing extraordinary here.
I'm honestly getting ready to jump ship and move to another pool.
Topic: Bitminter bitcoin mining pool - shutdown mining 2020-07-01 website 2021-06-01 - page 76. (Read 324945 times)
October 29, 2014, 07:40:40 AM
Jeez... 24 hours+ and still nothing. Has this happened before were a block has taken this long to find?
Yes, many times. Nothing extraordinary here.
I'm honestly getting ready to jump ship and move to another pool.
October 29, 2014, 06:40:20 AM
Jeez... 24 hours+ and still nothing. Has this happened before were a block has taken this long to find?
Yes, many times. Nothing extraordinary here.
October 29, 2014, 12:58:22 AM
hi dear i have some problem !!!!!!!!
Can you help me what can i do
2014-10-28 14:17 2h 34m 35,985,640,265 being paid now 1,672.0 1,982.3 4,279,296
2014-10-28 11:42 2h 32m 35,985,640,265 being paid now 1,695.8 1,961.6 4,178,944
2014-10-28 09:09 2h 31m 35,985,640,265 being paid now 1,710.7 1,991.4 4,204,544
2014-10-28 06:38 2h 30m 35,985,640,265 being paid now 1,713.3 2,039.7 4,286,464
2014-10-28 04:07 2h 29m 35,985,640,265 being paid now 1,722.3 1,943.2 4,064,256
2014-10-28 01:37 2h 30m 35,985,640,265 being paid now 1,719.0 1,999.2 4,190,208
2014-10-27 23:07 2h 33m 35,985,640,265 being paid now 1,680.6 2,013.8 4,313,088
2014-10-27 20:33 2h 32m 35,985,640,265 being paid now 1,689.3 1,991.7 4,255,744
2014-10-27 18:00 2h 29m 35,985,640,265 being paid now 1,723.5 1,989.8 4,158,464
2014-10-27 15:30 2h 32m 35,985,640,265 being paid now 1,695.0 1,964.7 4,172,800
2014-10-27 12:57 2h 31m 35,985,640,265 0.00000000 1,702.8 1,984.0 4,194,304
2014-10-27 10:26 2h 30m 35,985,640,265 0.00000000 1,714.6 1,983.5 4,178,944
2014-10-27 07:54 2h 00m 35,985,640,265 0.00000000 2,134.0 1,954.8 3,298,304
2014-10-27 05:53 1h 31m 35,985,640,265 0.00000000 2,820.0 2,037.8 2,600,960
2014-10-27 04:21 2h 06m 35,985,640,265 0.00000000 2,035.0 1,968.7 3,483,648
2014-10-27 02:14 2h 29m 35,985,640,265 0.00000000
Can you help me what can i do
2014-10-28 14:17 2h 34m 35,985,640,265 being paid now 1,672.0 1,982.3 4,279,296
2014-10-28 11:42 2h 32m 35,985,640,265 being paid now 1,695.8 1,961.6 4,178,944
2014-10-28 09:09 2h 31m 35,985,640,265 being paid now 1,710.7 1,991.4 4,204,544
2014-10-28 06:38 2h 30m 35,985,640,265 being paid now 1,713.3 2,039.7 4,286,464
2014-10-28 04:07 2h 29m 35,985,640,265 being paid now 1,722.3 1,943.2 4,064,256
2014-10-28 01:37 2h 30m 35,985,640,265 being paid now 1,719.0 1,999.2 4,190,208
2014-10-27 23:07 2h 33m 35,985,640,265 being paid now 1,680.6 2,013.8 4,313,088
2014-10-27 20:33 2h 32m 35,985,640,265 being paid now 1,689.3 1,991.7 4,255,744
2014-10-27 18:00 2h 29m 35,985,640,265 being paid now 1,723.5 1,989.8 4,158,464
2014-10-27 15:30 2h 32m 35,985,640,265 being paid now 1,695.0 1,964.7 4,172,800
2014-10-27 12:57 2h 31m 35,985,640,265 0.00000000 1,702.8 1,984.0 4,194,304
2014-10-27 10:26 2h 30m 35,985,640,265 0.00000000 1,714.6 1,983.5 4,178,944
2014-10-27 07:54 2h 00m 35,985,640,265 0.00000000 2,134.0 1,954.8 3,298,304
2014-10-27 05:53 1h 31m 35,985,640,265 0.00000000 2,820.0 2,037.8 2,600,960
2014-10-27 04:21 2h 06m 35,985,640,265 0.00000000 2,035.0 1,968.7 3,483,648
2014-10-27 02:14 2h 29m 35,985,640,265 0.00000000
There is no problem. Everyone's shifts look like that because it has been more than 10 shifts since we have found a block. You need to read about how PPLNS works. We get paid when the pool finds a block and it is based on our work over the last 10 shifts so if more than 10 shifts have passed since we have found a block there will be shifts not used to calculate our pay when we do find a block.
Aaron
Jeez... 24 hours+ and still nothing. Has this happened before were a block has taken this long to find?
October 28, 2014, 06:16:43 PM
Hope he stays so blocks can be faster, welcom back Koi..
Koi is a small fish (pun intended) compared to when netdomain drops in.
I think Koi uses Bitminter as a backup pool and read something about netdomain pointing his hash here when it's not rented.
October 28, 2014, 04:14:30 PM
Hope he stays so blocks can be faster, welcom back Koi..
October 28, 2014, 04:11:57 PM
Been a while since we've seen that name towards the top of the leader board, welcome back to Koi ...
October 28, 2014, 03:20:58 PM
You see Doc, it does not matter what stats you give it will always create issues for someone. I fully understand the system but still think it looks bad to have zeros on the shift page. You are essentially saying those shifts were worthless, in contradiction to your police searching for someone analogy. Those shifts aren't worthless but putting a zero beside them definitely makes them appear to be. Maybe instead of zeros you should be putting something along the lines of "Not used in calculation due to long block" (or something less wordy) and make it a link to an explanation of PPLNS.
Aaron
Aaron
October 28, 2014, 03:09:12 PM
hi dear i have some problem !!!!!!!!
Can you help me what can i do
2014-10-28 14:17 2h 34m 35,985,640,265 being paid now 1,672.0 1,982.3 4,279,296
2014-10-28 11:42 2h 32m 35,985,640,265 being paid now 1,695.8 1,961.6 4,178,944
2014-10-28 09:09 2h 31m 35,985,640,265 being paid now 1,710.7 1,991.4 4,204,544
2014-10-28 06:38 2h 30m 35,985,640,265 being paid now 1,713.3 2,039.7 4,286,464
2014-10-28 04:07 2h 29m 35,985,640,265 being paid now 1,722.3 1,943.2 4,064,256
2014-10-28 01:37 2h 30m 35,985,640,265 being paid now 1,719.0 1,999.2 4,190,208
2014-10-27 23:07 2h 33m 35,985,640,265 being paid now 1,680.6 2,013.8 4,313,088
2014-10-27 20:33 2h 32m 35,985,640,265 being paid now 1,689.3 1,991.7 4,255,744
2014-10-27 18:00 2h 29m 35,985,640,265 being paid now 1,723.5 1,989.8 4,158,464
2014-10-27 15:30 2h 32m 35,985,640,265 being paid now 1,695.0 1,964.7 4,172,800
2014-10-27 12:57 2h 31m 35,985,640,265 0.00000000 1,702.8 1,984.0 4,194,304
2014-10-27 10:26 2h 30m 35,985,640,265 0.00000000 1,714.6 1,983.5 4,178,944
2014-10-27 07:54 2h 00m 35,985,640,265 0.00000000 2,134.0 1,954.8 3,298,304
2014-10-27 05:53 1h 31m 35,985,640,265 0.00000000 2,820.0 2,037.8 2,600,960
2014-10-27 04:21 2h 06m 35,985,640,265 0.00000000 2,035.0 1,968.7 3,483,648
2014-10-27 02:14 2h 29m 35,985,640,265 0.00000000
Can you help me what can i do
2014-10-28 14:17 2h 34m 35,985,640,265 being paid now 1,672.0 1,982.3 4,279,296
2014-10-28 11:42 2h 32m 35,985,640,265 being paid now 1,695.8 1,961.6 4,178,944
2014-10-28 09:09 2h 31m 35,985,640,265 being paid now 1,710.7 1,991.4 4,204,544
2014-10-28 06:38 2h 30m 35,985,640,265 being paid now 1,713.3 2,039.7 4,286,464
2014-10-28 04:07 2h 29m 35,985,640,265 being paid now 1,722.3 1,943.2 4,064,256
2014-10-28 01:37 2h 30m 35,985,640,265 being paid now 1,719.0 1,999.2 4,190,208
2014-10-27 23:07 2h 33m 35,985,640,265 being paid now 1,680.6 2,013.8 4,313,088
2014-10-27 20:33 2h 32m 35,985,640,265 being paid now 1,689.3 1,991.7 4,255,744
2014-10-27 18:00 2h 29m 35,985,640,265 being paid now 1,723.5 1,989.8 4,158,464
2014-10-27 15:30 2h 32m 35,985,640,265 being paid now 1,695.0 1,964.7 4,172,800
2014-10-27 12:57 2h 31m 35,985,640,265 0.00000000 1,702.8 1,984.0 4,194,304
2014-10-27 10:26 2h 30m 35,985,640,265 0.00000000 1,714.6 1,983.5 4,178,944
2014-10-27 07:54 2h 00m 35,985,640,265 0.00000000 2,134.0 1,954.8 3,298,304
2014-10-27 05:53 1h 31m 35,985,640,265 0.00000000 2,820.0 2,037.8 2,600,960
2014-10-27 04:21 2h 06m 35,985,640,265 0.00000000 2,035.0 1,968.7 3,483,648
2014-10-27 02:14 2h 29m 35,985,640,265 0.00000000
There is no problem. Everyone's shifts look like that because it has been more than 10 shifts since we have found a block. You need to read about how PPLNS works. We get paid when the pool finds a block and it is based on our work over the last 10 shifts so if more than 10 shifts have passed since we have found a block there will be shifts not used to calculate our pay when we do find a block.
Aaron
October 28, 2014, 11:29:16 AM
hi dear i have some problem !!!!!!!!
Can you help me what can i do
2014-10-28 14:17 2h 34m 35,985,640,265 being paid now 1,672.0 1,982.3 4,279,296
2014-10-28 11:42 2h 32m 35,985,640,265 being paid now 1,695.8 1,961.6 4,178,944
2014-10-28 09:09 2h 31m 35,985,640,265 being paid now 1,710.7 1,991.4 4,204,544
2014-10-28 06:38 2h 30m 35,985,640,265 being paid now 1,713.3 2,039.7 4,286,464
2014-10-28 04:07 2h 29m 35,985,640,265 being paid now 1,722.3 1,943.2 4,064,256
2014-10-28 01:37 2h 30m 35,985,640,265 being paid now 1,719.0 1,999.2 4,190,208
2014-10-27 23:07 2h 33m 35,985,640,265 being paid now 1,680.6 2,013.8 4,313,088
2014-10-27 20:33 2h 32m 35,985,640,265 being paid now 1,689.3 1,991.7 4,255,744
2014-10-27 18:00 2h 29m 35,985,640,265 being paid now 1,723.5 1,989.8 4,158,464
2014-10-27 15:30 2h 32m 35,985,640,265 being paid now 1,695.0 1,964.7 4,172,800
2014-10-27 12:57 2h 31m 35,985,640,265 0.00000000 1,702.8 1,984.0 4,194,304
2014-10-27 10:26 2h 30m 35,985,640,265 0.00000000 1,714.6 1,983.5 4,178,944
2014-10-27 07:54 2h 00m 35,985,640,265 0.00000000 2,134.0 1,954.8 3,298,304
2014-10-27 05:53 1h 31m 35,985,640,265 0.00000000 2,820.0 2,037.8 2,600,960
2014-10-27 04:21 2h 06m 35,985,640,265 0.00000000 2,035.0 1,968.7 3,483,648
2014-10-27 02:14 2h 29m 35,985,640,265 0.00000000
Can you help me what can i do
2014-10-28 14:17 2h 34m 35,985,640,265 being paid now 1,672.0 1,982.3 4,279,296
2014-10-28 11:42 2h 32m 35,985,640,265 being paid now 1,695.8 1,961.6 4,178,944
2014-10-28 09:09 2h 31m 35,985,640,265 being paid now 1,710.7 1,991.4 4,204,544
2014-10-28 06:38 2h 30m 35,985,640,265 being paid now 1,713.3 2,039.7 4,286,464
2014-10-28 04:07 2h 29m 35,985,640,265 being paid now 1,722.3 1,943.2 4,064,256
2014-10-28 01:37 2h 30m 35,985,640,265 being paid now 1,719.0 1,999.2 4,190,208
2014-10-27 23:07 2h 33m 35,985,640,265 being paid now 1,680.6 2,013.8 4,313,088
2014-10-27 20:33 2h 32m 35,985,640,265 being paid now 1,689.3 1,991.7 4,255,744
2014-10-27 18:00 2h 29m 35,985,640,265 being paid now 1,723.5 1,989.8 4,158,464
2014-10-27 15:30 2h 32m 35,985,640,265 being paid now 1,695.0 1,964.7 4,172,800
2014-10-27 12:57 2h 31m 35,985,640,265 0.00000000 1,702.8 1,984.0 4,194,304
2014-10-27 10:26 2h 30m 35,985,640,265 0.00000000 1,714.6 1,983.5 4,178,944
2014-10-27 07:54 2h 00m 35,985,640,265 0.00000000 2,134.0 1,954.8 3,298,304
2014-10-27 05:53 1h 31m 35,985,640,265 0.00000000 2,820.0 2,037.8 2,600,960
2014-10-27 04:21 2h 06m 35,985,640,265 0.00000000 2,035.0 1,968.7 3,483,648
2014-10-27 02:14 2h 29m 35,985,640,265 0.00000000
October 28, 2014, 09:24:37 AM
Holy moly! All my miners suddenly disappeared from the pool! What happened? 
October 27, 2014, 03:31:06 PM
Looks like good old DDoS attacks are back.
Some users got blocked along with the attacker as DDoS filtering kicked in.
Should be back to normal again now.
Some users got blocked along with the attacker as DDoS filtering kicked in.
Should be back to normal again now.
October 27, 2014, 03:24:02 PM
There was a few seconds outage on the main server (mint.bitminter.com) about an hour ago. It was barely long enough for the pool hashrate to drop a bit and go back up.
It looks like it's having some problems again now. I'm looking into it right now.
The second server, us2.bitminter.com:3333 is running normally.
It looks like it's having some problems again now. I'm looking into it right now.
The second server, us2.bitminter.com:3333 is running normally.
October 27, 2014, 01:49:36 PM
Howdy,
My very first post here.. I've only been mining about 3 weeks (on an antminer s3).
Doc - I am very impressed with your system.. Whilst it was a 'strange new world' as the start, after some research and reading it all makes sense now.
I have no issues with the payout system. After studying the methods and process it all makes sense to me.
I am getting slightly less payouts than my first day.. but I understand that the pool size is growing so my percentage is dropping.. the benefit is that we hit more blocks as there's more effort in the pool - so on average my payout if fairly stable.
I do understand the renters concerns.. I guess if their rental expired in the past they'd still get a percentage of income for the next 9 shifts 9x3=27hrs.. where as in the past it'd be 9x10=90hrs.. still - I guess that is the risk of intermittent mining.
Just wanted to say that not everyone has complaints.. maybe a few stickys at the start of the forum that read 'before you complain about payouts/shifts read here'.. that explain the PPLNS and shifts and stuff might help everyone out.
Many Thanks for your fine system
erosco
Welcome to the party. I share your sentiments completely
October 27, 2014, 06:52:58 AM
Did you change the IP address? Having problems reaching mint.bitminter.com and www.bitminter.com.
No, nothing changed.
Not sure why you get the OCSP error at https://bitminter.com - which browser are you using?
You are also unable to mine at mint.bitminter.com:3333 ? Everything looks normal there, including the number of active connections and users mining.
Are other sites working ok for you right now?
October 27, 2014, 06:10:29 AM
Did you change the IP address? Having problems reaching mint.bitminter.com and www.bitminter.com.
I might have to reboot my router again (I think my ISP might be slowing down my connection or something). 2824ms ping!
Code:
Secure Connection Failed
An error occurred during a connection to www.bitminter.com. The OCSP response contains out-of-date information. (Error code: sec_error_ocsp_old_response)
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the web site owners to inform them of this problem.
I might have to reboot my router again (I think my ISP might be slowing down my connection or something). 2824ms ping!
October 26, 2014, 02:15:28 PM
Mining server maintenance will take place friday 2014.10.31 from 11:00 CET to 11:15 CET.
Expected downtime 1 minute on each server (mint/us1 and us2).
Only one server will be upgraded at a time.
You will probably not notice any changes. But there are some you may notice:
- Default extranonce2 size 4 (was 6) bytes on mint/us1.
If you don't know what this is then you can safely ignore it.
If you need an extranonce2 size above 4 bytes please set that in your worker settings
at bitminter.com now.
- After the initial rampup when you connect, the server will change difficulty less often.
This should make half-broken clients happier. If your mining client is severely broken, you should set a high minimum difficulty in your worker settings at bitminter.com. For example if your worker difficulty is sometimes 32 and sometimes 64, then set 128 or 256 and you can probably avoid difficulty changes altogether.
- Starting difficulty 16 (was 4)
- Minimum difficulty 4 (was 2)
- Maximum difficulty 524288 (was 131072)
Adjusting settings to follow the development in hashpower. It would have been nice to set starting and minimum difficulty higher, but we have a lot of users with very low hashpower, so let's wait with that a little longer. Remember you can always set a higher minimum difficulty for your workers in the worker settings at bitminter.com. Not normally needed, but very useful if you have a mining client that cannot handle low difficulty or difficulty changes.
Expected downtime 1 minute on each server (mint/us1 and us2).
Only one server will be upgraded at a time.
You will probably not notice any changes. But there are some you may notice:
- Default extranonce2 size 4 (was 6) bytes on mint/us1.
If you don't know what this is then you can safely ignore it.
If you need an extranonce2 size above 4 bytes please set that in your worker settings
at bitminter.com now.
- After the initial rampup when you connect, the server will change difficulty less often.
This should make half-broken clients happier. If your mining client is severely broken, you should set a high minimum difficulty in your worker settings at bitminter.com. For example if your worker difficulty is sometimes 32 and sometimes 64, then set 128 or 256 and you can probably avoid difficulty changes altogether.
- Starting difficulty 16 (was 4)
- Minimum difficulty 4 (was 2)
- Maximum difficulty 524288 (was 131072)
Adjusting settings to follow the development in hashpower. It would have been nice to set starting and minimum difficulty higher, but we have a lot of users with very low hashpower, so let's wait with that a little longer. Remember you can always set a higher minimum difficulty for your workers in the worker settings at bitminter.com. Not normally needed, but very useful if you have a mining client that cannot handle low difficulty or difficulty changes.
October 24, 2014, 02:53:14 AM
Sheesh, talk about putting words in my mouth.
I did not mean to put words in your mouth. I apologize. Not being experienced with PPLNS you probably didn't see it, but what you said the big renters are doing would require them to know the future.
If you want to know more about pool hopping and mining reward systems you can read here: http://bitcoin.stackexchange.com/questions/5072/what-is-pool-hopping
The top answer is written by Meni Rosenfeld and contains a link to his analysis of mining pool reward systems, which you can read if you want to get into the details.
You get paid as a pool op to explain luck and how PPLNS works over, and over, and over ad nauseam
Noooooooooooo...
I need to use bitcoin stackexchange more. I can just copy-paste the questions in and let someone else answer for me.
I think the entire shift thing simply confuses people. I actually ignore the shift concept when I look at things. I think if there was a way to eliminate shifts and get paid for your contribution per block, it would simplify things.
I agree it would simplify and I wish it was possible. But what you describe is the proportional reward system, which is vulnerable to pool hopping (see link above).
My very first post here.. I've only been mining about 3 weeks (on an antminer s3).
Welcome to the pool, and thanks for the kind words.
I am getting slightly less payouts than my first day.. but I understand that the pool size is growing so my percentage is dropping.. the benefit is that we hit more blocks as there's more effort in the pool - so on average my payout if fairly stable.
Yeah, as pool hashrate goes up your average income is the same but the variance decreases. More info here: http://bitcoin.stackexchange.com/questions/10731/mining-pool-hashrate-effect-on-a-miners-income
But note that your income will be going down if your hashrate stays the same, as the difficulty keeps increasing as long as more ASIC machines are built and start mining.
How fast is global hashpower growing: http://bitcoin.sipa.be/
How does that affect you: http://bitcoin.stackexchange.com/questions/16526/how-does-a-difficulty-increase-affect-a-miners-income
October 24, 2014, 01:34:39 AM
Howdy,
My very first post here.. I've only been mining about 3 weeks (on an antminer s3).
Doc - I am very impressed with your system.. Whilst it was a 'strange new world' as the start, after some research and reading it all makes sense now.
I have no issues with the payout system. After studying the methods and process it all makes sense to me.
I am getting slightly less payouts than my first day.. but I understand that the pool size is growing so my percentage is dropping.. the benefit is that we hit more blocks as there's more effort in the pool - so on average my payout if fairly stable.
I do understand the renters concerns.. I guess if their rental expired in the past they'd still get a percentage of income for the next 9 shifts 9x3=27hrs.. where as in the past it'd be 9x10=90hrs.. still - I guess that is the risk of intermittent mining.
Just wanted to say that not everyone has complaints.. maybe a few stickys at the start of the forum that read 'before you complain about payouts/shifts read here'.. that explain the PPLNS and shifts and stuff might help everyone out.
Many Thanks for your fine system
erosco
October 23, 2014, 08:13:08 PM
I think the entire shift thing simply confuses people. I actually ignore the shift concept when I look at things. I think if there was a way to eliminate shifts and get paid for your contribution per block, it would simplify things.
block 151 start
12:01am
1am 0 hashes
2am 0 hashes
3am 134 hashes
4am 5000 hashes
5am 576 hashes
6am 0 hashes
7am 0 hashes
8am 0 hashes
9am 0hashes
10am 0 hashes
10:33am block 151 found
10:33am block 152 starts
11am 0 hashes
12:01pm 0 hashes
ect ect ect
say the hunt for block 151 started at midnight and it was discovered at 10:33am hour.
Lets say a pool hopper jumped in during the 3am hour and left during the 5am hour.
His total contribution would be 5710 hashes for the time he spent here.
Even though his time here was short he still contributed some hash to the pool.
His share of pay would be equal to the percentage of his contribution.
Each block requires a different amount of hash to discover.
Say this block only took 11,000,000,000 hash to find.
His pay would be 5710/11,000,000,000*25btc=0.0000129772727273
Now say that block took 24 hours to find, and it took 37,000,000,000 hashes to discover.
The hoppers cut would go down because he only contributed 5710 hashes to that block.
His pay would now only be 5710/37,000,000,000*25btc= 0.0000038581081081
Since the blocks being found is simple chance of luck, time is irrelevant other then to see
How long its taking to find the next block, thusly making shifts pointless in my opinion.
block 151 start
12:01am
1am 0 hashes
2am 0 hashes
3am 134 hashes
4am 5000 hashes
5am 576 hashes
6am 0 hashes
7am 0 hashes
8am 0 hashes
9am 0hashes
10am 0 hashes
10:33am block 151 found
10:33am block 152 starts
11am 0 hashes
12:01pm 0 hashes
ect ect ect
say the hunt for block 151 started at midnight and it was discovered at 10:33am hour.
Lets say a pool hopper jumped in during the 3am hour and left during the 5am hour.
His total contribution would be 5710 hashes for the time he spent here.
Even though his time here was short he still contributed some hash to the pool.
His share of pay would be equal to the percentage of his contribution.
Each block requires a different amount of hash to discover.
Say this block only took 11,000,000,000 hash to find.
His pay would be 5710/11,000,000,000*25btc=0.0000129772727273
Now say that block took 24 hours to find, and it took 37,000,000,000 hashes to discover.
The hoppers cut would go down because he only contributed 5710 hashes to that block.
His pay would now only be 5710/37,000,000,000*25btc= 0.0000038581081081
Since the blocks being found is simple chance of luck, time is irrelevant other then to see
How long its taking to find the next block, thusly making shifts pointless in my opinion.
October 23, 2014, 07:34:56 PM
STRONGENOUGH24: I'm not a fan of the large hash renters myself. They do make it look like your getting paid less, but that's only because with their rented power, they're contributing more, which in turn reduces your percentage of the contribution for that block. However, because of their contribution, it helped find that block faster, which in turn will start us onto the next block sooner allowing us to find that one sooner. So in the long run, even though your cut on an individual block is less, your getting more blocks faster, so in turn, things level out and your still making the same amount, just in smaller chunks.
Jump to: