Steem RPC Node Following Anomaly

    Seems I've encountered anomalous data attempting a get_following method invocation against @anyx's full RPC node. I thought I was going insane.

See it for yourself

    The problem can be reproduced by performing the following using Python3.6.

from beem import Steem

nodes = NodeList().get_nodes()
stm = Steem(node='https://anyx.io')

stm.rpc.get_following(acc.name,'darth-azrael','blog',1, api='follow')

     If you try any other account, the ouput will return the same account but, for some reason, @darth-azrael outputs @ond. Let's try running it against another account.

 stm.rpc.get_following(acc.name,'rollingbones','blog',1, api='follow')

    As expected, this returns the follower dictionary representing the @steemflagrewards Community Moderator badge account following of @therollingbones as can be seen below:

 [{'follower': 'badge-127001', 'following': 'rollingbones', 'what': ['blog']}]

    I entertained the idea that perhaps the account having a hyphen could have caused this but this theory was scrapped after running the RPC call below.

>>> stm.rpc.get_following(acc.name,'sbi-booster','blog',1, api='follow')
[{'follower': 'badge-127001', 'following': 'sbi-booster', 'what': ['blog']}]

My question is what the F is going on?Is this a one-off or could there be a broader issue?

It's TINFOIL HAT TIME!

    Although it is difficult for we to isolate the fault on a system that we do not have administrative control over, we can speculate as to possible causitive factors.

Something to consider is that most accounts that @badge-127001 has followed were were followed today.

_{(Yes, that IS my representation of the loopback IP address. Had to snag it! #justITnerdthings)}

    It could be as simple as a glitch / system error on @anyx's node or something else. That something else could be a lot of things. Considering we have a slew of sock-puppet witnesses, I won't dismiss the possibility that one of the systems screewed the pooch in block production.

Bear in mind, this is merely conjecture at this point.

    I'm hoping someone will be able to shed some light as to what caused this inconsistent and unexpected result. Worse comes to worse, I'll need to develop some sort of logic bypass but I would rather not go to that length.

What do you think?

Is this just a random bug or a sign of FUBAR to come? Hope not but guess we'll cross that bridge when we get there! 🌉

If you appreciate the work, consider sending me a tip!

Or you could show some love by supporting the SFR project to help it grow as a moderation asset of our blockchain!

How to put your FREE Downvotes to work in 2 easy steps!

Learn more!

This post was created using the @eSteem Desktop Surfer App.

     They also have a referral program that promotes users to onboard to our great chain. Sign up using my referral link to help support my efforts to improve the Steem blockchain.

Ditch Partiko and get eSteem today!

PlayStore - Android	Windows, Mac, Linux
AppStore - iOS	Web