dpay-ruby
DPay-ruby the Ruby API for DPay blockchain.
Full documentation: http://www.rubydoc.info/gems/dpay-ruby
Note: This library depends on AppBase methods that are a work in progress.
radiator
vs. dpay-ruby
The dpay-ruby
gem was written from the ground up by @inertia
, who is also the author of radiator
.
"I intend to continue work on
radiator
indefinitely. But inradiator-0.5
, I intend to refactorradiator
so that is usesdpay-ruby
as its core. This means that some features ofradiator
like Serialization will become redundant. I think it's still useful for radiator to do its own serialization because it reduces the number of API requests." - @inertia
radiator |
dpay-ruby |
---|---|
Has internal failover logic | Can have failover delegated externally |
Passes error responses to the caller |
Handles error responses and raises exceptions |
Supports tx signing, does its own serialization | Also supports tx signing, but delegates serialization to database_api.get_transaction_hex
|
All apis and methods are hardcoded | Asks jsonrpc what apis and methods are available from the node |
(radiator-0.4.x ) Only supports AppBase but relies on condenser_api
|
Only supports AppBase but does not rely on condenser_api (WIP)
|
Small list of helper methods for select ops (in addition to build your own transaction) | Complete implementation of helper methods for every op (in addition to build your own transaction) |
Does not (yet) support json-rpc-batch requests |
Supports json-rpc-batch requests |
Getting Started
The dpay-ruby gem is compatible with Ruby 2.2.5 or later.
Install the gem for your project
(Assuming that Ruby is installed on your computer, as well as RubyGems)
To install the gem on your computer, run in shell:
gem install dpay-ruby
... then add in your code:
require 'dpay'
To add the gem as a dependency to your project with Bundler, you can add this line in your Gemfile:
gem 'dpay-ruby', require: 'dpay'
Examples
Broadcast Vote
params = {
voter: voter,
author: author,
permlink: permlink,
weight: weight
}
DPay::Broadcast.vote(wif: wif, params: params) do |result|
puts result
end
See: Broadcast
Streaming
The value passed to the block is an object, with the keys: :type
and :value
.
stream = DPay::Stream.new
stream.operations do |op|
puts "#{op.type}: #{op.value}"
end
To start a stream from a specific block number, pass it as an argument:
stream = DPay::Stream.new
stream.operations(at_block_num: 9001) do |op|
puts "#{op.type}: #{op.value}"
end
You can also grab the related transaction id and block number for each operation:
stream = DPay::Stream.new
stream.operations do |op, trx_id, block_num|
puts "#{block_num} :: #{trx_id}"
puts "#{op.type}: #{op.value}"
end
To stream only certain operations:
stream = DPay::Stream.new
stream.operations(types: :vote_operation) do |op|
puts "#{op.type}: #{op.value}"
end
Or pass an array of certain operations:
stream = DPay::Stream.new
stream.operations(types: [:comment_operation, :vote_operation]) do |op|
puts "#{op.type}: #{op.value}"
end
Or (optionally) just pass the operation(s) you want as the only arguments. This is semantic sugar for when you want specific types and take all of the defaults.
stream = DPay::Stream.new
stream.operations(:vote_operation) do |op|
puts "#{op.type}: #{op.value}"
end
To also include virtual operations:
stream = DPay::Stream.new
stream.operations(include_virtual: true) do |op|
puts "#{op.type}: #{op.value}"
end
Multisig
You can use multisignature to broadcast an operation.
params = {
voter: voter,
author: author,
permlink: permlink,
weight: weight
}
DPay::Broadcast.vote(wif: [wif1, wif2], params: params) do |result|
puts result
end
In addition to signing with multiple wif
private keys, it is possible to also export a partially signed transaction to have signing completed by someone else.
builder = DPay::TransactionBuilder.new(wif: wif1)
builder.put(vote: {
voter: voter,
author: author,
permlink: permlink,
weight: weight
})
trx = builder.sign.to_json
File.open('trx.json', 'w') do |f|
f.write(trx)
end
Then send the contents of trx.json
to the other signing party so they can privately sign and broadcast the transaction.
trx = open('trx.json').read
builder = DPay::TransactionBuilder.new(wif: wif2, trx: trx)
api = DPay::CondenserApi.new
trx = builder.transaction
api.broadcast_transaction_synchronous(trx: trx)
Get Accounts
api = DPay::DatabaseApi.new
api.find_accounts(accounts: ['dsite', 'alice']) do |result|
puts result.accounts
end
See: Api
Reputation Formatter
rep = DPay::Formatter.reputation(account.reputation)
puts rep
Tests
- Clone the client repository into a directory of your choice:
git clone https://github.com/dpays/dpay-ruby.git
- Navigate into the new folder
cd dpay-ruby
- All tests can be invoked as follows:
bundle exec rake test
- To run
static
tests:bundle exec rake test:static
- To run
broadcast
tests (broadcast is simulated, onlyverify
is actually used):bundle exec rake test:broadcast
- To run
threads
tests (which quickly verifies thread safety):bundle exec rake test:threads
- To run
testnet
tests (which does actual broadcasts)TEST_NODE=https://testnet.dpays.io bundle exec rake test:testnet
You can also run other tests that are not part of the above test
execution:
- To run
block_range
, which streams blocks (usingjson-rpc-batch
)bundle exec rake stream:block_range
If you want to point to any node for tests, instead of letting the test suite pick the default, set the environment variable to TEST_NODE
, e.g.:
$ TEST_NODE=https://testapi.dpays.io bundle exec rake test
Contributions
Patches are welcome! Contributors are listed in the dpay-ruby.gemspec
file. Please run the tests (rake test
) before opening a pull request and make sure that you are passing all of them. If you would like to contribute, but don't know what to work on, check the issues list.
Issues
When you find issues, please report them!
License
MIT