Changing the year to 2018. Added a dummy unit test for initial example.

cryptocurrent · Jan 7, 2018 · 427eb19 · 427eb19
1 parent b859c0d
commit 427eb19
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 5 deletions.
diff --git a/README.md b/README.md
@@ -1,10 +1,10 @@
 ```
 ____   _________________________   ________ ___________
 \   \ /   /\_   _____/\______   \ /  _____/ \_   _____/
- \   Y   /  |    __)_  |       _//   \  ___  |    __)_ 
-  \     /   |        \ |    |   \\    \_\  \ |        \ 2016 VERGE
+ \   Y   /  |    __)_  |       _//   \  ___  |    __)_
+  \     /   |        \ |    |   \\    \_\  \ |        \ 2018 VERGE
    \___/   /_______  / |____|_  / \______  //_______  /
-                   \/         \/         \/         \/ 
+                   \/         \/         \/         \/
 ```
 # A Node.js VERGE Client
 node-verge is a VERGE client for node.js
@@ -290,7 +290,7 @@ All [Litecoin API](https://litecoin.info/Litecoin_API) commands are supported, i
 </li><li> "hash1": formatted hash buffer for second hash
 </li><li> "target": little endian hash target
 </li></ul>
-<p>If [data] is specified, tries to solve the block and returns true if it was successful. 
+<p>If [data] is specified, tries to solve the block and returns true if it was successful.
 </p>
 </td>
 <td> N
@@ -523,7 +523,7 @@ By default `verged` exposes its JSON-RPC interface via HTTP; that is, all RPC co
     rpcsslprivatekeyfile=/etc/ssl/private/verged.pem
 
 In order to securely access an SSL encrypted JSON-RPC interface you need a copy of the self-signed certificate from the server: in this case `verged.crt`. Pass your self-signed certificate in the `ca` option and set `https: true` and node-verge is secured!
-    
+
 ```js
 var fs = require('fs')
 

diff --git a/test/test-node-verge.js b/test/test-node-verge.js
@@ -0,0 +1,5 @@
+exports.testSomething = function(test) {
+    test.expect(1);
+    test.ok(true, "this assertion should pass");
+    test.done();
+};