Steem Ruby API Client
Ruby Shell
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
images gource Oct 13, 2017
lib version bump Jun 1, 2018
test tests May 19, 2018
.codeclimate.yml Added code climate. Aug 19, 2016
.gitignore gource Oct 13, 2017
.travis.yml ci/cc May 7, 2018
Gemfile Initial push. Aug 19, 2016
Gemfile.lock version bump Jun 1, 2018
LICENSE Initial push. Aug 19, 2016 docs May 6, 2018
Rakefile Merge branch 'develop' May 6, 2018 gource Oct 13, 2017
radiator.gemspec gem update Apr 15, 2018

Build Status Code Climate Test Coverage Inline docs


STEEM Ruby API Client

Radiator is an API Client for interaction with the STEEM network using Ruby.

Changes in v0.4.0

  • Gem updates
  • AppBase Support
    • Defaulting to condenser_api.* in Radiator::Api (see below)
    • Handle/recover from new AppBase errors.
  • Radiator::Stream now detects if it's stalled and takes action if it has to wait too long for a new block.
    1. Exponential back-off for stalls so that the node doesn't get slammed.
    2. Short delays (3 times block production) only result in a warning.
    3. Long delays (6 times block production) may try to switch to an alternate node.
  • Fixed internal logging bug that would open too many files.
    • This fix also mitigates issues like SSL Verify problems (similar to #12)
  • Dropped GOLOS support.

Appbase is now supported.

If you were already using Radiator::Api then there is nothing to change. But if you made use of other API classes, like Radiator::FollowApi, then the method signatures have changed.


api =

api.get_followers('inertia', 0, 'blog', 10)

New Signature:

api =

api.get_followers(account: 'inertia', start: 0, type: 'blog', limit: 10)

-- or --

Switch to Condenser API:

The other strategy for using this version of Radiator is to just switch away from classes like Radiator::FollowApi over to Radiator::Api (also known as Radiator::CondenserApi) instead. Then you don't have to update individual method calls.

api =

api.get_followers('inertia', 0, 'blog', 10)

Note about GOLOS

GOLOS is no longer supported in Radiator. If you want to continue to use GOLOS, you'll need to branch from v0.3.15 (pre-appbase) and add WebSockets support because GOLOS completely dropped JSON-RPC over HTTP clients support for some reason

Radiator has never and will never use WebSockets due to its server scalability requirements.

From a client perspective, WebSockets is great. I have nothing against WebSockets. So I might get around to it at some point, but GOLOS won't be part of Radiator anymore mainly because GOLOS has no plans to implement AppBase.

Changes in v0.3.0

  • Gem updates
  • Added failover subroutines (see Failover section, below).
  • Added method closures support (aka passing a block to yield).
  • You can now stream virtual operations (see Streaming section, below).
  • Added more documentation.
  • Added/expanded more api namespaces: ::BlockApi, ::CondenserApi, ::TagApi
  • Addressed an issue with logging on certain Windows configurations.

Fixes in v0.2.3

  • Gem updates
  • Added low-level support for persistence and retrying API requests.
  • Now using exponential back-off for retries.
  • Detecting presence of transaction_ids (if enabled by the node).
  • Default for Hashie warnings now go to /dev/null, where they belong.
  • Added stray methods/operations.

Fixes in v0.2.2

  • Gem updates
  • Improved support for datatypes and handlers.
    • UTF-8 handled more smoothly.
    • Simplified operation construction.
  • Improved keep-alive defaults.
    • Better streaming reliability.

Also see: Documentation

Quick Start

Add the gem to your Gemfile:

gem 'radiator'


$ bundle install

If you don't have bundler, see the next section.


minimum ruby version: 2.2


$ sudo apt-get install ruby-full git openssl libssl1.0.0 libssl-dev
$ gem install bundler


$ gem install bundler


require 'radiator'

api =
api.get_dynamic_global_properties do |properties|
=> "271342874.337 STEEM"

... or ...

require 'radiator'

api =
response = api.get_dynamic_global_properties
=> "271342874.337 STEEM"

Follower API

api =
api.get_followers(account: 'inertia', start: 0, type: 'blog', limit: 100) do |followers|
=> ["a11at",


Here's an example of how to use a streaming instance to listen for votes:

require 'radiator'

stream =

stream.operations(:vote) do |op|
  print "#{op.voter} voted for #{}"
  puts " (weight: #{op.weight / 100.0}%)"

The output would look like this and continue until interrupted.

richman voted for krnel (weight: 100.0%)
rainchen voted for rainchen (weight: 100.0%)
richman voted for exploretraveler (weight: 100.0%)
jlufer voted for michaelstobiersk (weight: 100.0%)
jlufer voted for michaelstobiersk (weight: 100.0%)
patelincho voted for borishaifa (weight: 100.0%)
richman voted for vetvso (weight: 100.0%)
jlufer voted for michaelstobiersk (weight: 100.0%)
richman voted for orcish (weight: 100.0%)
demotruk voted for skeptic (weight: -100.0%)
photorealistic voted for oecp85 (weight: 100.0%)
meesterboom voted for rubenalexander (weight: 100.0%)
thecurator voted for robyneggs (weight: 40.0%)
richman voted for originate (weight: 100.0%)
helikopterben voted for etcmike (weight: 100.0%)

You can also just stream all operations like this:

stream.operations do |op|
  puts op.to_json

Example of the output:


You can also stream virtual operations:

stream.operations(:producer_reward) do |op|
  puts "#{op.producer} got a reward: #{op.vesting_shares}"

Example of the output:

anyx got a reward: 390.974648 VESTS
gtg got a reward: 390.974647 VESTS
someguy123 got a reward: 390.974646 VESTS
jesta got a reward: 390.974646 VESTS
blocktrades got a reward: 390.974645 VESTS
timcliff got a reward: 390.974644 VESTS
bhuz got a reward: 1961.046504 VESTS

Transactions are supported:

stream.transactions do |tx, trx_id|
  puts "[#{trx_id}] #{tx.to_json}"

Example of the output:



Even whole blocks:

stream.blocks do |bk, num|
  puts "[#{num}] #{bk.to_json}"

Example of the output:


Transaction Signing

Radiator supports transaction signing, so you can use it to vote:

tx = 'Your Wif Here')
vote = {
  type: :vote,
  voter: 'xeroc',
  author: 'xeroc',
  permlink: 'piston',
  weight: 10000

tx.operations << vote

You can also post/comment:

tx = 'Your Wif Here')
comment = {
  type: :comment,
  parent_permlink: 'test',
  author: 'your-account',
  permlink: 'something-unique',
  title: 'Radiator Can Post Comments!',
  body: 'Yep, this post was created by Radiator in `ruby`.',
  json_metadata: '',
  parent_author: ''

tx.operations << comment


tx = 'Your Wif Here')
transfer = {
  type: :transfer,
  from: 'ned',
  to: 'inertia',
  amount: '100000.000 SBD',
  memo: 'Wow, inertia!  Radiator is great!'

tx.operations << transfer

There's a complete list of operations known to Radiator in broadcast_operations.json.


Radiator supports failover for situations where a node has, for example, become unresponsive. When creating a new instance of ::Api, ::Stream, and ::Transaction, you may provide a list of alternative nodes, or leave them out to use the default list. For example:

options = {
  url: '',
  failover_urls: [

api =

In a nutshell, the way this works is Radiator will try a node and proceed until it encounters an error, then retry the request. If it encounters a second error within 5 minutes, it will abandon the node and try a random one from failover_urls.

It'll keep doing this until it runs out of failovers, then it will reset the configuration and go back to the original node.

Radiator uses an exponential back-off subroutine to avoid slamming nodes when they act up.

There's an additional behavior in ::Stream. When a node responds with a block out of sequence, it will use the failover logic above. Although this is not a network layer failure, it is a bad result that may indicate a problem on the node, so a new node is picked.

There is another rare scenario involving ::Transaction broadcasts that's handled by the failover logic: When a node responds with a network error after a signed transaction is accepted, Radiator will do a look-up to find the accepted signature in order to avoid triggering a dupe_check error from the blockchain. This subroutine might take up to five minutes to execute in the worst possible situation. To disable this behavior, use the recover_transactions_on_error and set it to false, e.g.:

tx = wif, recover_transactions_on_error: false)


To enable debugging, set environment LOG=DEBUG before launching your app. E.g.:

$ LOG=DEBUG irb -rradiator

This will enable debugging for the irb session.


Problem: My log is full of Unable to perform request ... retrying ... messages.

W, [2017-10-10T11:38:30.035318 #6743]  WARN -- : database_api.get_dynamic_global_properties :: Unable to perform request: too many connection resets (due to Net::ReadTimeout - Net::ReadTimeout) after 0 requests on 26665356, last used 1507660710.035165 seconds ago :: cause: Net::ReadTimeout, retrying ...

This is caused by network interruptions. If these messages happen once in a while, they can be ignored. Radiator will retry the request and move on. If there are more frequent warnings, this will trigger the failover logic and pick a new node, if one has been configured (which is true by default). See the Failover section above.

Problem: My log is full of Invalid block sequence messages.

W, [2017-10-10T13:53:24.327177 #6938]  WARN -- : Invalid block sequence at height: 16217674

This is a similar situation to Unable to perform request ... retrying .... Radiator::Stream will retry and failover if needed. It is happening because the node has responded with a block out of order and ::Stream is ignoring this block, then retrying.

Problem: What does the Stream behind error mean?

W, [2017-10-09T17:15:59.164484 #6231]  WARN -- : Stream behind by 6118 blocks (about 305.9 minutes).


This is an error produced by ::Stream when it notices that the current block is falling too far behind the head block. One solution is to just restart the stream and see if it happens again. If you see a message like this occasionally, but otherwise the stream seems to keep up, it probably was able to recover on its own.

There can be several root causes. Resources like memory and CPU might be taxed. The network connection might be too slow for what you're doing. Remember, you're downloading each and every block, not just the operations you want.

If you have excluded system resources as the root cause, then you should take a look at your code. If you're doing anything that takes longer than 3 seconds per block, ::Stream can fall behind. When this happens, ::Stream will try to catch up without displaying a warning. But once you fall 400 blocks behind (~20 minutes), you'll start to get the warning messages.

Verify your code is not doing too much between blocks.

Problem: I'm getting an endless loop: #<OpenSSL::SSL::SSLError: SSL_connect SYSCALL returned=5 errno=0 state=error: certificate verify failed>


You're probably creating too many threads or you don't have enough resources for what you're doing. One option for you is to avoid persistent HTTP by passing persist: false.

Doing this will impact performance because each API call will be a separate socket call. All of the constructors accept persist: false., e.g.:

api = false)

... or ...

stream = false)

... or ...

tx = false, wif: wif))

Also see troubleshooting discussion about this situation:


  • Clone the client repository into a directory of your choice:
    • git clone
  • Navigate into the new folder
    • cd radiator
  • Basic tests can be invoked as follows:
    • rake
  • To run tests with parallelization and local code coverage:
    • HELL_ENABLED=true rake
  • To run a stream test on the live STEEM blockchain with debug logging enabled:
    • LOG=DEBUG rake test_live_stream

See my previous Ruby How To posts in: #radiator #ruby

Get in touch!

If you're using Radiator, I'd love to hear from you. Drop me a line and tell me what you think! I'm @inertia on STEEM.


I don't believe in intellectual "property". If you do, consider Radiator as licensed under a Creative Commons CC0 License.