As many of you may be aware I was able successfully muster massive STEEM community support with my proposal to get SBD and STEEM listed on popular payment gateway Coinpayments.com. Together as a community our upvotes raised over $875 SBD which will be used alongside pledges from and
to achieve the amount of funding needed to have both SBD & STEEM implemented on their platform!
Earlier this morning I went ahead and paid just under 0.85 Bitcoin to Coinpayments.net in order to get them started on implementing SBD onto their website and payment gateway. I decided to send them a follow up email to see if I could get an estimate on how long it would take until SBD was implemented on their service..
The response from the admin at Coinpayments was a little saddening to say the least:
Funding isn't holding us back from expansion and adoption...
Complete lack of proper documentation is!
The very fact that the Coinpayments.net admin wasn't even able to find enough documentation to want to even attempt to implement SBD or STEEM is an incredibly serious issue in my opinion and raises a very pertinent question:
How The HELL Does STEEM Not Have PROPER Documentation?
While I'm sure many of you have read to this point and are thinking to yourself "Well, this KLYE fellow and his Coinpayments.net lover must just be blind and lazy! Tons of well written documents exists to reference for steem RPC stuff!" I assure you that I've now spent a total of 8 hours today searching on Google and Steemit.com for something that even remotely resembles a full list of the available RPC and API functions that steemd and cli-wallet feature. Now while I've found some pretty good examples of a few commands that seem to have had STEEM users properly document them as a whole we are lacking what some would refer to as necessary documentation.
I must say that for STEEM being such a well crafted and executed idea the very fact that nobody has bothered to take the time to write a proper RPC/API manual listing all available features and functions of our wallet seems downright absurd! While I understand some documentation can be accessed via the steemd or cli_wallet as a community we need to get together and focus on creating this much needed reference guide.
We're currently ranked #7 on Coinmarketcap.com but seemingly left out the part where we hire someone to write the instruction manual for network valued nearly $110,000,000..?
Well That's Just Bad For Business..!
The fact that even when paid $500 USD to implement the STEEM wallet into their system the Coinpayments.net's Administrator refused and was unsure about STEEM due to it's lack of proper documentation...
This is a HUGE Problem for Adoption!
So How Do We Go About Fixing This?
With all this being said I've taken it upon myself to research & compile the necessary information about STEEM's RPC and API calls in order to get the necessary documents needed for current and future developers to quickly and easily reference. While I've only just recently started using steemd / cli_wallet and find it very much different from the "standard" Bitcoin and altcoin wallets I've ran slowly but surely I'm learning the ins and outs of this new technology.
I personally ask anyone who's already started compiling a complete list of all RPC functions or can point me in the right direction in the cli_wallet that would be appreciated. Currently getting a seed and witness node running and going to dive into the nuances of steemd and attempt to make some RPC reference compiled and made public here in the upcoming days.