No commit activity in last 3 years
No release in over 3 years
Gem to access Blockchain Cryptoprocessing Platform API
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 1.16
>= 0
~> 10.0
~> 3.0

Runtime

~> 2.0
~> 0.19
 Project Readme

Cryptoprocessing

Ruby Gem to access and interact with Cryptoprocessing API.

To experiment with that code, run bin/console for an interactive prompt.

Gem Version Build Status Coverage Status

Installation

Add this line to your application's Gemfile:

gem 'cryptoprocessing'

And then execute:

$ bundle

Or install it manually as:

$ gem install cryptoprocessing

Usage

Basic usage

require 'cryptoprocessing'

# Authenticate using email and password
client = Cryptoprocessing::Client.new(email: '<EMAIL>', password: '<PASSWORD>')

# or

# Using block
Cryptoprocessing.configure do |c|
  c.email = '<EMAIL>'
  c.password = '<PASSWORD>'
end

# or

client = Cryptoprocessing::Client.new(access_token: '<TOKEN>')
client.account '<ACCOUNT_ID>'

Paging

Authorization

Authorization using API keys

Logging

Development

After checking out the repo, run bin/setup to install dependencies. Then, run rake spec to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/oomag/cryptoprocessing-api-client. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.

TODO

License

The gem is available as open source under the terms of the MIT License.

Code of Conduct

Everyone interacting in the Cryptoprocessing project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.

Credits

Arthur Chafonov mailto:actuosus@gmail.com