Let's say you have multiple blogs like steemit, golos, vox, whaleshares etc. How can you track balance? How to manage a lof of stuff? This repo was created to invent a way to manage all your graphene-based blogs in a comfortable way.
Details & Features
This repo can be reviewed in same way what "cryptocompare api" does for cryptocurrencies and exchanges (unified API and single access point). In the future it should be mediablockchain-neutral, universal source code to work with different blockchains.
Repository
https://github.com/sxiii/graphene-balances
Components
- Node.JS
Development status
- Main task: allow loading accountbalances from top-10 graphene blockchains
- Second task: implement a way to load post statistics from different blockchains
- Additional tasks: posting, calculating earnings, earnings history etc.
Communication
Telegram @fakesnowden
Github
This repo helps you to unify requests to different graphene-based blockchains.
Supported:
- steemit.com
- golos.io
- whaleshares.io
- vox.community
- smoke.network
Work in progress:
- serey.io
- weku.io
- viz.world
- scorum.com
- VIT
Installing
git clone https://github.com/sxiii/graphene-balances
cd graphene-bal*
Editing
Open recently downloaded folder and the single file. In the file, find var names = ['sxiii']
and edit it to your nickname.
Running
Run the file like node st.js
Sample output
URL Balance VESTS SBD
------------ ------------- ---------------------- -----------
vox 0.596 VOX 230076.684583 VESTS 0.499 GOLD
golos 650.589 GOLOS 183798279.977379 GESTS 406.449 GBG
smokenetwork 0.000 SMOKE 4.197000 VESTS
steemit 1.297 STEEM 206883.456950 VESTS 290.966 SBD
whaleshares 0.000 WLS 171.751990 VESTS
Thanks for the contribution, @sxiii! Looks like a cool, little CLI - good work.
I would recommend keep an eye on the quality of your code, your commit messages and the amount of work (as it is very little). There are many guides out there describing the best practices of JavaScript, e.g. the Airbnb style guide and how to write good commit messages, so I'd suggest you read both. I also think reading this guide, which was made by one of our (at the time) moderators, will benefit your future contributions. Good luck!
Also, you used the tag "task-development" when you should be using "development" instead.
Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.
To view those questions and the relevant answers related to your post, click here.
Need help? Write a ticket on https://support.utopian.io/.
Chat with us on Discord.
[utopian-moderator]
Hey @amosbastian! Thank you very much for your feedback. I will use tag "development" in the future. The code is really yet small but in the future I plan to make it larger as I stated in the repo. Thanks a lot for the links to the style guide and other info, I will take my time to improve myself!
Thank you for your review, @amosbastian!
So far this week you've reviewed 6 contributions. Keep up the good work!
Hey, @sxiii
Thank you for your contribution
So far you've submitted 2 contributions on Utopian. Keep up the good work!Your 0 contributions have been appoved and upvoted by Utopian
Here is your contributions details..
Your total payout for 0 contributions is $ 0.00
This bot is wrong. Probably he was developed later. I previously had a lot of utopian approved contributions!
Hi @sxiii!
Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your post is eligible for our upvote, thanks to our collaboration with @utopian-io!
Feel free to join our @steem-ua Discord server
Hey, @sxiii!
Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!
Get higher incentives and support Utopian.io!
Simply set @utopian.pay as a 5% (or higher) payout beneficiary on your contribution post (via SteemPlus or Steeditor).
Want to chat? Join us on Discord https://discord.gg/h52nFrV.
Vote for Utopian Witness!