Quote from: Darkz0r on December 16, 2017, 02:05:50 PM

I'm not the author but this seems really useful regarding pools: https://docs.google.com/spreadsheets/d/15W5EuyMo7zO4SxysxmRUp3NT7nKoyyI99rZAeRBKbyY/edit#gid=514488770

In the end, doesn't seem to matter much.

Quote from: srcrypt on November 16, 2017, 12:32:59 AM

Now it's BTCchina and F2 pool.
https://2.bp.blogspot.com/-Tfnosr3w7gM/WgzbmgpB__I/AAAAAAAEqaE/MdY1LkpDvuofuu6LEnO57VbyvmpfJ1wtQCLcBGAs/s1600/main%2B11.jpg

【Best Mining Pool Settings for Hashflare (updated daily)】
https://docs.google.com/spreadsheets/d/15W5EuyMo7zO4SxysxmRUp3NT7nKoyyI99rZAeRBKbyY/edit?usp=sharing

Quote from: rockmoney on December 10, 2017, 02:54:18 AM

Quote from: srcrypt on November 16, 2017, 12:32:59 AM

Now it's BTCchina and F2 pool.
https://2.bp.blogspot.com/-Tfnosr3w7gM/WgzbmgpB__I/AAAAAAAEqaE/MdY1LkpDvuofuu6LEnO57VbyvmpfJ1wtQCLcBGAs/s1600/main%2B11.jpg

【Best Mining Pool Settings for Hashflare (updated daily)】
https://docs.google.com/spreadsheets/d/15W5EuyMo7zO4SxysxmRUp3NT7nKoyyI99rZAeRBKbyY/edit?usp=sharing

So, a few days of mining have passed since I switched my pool settings on hashflare based in part from your data. Not sure how I didn't notice this before, but the numbers in your Google doc differ from the "Revenue per 1 TH/s" reported by hashflare on my dashboard. For instance, I have been using 100% f2pool for the last few days, and here are the numbers from the "Revenue per 1 TH/s" section as reported in my dashboard:

08.12 [08 DECEMBER 2017]: 0.00014858 BTC per 1 TH/s on 07.12.17 [07 DECEMBER 2017]
09.12 [09 DECEMBER 2017]: 0.00015635 BTC per 1 TH/s on 08.12.17 [08 DECEMBER 2017]
10.12 [10 DECEMBER 2017]: 0.00014912 BTC per 1 TH/s on 09.12.17 [09 DECEMBER 2017]

As you can see when comparing both sets of data, although our numbers should be the same, they are in fact quite different. This means hashflare could be scamming their customers, or we are using different sets of data. Can you please specify where and how you are obtaining the numbers in your Google doc?

This could potentially be a malicious method used by hashflare in order to increase their profits by reporting inaccurate data to their customers. Before any accusations can be made, we need to first figure a few things out. Most importantly is if Bitcoin payouts are all paid out to users at the same time. Unfortunately, there is little information in their "Help" section, but here are two important factors found in the "FAQ" section that we need more specifics on (mainly the time Bitcoin/SHA256 payouts are made):

How does pool allocation happen and work?
Our equipment is set up to work with a number of pools. When you select a specific pool and the hashrate percent allocated to it, our system begins to use that amount of hashrate in the selected pool. The accounting happens daily, thus you are able to change the pools once a day. After the system calculates your hashrate's input and the total payout from that pool you will be given your share of the mined BTC.

I have purchased some hashrate. When will I get a payout?
All payouts occur once per day. You will receive your first payout within 24 hours after the purchase. Afterward, the payouts continue daily.

The payouts are made from 00:00 to 09:00 UTC.

Although it does not specifically state the details of their payout times, I would assume that all payments are issued at the same time based on algorithm between 00:00 to 09:00 UTC, based on the FAQ above. Hopefully someone has an accurate answer!

Quote from: decie on August 24, 2017, 05:38:15 PM

this thread would be a lot more useful if people posted the revenue per 1 TH/s which they give you in the panel (BTC value changes so it next to useless looking back over how the pools are preforming)

I agree 100%, and it would be in the best interests of all hashflare users to begin reporting this information here! The most important piece of data is the value of "Revenue per 1 TH/s", along with the date. It seems the majority of people using this thread have purchased SHA256/Bitcoin contracts, but feel free to report the "Revenue per 1 TH/s | MH/s | H/s" for any algorithm (just be sure to specify when posting).

Quote from: rockmoney on December 11, 2017, 09:03:02 PM

Quote from: pivara on December 10, 2017, 06:00:34 AM

Can anyone help me optimize my pool allocation? I only bought the contract a week ago and the only pools that I have are Slush, BTCC and BW. I've been watching the % of blocks solved on Bitcoin Block Explorer and Blocktrail and they showed that Slush was essentially solving nearly DOUBLE that of BTCC and BW combined, however, when I used Slush at 100% I got the worst results. Now I'm trying to find the sweetspot but it's taking some time and effort. I really hate the idea of losing anything with the way the price is going and will go.

You have to keep the pool fees/rates in mind for accurate calculations. Although Slush might be finding more blocks than the other available pools, there is a 2% fee on slushpool, whereas there are negative fees on others. You also have to account for the mining payout structure - pay per share (PPS), pay per last N shares (PPLNS), score based (slush), etc.. Trying to calculate or forecast mining income with hashflare would essentially be impossible.

Quote from: rockmoney on December 10, 2017, 02:54:18 AM

Quote from: srcrypt on November 16, 2017, 12:32:59 AM

Now it's BTCchina and F2 pool.
https://2.bp.blogspot.com/-Tfnosr3w7gM/WgzbmgpB__I/AAAAAAAEqaE/MdY1LkpDvuofuu6LEnO57VbyvmpfJ1wtQCLcBGAs/s1600/main%2B11.jpg

【Best Mining Pool Settings for Hashflare (updated daily)】
https://docs.google.com/spreadsheets/d/15W5EuyMo7zO4SxysxmRUp3NT7nKoyyI99rZAeRBKbyY/edit?usp=sharing

So, a few days of mining have passed since I switched my pool settings on hashflare based in part from your data. Not sure how I didn't notice this before, but the numbers in your Google doc differ from the "Revenue per 1 TH/s" reported by hashflare on my dashboard. For instance, I have been using 100% f2pool for the last few days, and here are the numbers from the "Revenue per 1 TH/s" section as reported in my dashboard:

08.12 [08 DECEMBER 2017]: 0.00014858 BTC per 1 TH/s on 07.12.17 [07 DECEMBER 2017]
09.12 [09 DECEMBER 2017]: 0.00015635 BTC per 1 TH/s on 08.12.17 [08 DECEMBER 2017]
10.12 [10 DECEMBER 2017]: 0.00014912 BTC per 1 TH/s on 09.12.17 [09 DECEMBER 2017]

As you can see when comparing both sets of data, although our numbers should be the same, they are in fact quite different. This means hashflare could be scamming their customers, or we are using different sets of data. Can you please specify where and how you are obtaining the numbers in your Google doc?

This could potentially be a malicious method used by hashflare in order to increase their profits by reporting inaccurate data to their customers. Before any accusations can be made, we need to first figure a few things out. Most importantly is if Bitcoin payouts are all paid out to users at the same time. Unfortunately, there is little information in their "Help" section, but here are two important factors found in the "FAQ" section that we need more specifics on (mainly the time Bitcoin/SHA256 payouts are made):

How does pool allocation happen and work?
Our equipment is set up to work with a number of pools. When you select a specific pool and the hashrate percent allocated to it, our system begins to use that amount of hashrate in the selected pool. The accounting happens daily, thus you are able to change the pools once a day. After the system calculates your hashrate's input and the total payout from that pool you will be given your share of the mined BTC.

I have purchased some hashrate. When will I get a payout?
All payouts occur once per day. You will receive your first payout within 24 hours after the purchase. Afterward, the payouts continue daily.
her
The payouts are made from 00:00 to 09:00 UTC.

Although it does not specifically state the details of their payout times, I would assume that all payments are issued at the same time based on algorithm between 00:00 to 09:00 UTC, based on the FAQ above. Hopefully someone has an accurate answer!

Since questioning scrypt in my last post about their data and where they were obtaining it from, most of the rows in the google doc have been deleted. There was also a link in the doc to a hashflare blog here: http://hashflare100.blogspot.jp/. Hopefully scrypt will enlighten us, as the recent removal of data raises even more suspicion!

In the meantime, please keep posting the "Revenue per 1 TH/s" data from your hashflare dashboard, and thanks to everyone who has posted that information already - please continue posting that information as days pass! Getting to the bottom of this has manged to become a priority on my list now that scrypt has deleted data from their google doc without responding to my inquiries! Wink

I know that it can be a real pain sifting though some threads here for information, but this is only 4 pages. Please read everything quoted above, or simply go to page 3 of this thread and read it. That document you linked to is SHADY, and likely inaccurate due to the loads of data that was deleted from it after I asked the original poster where he was obtaining his information. Use it at your own risk, as you have been warned about its legitimacy!

Again, the best thing we can all do to help one another is by simply posting the daily "Revenue per 1 TH/s", including the date, algorithm, and pool allocation as it was set at the time.

17 DECEMBER 2017 (SHA256, 100% f2 Pool): 0.00014536 BTC
18 DECEMBER 2017 (SHA256, 100% f2 Pool): 0.00014838 BTC