#### Repository
https://github.com/mahdiyari/steemauto
[update commit](https://github.com/mahdiyari/steemauto/commit/f6b34b1c06975d5c91065b4b79630bb50cbc1fee)
<center>![steemauto_bitpizza.gif](https://cdn.steemitimages.com/DQmSGoS5BwZvVrWrR1TfbPCSJ31pRbJhDANhyBtgGuHoqw3/steemauto_bitpizza.gif)</center>
>10 assert_exception: Assert Exception
abs_rshares > STEEMIT_VOTE_DUST_THRESHOLD || o.weight == 0: Voting weight is too small, please accumulate more voting power or steem power.

Are you familiar with this error? 👆
When you try to upvote a post or a comment while you have low SP (steem power), you will receive that error! But you may receive that error in the other cases too. for example in the low-weight upvotes or when you have low voting power! Read more about voting weight and voting power in the [FAQ](https://steemit.com/faq.html)

STEEMIT_VOTE_DUST_THRESHOLD is a limitation in the steem blockchain to prevent very low-value upvotes on the posts and comments. Right now, a user with 1~1.5 SP is able to broadcast an upvote with full weight (100%) and this limitation (STEEMIT_VOTE_DUST_THRESHOLD) could be changed in the next forks or updates.

But how that limitation effects on the Steemauto?
Actually, when a big trail (with 1,000 followers) upvote a post, many little users will also follow that upvote, and there will be 1,000 upvote calls to the RPC node. Assume more upvotes, maybe 5,000 upvotes! that is where we may get some problems.

<center>![bandwidth_wire.jpg](https://cdn.steemitimages.com/DQmPdyWwZGtjdMMr1X8Lg3SwC5krTDaKw4Qua9yekAX6VZ6/bandwidth_wire.jpg)
<sub>source: searchnetworking.techtarget.com</sub></center>

Making more calls to an RPC node will use huge network bandwidth, and may slow the process of upvoting or other services. Of course, bandwidth on our servers is 1Gbps/s, and that is the huge bandwidth nowadays! but, that 1Gbps is also a limitation for an unlimited service like Steemauto and we may hit that limitation anytime soon!

<center>![bandwidth.png](https://cdn.steemitimages.com/DQmWCpWqKScmNwSrCDSfBCjt4o7Whpxoch59Kuq3CpNr5aG/bandwidth.png)
<sub>source: paessler.com</sub></center>

Steemauto is unlimited, but with limited resources like bandwidth, that is not possible to keep Steemauto unlimited forever. We may force some limitations by passing the time to keep Steemauto more efficiency and functionality to all users.

We decided to check in a regular time and save users SP (steem power) and VP (voting power) in the database, then use that data to prevent low-value upvotes locally in the Steemauto, instead of sending all upvotes to the RPC node. We made that and the result was very impressive! Efficiency increased by 50-60%! and even more in some cases.

<center>![Windows-10-install-update-banner.png](https://cdn.steemitimages.com/DQmNgc6i2Lyx1RshanenzgHSFRwVnVAB2SiS6bGmCoT14So/Windows-10-install-update-banner.png)
<sub>source: winaero.com</sub></center>

#### So, let's announce that new update:
Low-value upvotes will be prevented in the Steemauto, in the all services: Fanbase, Curation trail and Comment upvote.
That limitation in the Steemauto is set to prevent upvotes from users who have less than 1.5 SP (steem power) or upvotes equal to that limitation!

Let's explain in one example:
>Assume I have 10 SP and I configured to upvote a user with 10% weight. Steemauto will calculate effective value of that upvote, which is: `10 SP * 10% = 1 SP` 
in this example, Steemauto will not broadcast that upvote, because 1 SP is lower than 1.5 SP (the configured limitation)

We are waiting for more suggestions and contributions, show some love to this project. Thank you.
***
Submitted to https://utopian.io

Regards,
2018-05-29