You are viewing a single comment's thread from:
RE: How Much of the Rewards Pool is Paid out by BitBots Votes V's Organic Votes
The real problem with doing it that way is trying to actually sort through that much data, because you have to have both all of the transfers and memos and all of the votes in order to possibly have a positive hit.
If these bot designers were smart, they would start requiring that the memo be sent with an encrypted hashtag at the beginning so that casual observation couldn't make out what the targeted URL is from outside the recipient. Some of them may be doing that; that's outside of my personal experience.
That is a lot of data to be slinging around the network, which is the problem I've been running into a lot lately. It might be possible, but it's definitely not a simple trick.
You caught me there, it's probably too simplistic what I would do:
Done. But again: This is the approach of a lousy SQL amateur;-)
See, the problem is not this process, which is fairly straightforward – it's generating the list of transfer amounts and URLs along with bot up votes percentage and URL. In order to generate those lists in the first place, you have to do a fair amount of ugly digging and parsing.
It's that part that's really the issue. Figuring out what the signs of those things are and extracting them.
And then you have to do it for every single bot, which means that you have a fair number of transactions that are going to have to be hitting the server in order to straighten everything out.
It's a lot of data. And ultimately – I'm not sure that it really tells us anything that we don't already know.
It might actually be more efficient to simply query the lot of all posts made over the last week and have them give their active_votes attribute up and do all of the parsing on that. If nothing else it keeps the query simple.