Ever SDK (formerly TON SDK) client in Ruby and for Ruby

Ruby gem-client bindings for Ever SDK which allows one to communicate with Everscale blockchain in Ruby.

Note that there are 2 types of versions:

• EverSdk::VERSION - the version of the gem
• EverSdk::NATIVE_SDK_VERSION - the version of the original SDK

and they may not always match each other.

Add this to the Gemfile of a project:

gem "ever_sdk_client"

and run bundle install

Alternatively install it directly

gem install ever_sdk_client

The gem requires tonclient native library, appropriate for one's OS; the download links are at:

https://github.com/tonlabs/ever-sdk#download-precompiled-binaries

Once downloaded, unpack it into a directory of your choice and then set an environmental variable TON_CLIENT_NATIVE_LIB_NAME pointing to the full path of a library.

The examples are located in the examples directory, and they cover most the modules.

And here's a simple minimalistic one:

require "ever_sdk_client"

cfg = EverSdk::ClientConfig.new(
        network: EverSdk::NetworkConfig.new(
                endpoints: ["net.ton.dev"]
        )
)

# first, create a context
c_ctx = EverSdk::ClientContext.new(cfg.to_h.to_json)

# next, call a method of a module you want passing a context to it
EverSdk::Client.version(c_ctx.context) do |res|

  # 'res' is of type EverSdk::NativeLibResponseResult
  # holds either 'result' or 'error'
  # to check which one it is, use boolean methods:
  # res.success? or res.failure?

  if res.success?
    puts "client_version: #{res.result.version}"
  else
    puts "client_version error: #{res.error}"
  end

end

In this case, the method version() requires only a context object. But most others require an additional 2nd argument appropriate for a certain method. Note that some methods, such some of the Processing, Net, Tvm modules, will continue to run for some time asynchronously delivering a result to a user, for instance, Processing.process_message(...) will do it via a callback

  my_callback = Proc.new do |a|

    # will be triggered multiple times, asynchronously
    puts "callback fired: #{a}"
  end

  pr1 = EverSdk::Processing::ParamsOfProcessMessage.new(
    message_encode_params: encode_params,
    send_events: true
  )

  EverSdk::Processing.process_message(@c_ctx.context, pr1, my_callback) do |a|
    # [.......]
  end

while other methods will deliver a result relatively fast, without a callback, and terminate.

• https://docs.ton.dev/86757ecb2/p/7941cd-what-is-ton-os
• https://github.com/tonlabs/ever-sdk/tree/master/docs
• https://github.com/tonlabs/ever-sdk/blob/master/tools/api.json

Mind the current version of SDK when reading documentation and examples at https://github.com/tonlabs/ever-sdk

Clone the repository

git clone git@github.com:radianceteam/everscale-client-ruby.git
cd everscale-client-ruby

gem install ffi concurrent-ruby rspec

There may be other dependencies too, check the gemspec file for the full list of them.

Being dependent on the environment and OS, the gem ffi may produce errors during installation; should it happen, check out its repository https://github.com/ffi/ffi and search for pointers there.

Rspec is used for the tests, which are located in the spec directory. To run all the tests:

rspec

or run a specific set of the tests:

rspec spec/boc_spec.rb

The examples are located in the examples directory. Run them from the root directory of the gem to avoid issues with paths, for instance:

ruby ./examples/crypto.rb

random sign keys:
  public: f19eb4d77f081a562169005a8de3c1ff531c921e6788e30535ab89f0746811e7
  secret: da9aab4e2a57acf083e7abf0dae1274e21e13b0c530271734e135e9cf7b4a228

factorize
  ["494C553B", "53911073"]

• MacOS Catalina 10.15.5
• Arch Linux x86_64

• Wiki of the gem FFI: https://github.com/ffi/ffi/wiki ; callbacks: https://github.com/ffi/ffi/wiki/Callbacks
• https://stackoverflow.com/questions/60689128/ruby-ffi-callback-return-values

• Rspec validators or matchers don't work in a block of a non main thread, therefore in the tests an intermediate variable is used to save a result, a block, and then validate it outside of a block.
• Testing asynchronous code in Ruby is difficult and can incur hacks. Not all asynchronous code should be tested automatically via Rspec or other libraries, some should be instead tested manually once and then left alone thereafter: https://www.mikeperham.com/2015/12/14/how-to-test-multithreaded-code
• In some of the tests of the gem a "sleep" loop with a timeout are used to wait for an asynchronous operation to deliver a result, and this approach will do, although it can be replaced with a more idiomatic one. Oweing to the side effects, at times some tests may fail. When it happens, try to increase a timeout:

timeout_at = get_timeout_for_async_operation

# before, 5 seconds by default
sleep(0.1) until @res || get_now >= timeout_at

# after, longer timeout
sleep(0.1) until @res || get_now >= (timeout_at * 2)

• Tonlabs.io
• Radiance team
• Alex Maslakov

Apache 2.0; see the LICENSE file

See the CHANGELOG file

• Everscale News on Telegram https://t.me/everscale_news
• Everscale DEV Tools & SDK Telegram chat https://t.me/ever_sdk
• Everscale