Community post
Waveschainex 0.2 release: Elixir/Erlang client for WAVES REST API
I'm releasing Waveschainex 0.2, an update of Elixir API client for WAVES API.
Repos and docs
Release commit history
Configuration
Default setting for WAVES nodes API is https://nodes.wavesnodes.com.
To configure a custom url use the following config setings:
config :waveschainex,
waves_node_url: "YOUR_CUSTOM_URL"
Changelog
All functions are documented, covered by tests and include typespecs.
Address module
get_data_item: Read data associated with an account and a keybalance_details: Details for balancealias_of_address: Returns a collection of aliases associated with an Addressaddress_of_alias: Returns an address associated with an Alias.
Block module
first: Get genesis block datachild: Get children of specified blockseq: Get block at specified heightsaddress: Get list of blocks generated by specified address
Peers module
connected_peers: Connected peers list
Transaction module
utx_transaction_info: Get transaction that is in the UTXaddress_limit: Get list of transactions where specified address has been involvedutx_size: Get number of unconfirmed transactions in the UTX pool
Consensus module
algo: Shows which consensus algo being using
Asset module
balance_distribution: Asset balance distribution by account
About Elixir
Elixir is a functional programming language with superior concurrency primitives, distributed computation and fault tolerance capabilities based on Erlang/OTP. Personally, I am really happy with my bet on Elixir to build cryptocurrency related apps and strongly recommend to learn more about Elixir and Erlang ecosystem.
Learning resources:
- ElixirConf Jose Valim Keynote
- ElixirConf 2016 Chris McCord Keynote
- Elixir School
- Elixir Crash Course
Replies (6)
Finding happiness in what we do is the strength behind every improvement.
I’m humbled by your humility and quest to learn more.
I’m a friend @maxdevalue
Thanks for the contribution, @ontofractal! Very cool to see that you are still working on this - great work!
One thing I'd like to note is that in Utopian's guidelines it says that we only take commits made, or pull requests merged, in the last 14 days into account when reviewing a contribution. The majority of the changes in this release are from months ago. I have tried being a bit lenient with this guideline, but even so, I'd like to ask you to keep that in mind for future contributions.
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]
Hi @ontofractal!
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, @ontofractal!
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!
Thank you for your review, @amosbastian!
So far this week you've reviewed 8 contributions. Keep up the good work!
Thanks for the review, @amosbastian! I'll make sure to remember the 14 days rule in the future.