RE: An Update on @EZVote and the collective going along with it! HIGHER RETURNS NOW AVAILABLE! Over 14K SP now available to vote with! :)
I am using a 'Roll Call' as stress test for ezvote's instant-vote version. It made it about 6 votes in across an hour before any delay/problem started, but that could also be caused by what challengethegods mentioned (the invalid memo botwar, LOL).
Assuming there was some threshold set early on from the bidding rounds system, I think it might make sense to either have some queue mechanic (maybe you already do?), or to just allow the bot draining itself down to lower voting power as a pseudo-market autobalance type deal.
Also, I have sent a duplicate bid for the last one, so it will be interesting to see how the bot handles that after whichever delay is finished (I'm guessing same as duplicate vote behavior, but this seems like a slightly different scenario to test)
edit: it may have determined the duplicate URL could be considered as a stacked bid of 0.2, which makes sense, but it may have cause some weirdness in the process because that person got a smaller vote than everyone else from the double-bid scenario. Thinking on it now, I'm not sure I have tested anything except minimum bids, so I'm not sure if this is from the duplicate memo, increased bid size, a recent change to the bot, or combination of these. Anyway I thought this extra tidbit might be useful to know.
^_^
It seems that by constantly "getting bids" it was delaying the voting rounds from happening as it thought there were constantly more bids coming in, despite it being the dlease txs meant to refer to delegations. We simply added dlease to the "non-refund" list now, so that should prevent any future issues. We use dlease heavily for delegations, so it makes sense that eventually there'd be some sort of issue considering we forgot to add them to the ignore list. lol. All should be fixed now and if there is anywhere that value wasn't properly applied, please let us know and we will be happy to fix it! :) Thanks for bringing this to our attention!
P.S. - The bot is set to vote until it's under 96% and it will not curate anything unless it's over 99%, so votes are always available (Unless it should be used to go below 96%, then a minor wait would occur. The wait should be no more than 40~ minutes or so tho, which is why the bot is not set to vote at 100% power because it would have to wait 2.4 hours then. We are able to consistently provide profitability from small bids, while being able to vote more often and essentially instantly when people request one.