No commit activity in last 3 years
No release in over 3 years
Ruby wrapper for Block Explorer and Blockchain.info. Plan to add additional 3rd-party bitcoin APIs
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

>= 0
>= 0
>= 0
 Project Readme

Bitcoin 3rd-party APIs

Ruby wrapper for various popular 3rd-party bitcoin related APIs. At the moment only Block Explorer (http://blockexplorer.com) and BlockChain.info (http://blockchain.info) are wrapped. The gem exposes some handy bitcoin blockchain query methods, useful for thin bitcoin clients.

Installation

Add this line to your application's Gemfile:

gem 'bitcoin-3rd-party-apis'

And then execute:

$ bundle

Or install it yourself as:

$ gem install bitcoin-3rd-party-apis

Usage

mytransactions returns Ruby hash of raw transactions relating to the specified address(es).

    BlockExplorer.mytransactions(address)
    BlockExplorer.mytransactions([address1, address2])

multiaddr is similar to BlockExplorer's mytransactions, but returns a more user-friendly hash.

    BlockchainInfo.multiaddr(address)
    BlockchainInfo.multiaddr([address1, address2])

getreceivedbyaddress returns BigDecimal of the total amount of bitcoins sent to the address. Note for the BlockchainInfo version, 120 is the maximum confirmation number.

    BlockExplorer.getreceivedbyaddress(address)
    BlockExplorer.getreceivedbyaddress(address, 3) # return received amount where transactions have minconf=3

    BlockchainInfo.getreceivedbyaddress(address)
    BlockchainInfo.getreceivedbyaddress(address, 3) # return received amount where transactions have minconf=3

longest_block_count returns count of the longest blockchain in the network. This blockchain is considered the current blockchain.

    BlockchainInfo.longest_block_count

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request