In this version of #bisteemit, and as requested by @inquiringtimes, and being a bidbot user myself, let's look at the return on investment or ROIs (I'm not sure if that's the correct term) for the different bid bots available.
Due to the large number of bots available, I trimmed down the scope to the top 4 bots with the highest vote values. And they are:
(data retrieved from steembot tracker 2017/11/03 23:14 UTC+8)
1.1. Computation of ROI
The ROI assumes a 75% author reward and a 25% curation reward. ROI is computed as follows:
ROI = (author reward - amount sent) / amount sent
I sent $1 SBD, and the bot's vote value is $2, the bot vote value will be split into a 75% author reward ($ 1.5) and 25% curation reward ($0.5). Which will give us an ROI of $0.5 or 50%.
ROI = ($1.5 - $1.0) / $1.0 = 0.5 or 50%
1.2. Extracted Data
The data extracted was for 1 week (from 2017-10-26 to 2017-11-01). Data was extracted on 2017-11-02 15:47 to 15:55 (UTC + 8).
1.3. Deleted Data
When I extracted the data, there were data wherein the user sent multiple times to the same bot within the same time frame. I call these 'dirty data' and were excluded from the data analyzed.
Out of the 3000+ data analyzed, this was around 100+. You can look at the raw extracted data in the Github repository shared at the end of this post.
1.4. Excluded Guilds
As pointed out by @buggedout in the comments below, this does not take into consideration the front-runner guilds that these bots may have.
With these down, let's start.
Again, before looking into the details, let's look at the performance of the bidbots.
We can see here that there are days that the bots are profitable, and there are days they're not. @bellyrub, the bot with the highest vote value, is most profitable on Wednesdays. While @booster, the bot with the lowest vote value, is profitable on all days of the week. Here's the data in table format:
3. Individual Performances
Let us now look into the individual performance of the bots.
The graph on the left are stats for each weekday. While the stats on the right breaks it down into weekday and time.
We can see here that @bellyrub is most profitable on Wednesdays, around 1400H.
Let us now check @buildawhale's performance.
We can see here that @buildawhale's most profitable day is on Thursdays. But the peak is on Saturdays, around 0400H and 1800H.
Let us now check @booster's performance.
We can see here that on average, you lose when you use @booster. The possible time you'll get a positive ROI is on Mondays, around 0700H with an 80% ROI.
And last, but not the least, @boomerang.
We can see here that even though @boomerang, has the least vote value of $14.83, you'll see that you'll get a positive ROI on all days of the week.
Zooming in further on the time, the best time to bid is BEFORE the bot votes on Mondays around 21:00H where you can get 204% ROI, and BEFORE the bot votes on Saturdays 22:00H where you may get a 209% ROI.
Here, we've looked into four bidbots that have the highest vote values in Steemit. We saw here that even @boomerang has the lowest vote value, it can give you an average positive ROI of 33% on all days of the week. While one the contrary, on average, you lose when you bid on @booster.
@bellyrub, the one with the highest vote value, is most profitable on Wednesdays, while the next highest voter @buildawhale gives a 24% ROI on Thursdays.
Again, I don't recommend using these bots if you don't know what you're doing and you don't know the performance of the bots. These statistics and data change over time and the scope of the data analyzed is only for one week. I only provide this data to give you an idea (a benchmark perhaps) of the performance of these bots. Please use them at your own risk.
These data are based only on past data and is not meant to be used to forecast future performances.
6. Open Source
For transparency, all extracted data and SQL are uploaded in the ff. github repository:
I am part of a Steemit Business Intelligence community. We all post under the tag #bisteemit. If you have an analysis you would like carried out on Steemit data, please do contact me or any of the #bisteemit team and we will do our best to help you...
Data retrieved from steemsql by @arcange.