dpay-ruby 0.1.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 23e94a17964a441a5b98383fc3946f6643a0c94d93a958bbc59a72bd1b2323d9
+  data.tar.gz: 9cb30fe0becefc5553244ae21dbb3ce3e6c676f4be47454a7d30ca7c42b72ffe
+SHA512:
+  metadata.gz: 520176a45c078bd306c3a9fa37cb8b2433ab56fe2161d8b3dd08262133f73eae1f0d9c2f6e211b45b0d58ef1f2b3b4033fbc80d4997e394fcc3316ddbd156fb0
+  data.tar.gz: 20730173de19fa99069dc2a6512a6e79ae13fbbea2e1a99c16594ea4ead05fa5a82467d2039aa9fdc6a51999a7b79e8e3be461437c0d976b6d3eb07f1d8e3281

data/.gitignore

@@ -0,0 +1,54 @@
+*.gem
+*.rbc
+/.config
+/coverage/
+/InstalledFiles
+/pkg/
+/spec/reports/
+/spec/examples.txt
+/test/tmp/
+/test/fixtures/vcr_cassettes/*.yml
+/test/version_tmp/
+/tmp/
+
+# Used by dotenv library to load environment variables.
+# .env
+
+## Specific to RubyMotion:
+.dat*
+.repl_history
+build/
+*.bridgesupport
+build-iPhoneOS/
+build-iPhoneSimulator/
+
+## Specific to RubyMotion (use of CocoaPods):
+#
+# We recommend against adding the Pods directory to your .gitignore. However
+# you should judge for yourself, the pros and cons are mentioned at:
+# https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control
+#
+# vendor/Pods/
+
+## Documentation cache and generated files:
+/.yardoc/
+/_yardoc/
+/doc/
+/rdoc/
+
+## Environment normalization:
+/.bundle/
+/vendor/bundle
+/lib/bundler/man/
+
+# for a library or gem, you might want to ignore these files since the code is
+# intended to run in multiple environments; otherwise, check them in:
+# Gemfile.lock
+# .ruby-version
+# .ruby-gemset
+
+# unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
+.rvmrc
+
+# gource output
+output.mp4

data/CONTRIBUTING.md

@@ -0,0 +1,79 @@
+
+# Contributing
+
+Everyone is welcome to contribute code to dPay DAO projects. We have a Code of Conduct;
+we ask that you please follow it in all your interactions with our team and your fellow
+contributors.
+
+Please note that this contributing guide only applies to our development presence.
+
+## How to contribute
+
+1. File an issue describing the problem you would like to
+   solve or the feature you would like to add. It saves unnecessary work on your part,
+   in case there's a nontechnical reason we can't accept a particular change.
+   Please note that we can and will _automatically close all pull requests that do not refer to
+   an issue_.
+2. Learn the conventions of the project you are submitting code to, even implicit ones,
+   and follow them. In case you have a question about a project's conventions, please
+   ask on the issue you filed. This includes writing tests, formatting code, and documentation.
+3. File a pull request against your Github issue and fill out the pull request template.
+   Remember, you are agreeing to license your code and any intellectual property associated
+   with your code under the same terms as the repository you are contributing to.
+4. If one of our teammates asks you to make changes, please make them. Our rule is that all
+   requests for changes in code review are resolved in favor of the reviewer. Our teammates
+   follow this rule too!
+
+## Code of Conduct
+
+Again, please note that this Code of Conduct _only applies to our development presence_.
+
+### Our Pledge
+
+We welcome your membership in our project and community under the rules that we have set below.
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers will work to make your participation in
+our project and community as fulfilling as possible.
+
+### Our Rules
+
+All members of our project and community must:
+
+1.  Show empathy toward other project and community members
+2.  Use welcoming and inclusive language
+3.  Respect differing viewpoints and experiences
+4.  Gracefully accept constructive criticism
+
+All members of our project and community must not:
+
+1.  Harm our project and community, or advocate harm to our project and community
+2.  Insult or make derogatory comments about others
+3.  Interact with others after they have withdrawn permission to do so
+
+### Our Responsibilities
+
+We will use any and all lawful means at our disposal to enforce our rules. This includes
+but is not limited to:
+
+1.  Rejecting contributions
+2.  Removing comments, commits, code, wiki edits, and issues
+3.  Banning abusers
+
+We will clarify standards of acceptable behavior and we will take appropriate
+and fair corrective action in response to any instances of unacceptable behavior.
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting us at github.abuse@dpays.io. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. We
+maintain strict confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+### Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/gg

data/Gemfile

@@ -0,0 +1,3 @@
+source 'https://rubygems.org'
+
+gemspec

data/Gemfile.lock

@@ -0,0 +1,73 @@
+PATH
+  remote: .
+  specs:
+    dpay-ruby (0.1.1)
+      bitcoin-ruby (~> 0.0, >= 0.0.18)
+      ffi (~> 1.9, >= 1.9.23)
+      hashie (~> 3.5, >= 3.5.7)
+      json (~> 2.1, >= 2.1.0)
+      logging (~> 2.2, >= 2.2.0)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    addressable (2.5.2)
+      public_suffix (>= 2.0.2, < 4.0)
+    awesome_print (1.8.0)
+    bitcoin-ruby (0.0.18)
+    coderay (1.1.2)
+    crack (0.4.3)
+      safe_yaml (~> 1.0.0)
+    docile (1.3.1)
+    ffi (1.9.25)
+    hashdiff (0.3.7)
+    hashie (3.5.7)
+    json (2.1.0)
+    little-plugger (1.1.4)
+    logging (2.2.2)
+      little-plugger (~> 1.1)
+      multi_json (~> 1.10)
+    method_source (0.9.0)
+    minitest (5.11.3)
+    minitest-line (0.6.5)
+      minitest (~> 5.0)
+    minitest-proveit (1.0.0)
+      minitest (> 5, < 7)
+    multi_json (1.13.1)
+    pry (0.11.3)
+      coderay (~> 1.1.0)
+      method_source (~> 0.9.0)
+    public_suffix (3.0.2)
+    rake (12.3.1)
+    safe_yaml (1.0.4)
+    simplecov (0.16.1)
+      docile (~> 1.1)
+      json (>= 1.8, < 3)
+      simplecov-html (~> 0.10.0)
+    simplecov-html (0.10.2)
+    vcr (4.0.0)
+    webmock (3.4.2)
+      addressable (>= 2.3.6)
+      crack (>= 0.3.2)
+      hashdiff
+    yard (0.9.15)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  awesome_print (~> 1.8, >= 1.8.0)
+  bundler (~> 1.16, >= 1.16.1)
+  dpay-ruby!
+  minitest (~> 5.10, >= 5.10.3)
+  minitest-line (~> 0.6, >= 0.6.4)
+  minitest-proveit (~> 1.0, >= 1.0.0)
+  pry (~> 0.11, >= 0.11.3)
+  rake (~> 12.3, >= 12.3.0)
+  simplecov (~> 0.15, >= 0.15.1)
+  vcr (~> 4.0, >= 4.0.0)
+  webmock (~> 3.3, >= 3.3.0)
+  yard (~> 0.9, >= 0.9.12)
+
+BUNDLED WITH
+   1.16.2

data/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2018 dpay-ruby
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+

data/README.md

@@ -0,0 +1,250 @@
+[![Gem Version](https://badge.fury.io/rb/dpay-ruby.svg)](https://badge.fury.io/rb/dpay-ruby)
+[![Inline docs](http://inch-ci.org/github/dpays/dpay-ruby.svg?branch=master&style=shields)](http://inch-ci.org/github/dpays/dpay-ruby)
+
+# `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`](https://github.com/inertia186/radiator).
+
+> "I intend to continue work on `radiator` indefinitely. But in `radiator-0.5`, I intend to refactor `radiator` so that is uses `dpay-ruby` as its core. This means that some features of `radiator` 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](https://www.ruby-lang.org/en/downloads/) on your computer, as well as [RubyGems](http://rubygems.org/pages/download))*
+
+To install the gem on your computer, run in shell:
+
+```bash
+gem install dpay-ruby
+```
+
+... then add in your code:
+
+```ruby
+require 'dpay'
+```
+
+To add the gem as a dependency to your project with [Bundler](http://bundler.io/), you can add this line in your Gemfile:
+
+```ruby
+gem 'dpay-ruby', require: 'dpay'
+```
+
+## Examples
+
+### Broadcast Vote
+
+```ruby
+params = {
+  voter: voter,
+  author: author,
+  permlink: permlink,
+  weight: weight
+}
+
+DPay::Broadcast.vote(wif: wif, params: params) do |result|
+  puts result
+end
+```
+
+*See: [Broadcast](https://www.rubydoc.info/gems/dpay-ruby/DPay/Broadcast)*
+
+### Streaming
+
+The value passed to the block is an object, with the keys: `:type` and `:value`.
+
+```ruby
+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:
+
+```ruby
+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:
+
+```ruby
+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:
+
+```ruby
+stream = DPay::Stream.new
+
+stream.operations(types: :vote_operation) do |op|
+  puts "#{op.type}: #{op.value}"
+end
+```
+
+Or pass an array of certain operations:
+
+```ruby
+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.
+
+```ruby
+stream = DPay::Stream.new
+
+stream.operations(:vote_operation) do |op|
+  puts "#{op.type}: #{op.value}"
+end
+```
+
+To also include virtual operations:
+
+```ruby
+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.
+
+```ruby
+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.
+
+```ruby
+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.
+
+```ruby
+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
+
+```ruby
+api = DPay::DatabaseApi.new
+
+api.find_accounts(accounts: ['dsite', 'alice']) do |result|
+  puts result.accounts
+end
+```
+
+*See: [Api](https://www.rubydoc.info/gems/dpay-ruby/DPay/Api)*
+
+### Reputation Formatter
+
+```ruby
+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, only `verify` 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 (using `json-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.:
+
+```bash
+$ 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