Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE BLURT!
Sort Order:  
  ·  3 years ago  ·  

There is no method on Blurt nodes that return incoming delegations. I can ask for it to be added during the next hardfork, then we can add it to the blurt.blog frontend.

I might try to write an independent API for that in the meantime.

That’s something that I’ve been wanting to add to Blurt nodes for a while. I actually asked for that on Steem way back when, too.

  ·  3 years ago  ·  

That is a nice feature to build. Tomoyans tool shows delegate to him, maybe same way we can know delegates for other people.

  ·  3 years ago  ·  

I have opened and issue on GitLab to have this added to Blurt RPC nodes. It doesn't require a hardfork, so it should be easy enough to add. The database already keeps track of delegations. There is a method for getting outgoing delegations and expiring delegations, but no method for getting incoming delegations.

The same problem exists on Steem and Hive. Anyone that shows incoming delegations on their site, it's because they use their own solution for it.

  ·  3 years ago  ·  

Well that could work, I will examine the code and see if i can add.

  ·  3 years ago  ·  

Do you do C++?

  ·  3 years ago  ·  

Ohh that thing, no . But I was thinking if tomoyan added, I may add same through api

  ·  3 years ago  ·  

You would have to build a program that streams the blockchain for vesting_delegation operations, then put them in a database. Then build an API that will return delegations by incoming and outgoing.

It should be easy enough to do.

If I did it, I would do something similar to how I did the price info API.

  ·  3 years ago  ·  

Sounds easy from you , but yeah I will still try as I know you will anyways complete it if I fail
Thanks