Hi, I'm enjoying this application but the Steem Connect pop-up says verify that you are on the correct URL.

This can be done by right clicking on the iframe and selecting open as a new tab, or view frame source.

For those who want to verify the correct URL each time it's exhausting. It would be great if there was an option to use new tab instead of an iframe.

Edit: This would also make the site work with Brave brave/browser-laptop#13392

Hello @MattyIce,

I started new upvote bot. http://steemit.com/@upyourpost.
And I setup the json_metadata on my upvoting bot @upyourpost.
Why my new bot was not listed on the steembottracker ?
II want to know about how to register my bot to the steembottracker.

Expected behavior

Clicking on the logo shown in the left of the top navigation bar should take you to the home page of the site.

Actual behavior

Clicking on the logo shown in the left of the top navigation bar should takes you to a page that shows a 404 when clicked on certain pages.

How to reproduce

A) Visit https://steembottracker.com/
B) Click on Tools in the top navigation
C) Click on Curation Estimator
D) Once the page has loaded on the curation estimator page, click on the steemtracker logo located at the top left corner of page in the navigation area.

Browser: Google Chrome (Version 63.0.3239.132 (Official Build) (64-bit))
Operating system: MacOS HighSierra Version 10.13

Recording Of The Bug

A video of the bug can be found here: https://d.tube/#!/v/tobias-g/u9ktmw23

The post promoter software now allows a whole bunch of settings which are not currently able to be specified in the bot config or viewed on the site.

Today I see bottracker showing bids invalid that are actually valid and accepted by bot, this misleads bidders.

I just found that the amounts showing for the 'Total Bids' for a variety of bots were higher than their Vote Value and wondered if that was because I had just opened my PC from Sleep mode - where the bot tracker page had been open in the browser before the device went to sleep. It appears that the algorithm on the bot-tracker page doesn't account for these situations, so the data on the page was wrong. After I refreshed the page, the correct data was displayed.

To (probably) recreate:

1. Open Bot Tracker.
2. Put device to sleep.
3. Come back 30+ minutes later.
4. Wake up device.
5. There's a good chance that the displayed data will be different to what displays after a page refresh.

The bottracker curation estimator reward calculations show slight deviations to the steem calculated values. Steem calculates the "weight" of each vote with a formula using the square root of the voter rshares in relation to the sum of all previous voters rshares. A great explanation of the curation reward system was given by @miniature-tiger in:

• An Illustrated Guide to Curation - from the simple to the complex - with real examples from past posts - Part 1
• An Illustrated Guide to Curation - from the simple to the complex - with real examples from past posts - Part 2

The core math is the calculation of

weight = (sqrt(prev_rshares - vote_rshares) - sqrt(prev_rshares)) * [30min-penalty] * [beneficiaries]

Trying to repeat the math manually on a couple of posts I saw deviations with the steem calculated weights. It turned out the reason for that is that steem does not use the actual square root function but an approximation. I suspect performance reasons, because a square root calculation on a 128bit integer may be computationally expensive. The according approximation function is at https://github.com/steemit/steem/blob/06cd84fddeea2cc9fca179a0f093976864ba7b09/libraries/chain/util/reward.cpp#L17

The following graph shows a plot of sqrt() and approx_sqrt() for an rshare range of [100, 2e14]. The calculations are done with python's math.sqrt(). As a reference, the current rshare values of 5% and 100% utopian-io votes at ~100% VP are shown.

You can see that the approx_sqrt() function uses a step-wise linear approximation of the square root and the approximated function tends to give higher results.
The following graph shows the relative difference of sqrt() and approx_sqrt() in relation to the sqrt() result. Please note the logarithmic scale on the x axis.

You can see that the deviation between the two the square root functions oscillates between 0 and around +6% in most of the cases. For low rshare values, the deviation can also be negative.

This means that using Math.sqrt() may give results that are up to around 6% off the values that are calculated by steem. This is however not necessarily the resulting error on the final curation reward in STEEM. This value had to be calculated with proper error propagation on the full formula.
I compared the results with both functions for a handful of posts manually and saw deviations in the order of 0-3%, but this is obviously not statistically significant.

The approx_sqrt() function should be rather easy to implement in the bottracker curation estimator to get consistent results with steem. Unfortunately my javascript skills are close to non-existant, so I can't provide a PR.

Expected behavior

You should be able to login via Steem Connect on any page on the site.

Actual behavior

When you try to login on the curation rewards estimator page steem connect returns a failure message.

How to reproduce

A) Visit https://steembottracker.com/
B) Click on Tools in the top navigation
C) Click on Curation Estimator
D) Once the page has loaded on the curation estimator page, click on login located at the top right of the page.
E) It will take you to a page which shows an error when you try to login.

Browser: Google Chrome (Version 63.0.3239.132 (Official Build) (64-bit))
Operating system: MacOS HighSierra Version 10.13

Recording Of The Bug

A recording of the bug can be found here: https://d.tube/#!/v/tobias-g/tqjmvkpy

Note: I found this post following my previous contribution and is the same bug as the current bug has been resolved and this issue is still apparent at the time of writing.

I found a bot (profitbot) which says it doesn't leave a comment but does.

Is there anything that can be done about false info?

The latest bidders is not moving to "Last Round" after end of bid, this issue when "max_roi" turned on.

Hi,

Already config the bot by https://steembottracker.com/config.html and update JSON Metadata. But @boostbot still unlisted at https://steembottracker.com.

Would you please check why this @boostbot not listed yet at https://steembottracker.com?

Thank you.

I'm copypasting the same issue I made on Post Promoter script here as it is also relevant to Steembottracker.com.

CoinMarketCap average price is artificially inflated due to HitBTC's price insanity that happens from time to time. You haven't been able to Deposit/Withdraw STEEM/SBD from Hitbtc for a long time yet it frequently pumps to extremely high levels. Currently over $20 for SBD.

We also know poloniex suffers from similar issues just not as pronounced. I recommend using an average of Bittrex & Binance to report current STEEM/SBD prices. They will be far more realistic and consistent.

Currently Steembottracker and Post Promoter script are reporting $3.45 SBD price, but it is no where near that in reality.

Steem Bot Tracker - Timer Glitch on Input Change

Demo Video

Steps to Reproduce:

1. Go to Steem Bot Tracker
2. Slide the Vote Value slider back and forth quickly
3. Watch the Last Vote and Next Vote clocks run much faster

Expected Behavior

Changing the Vote Value slider should not affect anything else on the page, except for which bots are displayed

Actual Behavior

Changing the Vote Value slider causes the timers for the Last Vote and Next Vote clocks to run much faster. It looks like every time the Vote Value slider changes value increments/decrements them by a second

Browser/OS Info

OS: MacOS Sierra 10.12.06
Browser: Chrome 63.0.3239.84 (Official Build) (64-bit)

Thanks!

it is round details:

and, it is actual vote value:

When contacted to @booster admins, they presented it is a bottracker issue.

Please, can you check?

Actual behavior

When using @yabapmatt curation calculator with posts that have a value more than 500$ the slider will not work as expected and the max value is fixed to 500$ .

Expected behavior

The slider max should be a variable that depend on the initial value of the post.

How to reproduce

1- Go to https://steembottracker.com/curation_calculator.html?
2- Enter the requested information and use a post with a value > 500$ you can use this one : https://steemit.com/steemstem/@steemstem/promoting-steemit-going-down-inside-the-large-hadron-collider-at-cern-with-steemstem
3- Now Try to move the slider and check the min/max value of the slider.

• Browser:
  Google Chrome Version 63.0.3239.132 (Official Build) (64-bit)
• Operating system:
  Windows 10

𝕨𝕖 𝕘𝕠 𝕤𝕝𝕠𝕨 𝕓𝕦𝕥 𝕨𝕖 𝕘𝕠 𝕗𝕦𝕣𝕥𝕙𝕖𝕣 @TheGoldenPhoenix

---

---

Posted on Utopian.io - Rewarding Open Source Contributors

---

Strangely pushup bot disappeared today from the site.
Bid api site is working fine
https://steembrain.com/api/bids

Hello@Mattyice,

I am a professional copywriter looking for open source projects here on git hub to contribute to.

I can see from the bottracker website that it needs certain web pages such as an An About Us page, FAQ page, Privacy Policy/ Terms Of Use Page, and so on

I can help you write the webpage copy/content for each of these pages if you'd like... so you could paste them in the respective pages when they are created.

The question though is... can I write them ...and if yes, will they be merged into your master repo here on github?

Either way, please let me know asap so I could get started immediately.... or not.

I can be reached on Discord via @order4adwriter if you'd like us to have a chat about it.

Thanks.

The field for 'Max Suggested Bid' should be limited by the bot's 'Max Bid' setting to create a better UX.

I disabled bot 'pushup' in settings but it is still showing up on tracker.

Hello,

The idea of your project is amazing and while you are doing an awesome job with technical aspects and coding, i will like to take some weight off you by offering copywriting services.

I will contribute a privacy policy which is a statement or a legal document that discloses some or all of the ways a party gathers, uses, discloses, and manages a customer or client's data.

I will contribute a compelling About Us content that will tell off your founding story, a content that will show off your the core or your project, and will answer the most pressing question new and old users may have about your project.

I will also create FAQ Content. I will use Frequently asked questions or Questions and Answers to list out questions and answers, all supposed to be commonly asked in some context, and pertaining to your project and more insight to the project.

I am willing to contribute to the copywriting aspect of your project so you can put more effort on the technicalities and perform at your optimum best.

Anticipating Your response.

Thank you.

There has been an explosion in bid-based voting bots recently and I've had to turn a bunch away which have small amounts of SP. I would like to add a separate section for these smaller bots which maybe needs to be loaded/refreshed manually by the user.

I have been seeing bids show up for crazy high prices, 20 SBD bids turning into 450 SBD and causing the site to show a bot well over profitability, and a few minutes later showing the correct bid.

This happens fairly often and doesn't seem limited to any specific bot and it also doesn't seem to be reflected in the bot's bid api, so it seems exclusive to Steembottracker.com. It's not a new issue just never thought to leave an issue on the bottrackersite github about it.

Inflated Bid (look at @gravity-protocol)

After hitting F5 to refresh

There was a bid bot that went down for two days and got dropped from steembottracker.com. The tracker showed it down for a while then it got delisted.

The bot has resumed voting and the bot operator did an account_update broadcast, but it didn't get relisted on steembottracker.com. Is there some other way to get it relisted?

Bot in question: @booster

The bottracker curation estimator reward calculations show slight deviations to the steem calculated values. Steem calculates the "weight" of each vote with a formula using the square root of the voter rshares in relation to the sum of all previous voters rshares. A great explanation of the curation reward system was given by @miniature-tiger in:

• An Illustrated Guide to Curation - from the simple to the complex - with real examples from past posts - Part 1
• An Illustrated Guide to Curation - from the simple to the complex - with real examples from past posts - Part 2

The core math is the calculation of

weight = (sqrt(prev_rshares - vote_rshares) - sqrt(prev_rshares)) * [30min-penalty] * [beneficiaries]

Trying to repeat the math manually on a couple of posts I saw deviations with the steem calculated weights. It turned out the reason for that is that steem does not use the actual square root function but an approximation. I suspect performance reasons, because a square root calculation on a 128bit integer may be computationally expensive. The according approximation function is at https://github.com/steemit/steem/blob/06cd84fddeea2cc9fca179a0f093976864ba7b09/libraries/chain/util/reward.cpp#L17

The following graph shows a plot of sqrt() and approx_sqrt() for an rshare range of [100, 2e14]. The calculations are done with python's math.sqrt(). As a reference, the current rshare values of 5% and 100% utopian-io votes at ~100% VP are shown.

You can see that the approx_sqrt() function uses a step-wise linear approximation of the square root and the approximated function tends to give higher results.
The following graph shows the relative difference of sqrt() and approx_sqrt() in relation to the sqrt() result. Please note the logarithmic scale on the x axis.

You can see that the deviation between the two the square root functions oscillates between 0 and around +6% in most of the cases. For low rshare values, the deviation can also be negative.

This means that using Math.sqrt() may give results that are up to around 6% off the values that are calculated by steem. This is however not necessarily the resulting error on the final curation reward in STEEM. This value had to be calculated with proper error propagation on the full formula.
I compared the results with both functions for a handful of posts manually and saw deviations in the order of 0-3%, but this is obviously not statistically significant.

The approx_sqrt() function should be rather easy to implement in the bottracker curation estimator to get consistent results with steem. Unfortunately my javascript skills are close to non-existant, so I can't provide a PR.

The curation reward estimator uses the 30 minute time window (HF19) instead of the 15 minute time window (HF20). Also, it claims that rewards go to the author instead of back to the rewards pool.

Having problems loading today

Somewhere in the last few months, the site has become very slow. Most notably hitting the dropdown for a bot to select details. It takes quite a few tries sometimes and is very slow. The site also feels very sluggish in general compared to where it was a few months ago.

It feels inconsistent, sometimes it isn't so bad, other times it feels it really struggling. I typically have most bots filtered out as I keep the filter at 50 minimum.

Price for Steem and SBD currently shows as $1. This messes up all calculations for bid profitability.

• Take into account post age
• Think about changing how ROI is shown

I will be doing an analysis for each pay out made from each bot on the steembottracker site to estimate most profitable bots for bidding, and factors that affect interest or profitability. Any charts of analysis available would be greatly appreciated

There was a bid bot that went down for four days and got dropped from steembottracker.com. The tracker showed it down for a while then it got delisted.

The bot has resumed voting and the bot operator did an account_update broadcast, but it didn't get relisted on steembottracker.com. Is there some other way to get it relisted?

Bot in question: @booster

I filled out the bot owner from and added the metadata to my bot's account but it is still not listed in the tracker. Here is the bot's profile: https://steemit.com/@bluebot

Am I missing something?

• Don't allow delegating all SP available in the account
• Don't allow delegating SP that is being powered down
• Add a button to click after entering delegator account name

Expected behavior

The Steembottracker is a bidding application build by @yabapmatt that provides a dynamic window for a user to buy votes from the bidding bots, displaying their Minimum Value, Suggested Bid and ROI like parameters. So that a user can bid on the voting power of a particular bot.

It's expected that when a user clicks on the User --> Bid History It should display the History of Bids made by the logged in user.

Actual behavior

Currently, the Bid History is not getting displayed at all irrespective of the waiting time.

How to reproduce

1. Open the https://steembottracker.com/ on Web Browser (Google Chrome is used here).
2. Login with a steemit user using steemconnect.
3. Navigate to User--> Bid History
4. Frame opens up but no data is displayed.

• Browser: Google Chrome/ Mozilla Firefox
• Operating system: Windows 8.1

Recording Of The Bug