seems like we're going to see another day of 100+TH/s dividends, but there are a couple of mature blocks that haven't been moved to the dividend address yet. i see 1 block each at 1HSZ62sk8EdARQihqX46SYXfR3TsT5z8bj and 194FxKRpVf7rPD4v88Nq4vuzdTGbKuzHkW. i wonder if moving of matured coins is manual, cronjob, or polled (doubtful).
EDIT: and...just after I typed that, the coins form 1HSV... moved.
Topic: [PicoStocks] 100TH/s bitcoin mine [100th] - page 20. (Read 470088 times)
Now reported: 169 TH/s
We've finally seen 2 consecutive days of 100+TH/s dividends. thanks, dave and team.
Now reported: 169 TH/s
Here's what I have (some minor errors around diff changes)
(my numbers are based off of deposits to the dividend address)
The thing that I find strange is the consistent up and down between days. I'd expect a bit more variation...not sure what this pattern is attributed to.
(my numbers are based off of deposits to the dividend address)
The thing that I find strange is the consistent up and down between days. I'd expect a bit more variation...not sure what this pattern is attributed to.
This 100th project power calculation. Data loaded from dividend log (any user), this data can't be different with total dividend log, or it was big midstake of 100th/picostocks.
Here is prepared data for building charts.
Next chart show project's power fluctuation between 6-09-2013 and 14-11-2013:
Brief:
* blue line - power calculated each 40 dividend (aprox. 4-5 days) for each dividend payment time
* red line - power calculation for each network difficulty change (most correct and usefull for calculating total dividend payment)
It's showed, that 100th project never reached for declared 100th. And of course for promised 200th, even for a short time.
Here is prepared data for building charts.
Next chart show project's power fluctuation between 6-09-2013 and 14-11-2013:
Brief:
* blue line - power calculated each 40 dividend (aprox. 4-5 days) for each dividend payment time
* red line - power calculation for each network difficulty change (most correct and usefull for calculating total dividend payment)
It's showed, that 100th project never reached for declared 100th. And of course for promised 200th, even for a short time.
(edited)
I've calculated the dividends from the last three days (11th, 12th, 13th Nov) and they are equvalent to >124 TH/s, so it looks like fluctuations in 9th or 10th Nov.
(https://picostocks.com/stocks/bitcoins/19)
I've calculated the dividends from the last three days (11th, 12th, 13th Nov) and they are equvalent to >124 TH/s, so it looks like fluctuations in 9th or 10th Nov.
(https://picostocks.com/stocks/bitcoins/19)
Now: 142 TH/s
Hey, it's lie or mistake!Current calculations via dividends (any owner's dividend log - https://picostocks.com/users/incomes/1325 ):
Quote
0,00002528 13.11.2013 0:40
0,00000259 12.11.2013 21:16
0,00004744 12.11.2013 7:55
0,00000086 12.11.2013 7:35
0,0000473 12.11.2013 6:04
0,00002528 11.11.2013 23:57
0,00009492 11.11.2013 22:19
0,00004733 11.11.2013 21:50
0,0000095 11.11.2013 18:50
0,00000022 11.11.2013 17:50
0,00004766 11.11.2013 10:41
0,00000151 11.11.2013 9:53
0,00002528 11.11.2013 4:25
0,00004731 11.11.2013 0:09
0,00004767 10.11.2013 21:45
0,00000391 10.11.2013 17:49
0,00002528 10.11.2013 11:43
0,00002528 09.11.2013 17:24
0,00000221 09.11.2013 12:47
0,0000016 09.11.2013 1:14
---------------------------
0,00052843 3,976574074 <-- dividend summ and interval in days
diff kk: 510,929
share GH/s: 0,135003508 <-- =(diff_kk*4294967296*summ_btc) / (25*3600*24*days_interval*1000)
total shares: 518271
total TH/s: 69,96840291 <-- =share_ghs*total_shares/1000
It's not fluctuation (such a low power last week), i am watching for it every day last months, and power of project no more 100th (except 2-3 days 155TH/s in 27 Sent 2013) 0,00000259 12.11.2013 21:16
0,00004744 12.11.2013 7:55
0,00000086 12.11.2013 7:35
0,0000473 12.11.2013 6:04
0,00002528 11.11.2013 23:57
0,00009492 11.11.2013 22:19
0,00004733 11.11.2013 21:50
0,0000095 11.11.2013 18:50
0,00000022 11.11.2013 17:50
0,00004766 11.11.2013 10:41
0,00000151 11.11.2013 9:53
0,00002528 11.11.2013 4:25
0,00004731 11.11.2013 0:09
0,00004767 10.11.2013 21:45
0,00000391 10.11.2013 17:49
0,00002528 10.11.2013 11:43
0,00002528 09.11.2013 17:24
0,00000221 09.11.2013 12:47
0,0000016 09.11.2013 1:14
---------------------------
0,00052843 3,976574074 <-- dividend summ and interval in days
diff kk: 510,929
share GH/s: 0,135003508 <-- =(diff_kk*4294967296*summ_btc) / (25*3600*24*days_interval*1000)
total shares: 518271
total TH/s: 69,96840291 <-- =share_ghs*total_shares/1000
Now: 142 TH/s
http://eligius.st/~gateway/ is 0%.
edit - if you look at the last pmt it came from a payout from slush's pool, so looks like they are at least mining some on slush's https://blockchain.info/tx/85791245bfa322ab92a01a1ddcab8c5d665465feed2f5fc203b55afcdec2cf48
edit2 - and there is some mining going on btcguild's pool based on this https://blockchain.info/tx/811b4265f68814acd32ddb80de4c64c524a3ccff55c2873b82122c63fee1d2cb
edit - if you look at the last pmt it came from a payout from slush's pool, so looks like they are at least mining some on slush's https://blockchain.info/tx/85791245bfa322ab92a01a1ddcab8c5d665465feed2f5fc203b55afcdec2cf48
edit2 - and there is some mining going on btcguild's pool based on this https://blockchain.info/tx/811b4265f68814acd32ddb80de4c64c524a3ccff55c2873b82122c63fee1d2cb
3% is highway robbery and pps is for the mathematically impared. If you must "pool-up" then please consider bitmiter: ppnls 1% fees.
Bitminter is good too.
I like PPS because it's simple zero variance. No (well, much less) math required to estimate hashrate.
Anything is better than wasting shares on orphans; that is adding insult to injury!
3% is highway robbery and pps is for the mathematically impared. If you must "pool-up" then please consider bitmiter: ppnls 1% fees.
Slush's pool ~280TH/s 2013-11-08 17:05:18 ---> 2013-11-10 12:16:42 --- 20 blocks solved
Eclipse ~120TH/s 2013-11-08 18:36:17 ---> 2013-11-10 11:16:47 --- 6 blocks solved
100 TH (90-120TH/s) 2013-11-08 17:32:12 ---> 2013-11-10 13:17:00 --- 1 block solved
Dave, Leszek - please comment
Eclipse ~120TH/s 2013-11-08 18:36:17 ---> 2013-11-10 11:16:47 --- 6 blocks solved
100 TH (90-120TH/s) 2013-11-08 17:32:12 ---> 2013-11-10 13:17:00 --- 1 block solved
Dave, Leszek - please comment
This is ridiculous. 100TH is no longer sufficient for solo mining, nor is running a full node our core competence.
Get in a pool and stop wasting the hashes for which we've waited so long.
3% PPS at 50BTC is a great deal. Take it!
yes
Maybe little silly question to post here but can anyone tell me who operator of ghash.io is ?(his ID on bitcointalk)
.It is publicly on the internet...hint.
Anyways, lets stay on topic. As of 11/10/2013 @6:17pm MST. The 100TH mine is at ~123.4TH/s
As pointed out, there is also something wrong with dividend payouts and fees per share. The dividends and fees are inconsistent in values.
At 123.4 TH/s....Thats about 236 MH/s per share. If difficulty was held constant (which we know it will actually increase), $236 MH/s at .02BTC would take 96 days to ROI. Since difficulty will actually increase it will take far more than 96 days to make ROI on .02btc/share
Even at 200TH or 385MH/s per share, it would take 58 days to make ROI if difficulty is held constant. Again, difficulty will change every 10.x days. So 58 days ROI on .02btc is highly unlikely.
It is in 200TH's best interests to increase hashrate to 500TH or 1000TH/s. This would make the mine lucrative for the majority of its shareholders. 200Th is a little too late to the game. The shares are statistically worth 0.02btc or less.
Maybe little silly question to post here but can anyone tell me who operator of ghash.io is ?(his ID on bitcointalk)
What is happening, number of blocks found have dropped of heavily to ~2-3 a day. Also the last couple of dividends seem to be half what a block should be.
Phil
Phil
Use Eligius - zero pool fees, readable stats, fees from transaction in blocks included in payments...
Slush's pool ~280TH/s 2013-11-08 17:05:18 ---> 2013-11-10 12:16:42 --- 20 blocks solved
Eclipse ~120TH/s 2013-11-08 18:36:17 ---> 2013-11-10 11:16:47 --- 6 blocks solved
100 TH (90-120TH/s) 2013-11-08 17:32:12 ---> 2013-11-10 13:17:00 --- 1 block solved
Dave, Leszek - please comment
Eclipse ~120TH/s 2013-11-08 18:36:17 ---> 2013-11-10 11:16:47 --- 6 blocks solved
100 TH (90-120TH/s) 2013-11-08 17:32:12 ---> 2013-11-10 13:17:00 --- 1 block solved
Dave, Leszek - please comment
+1
The behavior of the mine (based on dividend payouts) is fairly strange. Lately, we're seeing barely any blocks get solved. Previously, there was a consistent pattern of a "normal" hash rate day then a low hash rate day then a normal day..always averaging out to less than expected dividends.
I've asked a couple times already and would like to hear your thoughts on going back to full pooled mining.
Slush's pool ~280TH/s 2013-11-08 17:05:18 ---> 2013-11-10 12:16:42 --- 20 blocks solved
Eclipse ~120TH/s 2013-11-08 18:36:17 ---> 2013-11-10 11:16:47 --- 6 blocks solved
100 TH (90-120TH/s) 2013-11-08 17:32:12 ---> 2013-11-10 13:17:00 --- 1 block solved
Dave, Leszek - please comment
Eclipse ~120TH/s 2013-11-08 18:36:17 ---> 2013-11-10 11:16:47 --- 6 blocks solved
100 TH (90-120TH/s) 2013-11-08 17:32:12 ---> 2013-11-10 13:17:00 --- 1 block solved
Dave, Leszek - please comment
Jump to: