0.0
No commit activity in last 3 years
No release in over 3 years
Ruby wrapper for the Bitcoinaverage API. Bitcoinaverage is an independent 'globally averaged bitcoin price' provider
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
 Dependencies

Development

>= 0

Runtime

>= 0
 Project Readme

Ruby wrapper for the BitcoinAverage API

Gem Version Coverage Status Build Status

Bitcoinaverage is an independent 'globally averaged bitcoin price' provider. They provide on one hand a Global price, which is based on the volume and price of BTC in all currencies. And on the other hand they provide a Market price, which only takes into account the volume of BTC directly exchangeable using the chosen specific currency. For more information on the methods BitcoinAverage uses to calculate the price, please refer to their website, in particular this page.

Important first note

The development of this gem has been deeply inspired by Erik Michaels-Ober's great mtgox gem ( specially this README ;) ).

Installation

gem install bitcoinaverage

Documentation

TODO

Usage

require 'rubygems'
require 'bitcoinaverage'

# Obtain the BitcoinAverage's global price
BitcoinAverage.global

# Obtain the BitcoinAverage's market price
BitcoinAverage.market

# Obtain the BitcoinAverage's global price in EUR
BitcoinAverage.global 'EUR'

# Obtain the BitcoinAverage's market price in GBP
BitcoinAverage.market 'GBP'

# Obtain the specific fields of BitcoinAverage's global price
BitcoinAverage.global.last
BitcoinAverage.global.bid
BitcoinAverage.global.ask
BitcoinAverage.global.volume_btc
BitcoinAverage.global.volume_percent

Tested Ruby Versions

This library aims to support and is tested against the following Ruby implementations:

  • ruby-1.9.3-p374
  • ruby-2.0.0-p353
  • ruby-2.1.0

Contributing

In the spirit of free software, everyone is encouraged to help improve this project.

Here are some ways you can contribute:

  • by using alpha, beta, and prerelease versions
  • by reporting bugs
  • by suggesting new features
  • by writing or editing documentation
  • by writing specifications
  • by writing code (no patch is too small: fix typos, add comments, clean up inconsistent whitespace)
  • by refactoring code
  • by closing issues
  • by reviewing patches

Copyright

Copyright (c) 2014 Toni Urcola. See LICENSE for details.