yolodice-client 0.1.1 → 0.1.2

Sign up to get free protection for your applications and to get access to all the features.
Files changed (3) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +3 -1
  3. metadata +2 -22
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: a3f9c18f4f343eb90b4b79ac9ea29947aa37e8cc
4
- data.tar.gz: 79d786b072ff58a346805ce4c6ac57bf9af8f3f8
3
+ metadata.gz: b770b33186e05e3fd16caee8bdb990aca0da7740
4
+ data.tar.gz: c60e4b8ac43202cb52b3f33deac511cebf0cbc71
5
5
  SHA512:
6
- metadata.gz: 4cd29705d3668b1fc29489fdc255efeb7b364085325cf482eb9e641aa95b7c242be4b7f90a36e30423029c120ce32658a1d6632999852975f21968f2b9b554db
7
- data.tar.gz: 5af05d6cb39c7693ff7df81040a936cdad27820ef5a82161e1257c22b23d152d05055bd658ee951f233f762a384ea822d1799a7206c3957cb051ffdf43642878
6
+ metadata.gz: 873a5a2542fa8da4ef04da2ba049b934117b7bb18eee723a39dae9fe4b45def756da1f58e462a1d6c9cbd2a5383ef3ffb99a4adc2c3c617e30577086ed861505
7
+ data.tar.gz: a7a8f91141abfc76fd481fb705fdba2541e5d1d3c9b7aa371b83e917207d857c570583ecce9ff438cad82d9196f0fd73f63cf8f4eae57e5ba3b1cc93ba8bd13f
data/README.md CHANGED
@@ -32,6 +32,7 @@ YOLOdice API requires authentication for most of it's methods. A Bitcoin key/add
32
32
 
33
33
  1. Generate an Bitcoin public and private key:
34
34
 
35
+
35
36
  require 'bitcoin'
36
37
 
37
38
  btc_key = Bitcoin::Key.generate
@@ -39,6 +40,7 @@ YOLOdice API requires authentication for most of it's methods. A Bitcoin key/add
39
40
  auth_addr = btc_key.addr # paste this in your YD settings as a new key
40
41
 
41
42
  2. Go to [YOLOdice account Settings](https://yolodice.com/#settings), create a new key and paste the `auth_addr` generated above. Set permissions as you wish.
43
+
42
44
  3. Use `auth_key` in your code to authenticate.
43
45
 
44
46
  Just a quick note — this address is used ONLY to authenticate. No coins will be ever sent to it.
@@ -95,7 +97,7 @@ There are two error classes:
95
97
 
96
98
  `RemoteError` has two extra attributes: `code` and `data` that are mapped to values in the error object returned from the server.
97
99
 
98
- ## Another example
100
+ ## An example
99
101
 
100
102
  Here is a script that connects to the server, authenticates, fetches user data, rolls a few 50% chance bets and reads user data again (make sure to use your own credential):
101
103
 
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: yolodice-client
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.1
4
+ version: 0.1.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - ethan_nx
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2017-02-09 00:00:00.000000000 Z
11
+ date: 2017-02-10 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: bitcoin-ruby
@@ -24,26 +24,6 @@ dependencies:
24
24
  - - "~>"
25
25
  - !ruby/object:Gem::Version
26
26
  version: 0.0.8
27
- - !ruby/object:Gem::Dependency
28
- name: hashie
29
- requirement: !ruby/object:Gem::Requirement
30
- requirements:
31
- - - "~>"
32
- - !ruby/object:Gem::Version
33
- version: '3.5'
34
- - - ">="
35
- - !ruby/object:Gem::Version
36
- version: 3.5.1
37
- type: :runtime
38
- prerelease: false
39
- version_requirements: !ruby/object:Gem::Requirement
40
- requirements:
41
- - - "~>"
42
- - !ruby/object:Gem::Version
43
- version: '3.5'
44
- - - ">="
45
- - !ruby/object:Gem::Version
46
- version: 3.5.1
47
27
  description: A simple JSON-RPC2 client dedicated for YOLOdice.com API.
48
28
  email:
49
29
  executables: []