And, those ~3 BTC transactions have been fairly consistent since the BWA's creations, as seen here: http://www.walletexplorer.com/address/12HmUEdk3fqz9W4SEf1xjxPqvkGDqAqHyc
That, in spite of it being impossible given the difficulty increases if no further bitcoin miners are added to account for the regular payouts. Also, Josh Zerlan is on record in stating that the payouts are done automatically sans his input, yet these payouts seem to have an ongoing helping hand during the transfer process. (hoping this assessment of mine makes sense)
That's not exactly true, those payouts are consistent with a relatively fixed amount of hardware running and the payout decreasing over time. What is happening is that his payout threshold is set to 3BTC, so every time the balance clicks over 3BTC it gets a payout.That, in spite of it being impossible given the difficulty increases if no further bitcoin miners are added to account for the regular payouts. Also, Josh Zerlan is on record in stating that the payouts are done automatically sans his input, yet these payouts seem to have an ongoing helping hand during the transfer process. (hoping this assessment of mine makes sense)
If you look at the BTC transferred in per day you can see that.
https://blockchain.info/charts/received-per-day?timespan=2year&showDataPoints=false&daysAverageString=1&show_header=true&scale=0&address=12HmUEdk3fqz9W4SEf1xjxPqvkGDqAqHyc
It starts off with a massive income per day, dropping off sharply in Oct last year as the hashrate was exploding. Soon it was 6-9 BTC/day, then 3-6BTC/day, then 3BTC most days, 3BTC every couple days, 3BTC/week, etc. Towards the end of spring/early summer it was earning very little, as you'd expect whatever 65nm hardware they still had to do. Then, in July they get in a bunch of Monarchs for burn in and payouts pick up, starting to space a little further apart again as difficulty rises.
https://blockchain.info/charts/received-per-day?timespan=2year&showDataPoints=false&daysAverageString=1&show_header=true&scale=0&address=12HmUEdk3fqz9W4SEf1xjxPqvkGDqAqHyc
Visualized
