node-digibyte v0.3.9

A Node.js DogeCoin Client!

node-digibyte is a Digibyte client for Node.js. It is a fork of the excellent Kapitalize Bitcoin Client (now removed from GitHub) intended for use with Digibyte. The purpose of this repository is:

• Provide a one-stop resource for the Node.js developer to get started with Digibyte integration.
• Prevent would-be Digibyte web developers worrying whether a Bitcoin client will work out of the box.
• Promote Node.js development of Digibyte web apps.
• Identify and address any incompatibilities with the Digibyte and Bitcoin APIs that exist now and/or in the future.

Dependencies

You'll need a running instance of digibyted to connect with. If you're running Debian/Ubuntu, this worked for me: http://www.dogeco.in/wiki/index.php/Digibyted

Then, install the node-digibyte NPM package.

npm install node-digibyte

Examples

Some code examples follow below, but for more complete examples, see these snippets, or this wallet app which was created to to test this module.

var digibyte = require('node-digibyte')()

digibyte.auth('myusername', 'mypassword')

digibyte.getDifficulty(function() {
    console.log(arguments);
})

Chaining

Pretty much everything is chainable.

var digibyte = require('node-digibyte')()

digibyte
.auth('MyUserName', 'mypassword')
.getNewAddress()
.getBalance()

Methods

The Litecoin API is supported as direct methods. Use either camelcase or lowercase.

digibyte.getNewAddress(function(err, address) {
    this.validateaddress(address, function(err, info) {

    })
})

.exec(command string, ...arguments..., callback function)

Executes the given command with optional arguments. Function callback defaults to console.log. All of the API commands are supported in lowercase or camelcase. Or uppercase. Anycase!

digibyte.exec('getNewAddress')

digibyte.exec('getbalance', function(err, balance) {

})

.set(key string, object, value optional)

Accepts either key & value strings or an Object containing settings, returns this for chainability.

digibyte.set('host', '127.0.0.1')

.get(key string)

Returns the specified option's value

digibyte.get('user')

.auth(user string, pass string)

Generates authorization header, returns this for chainability

Commands

TODO: Write tests for these.

All Litecoin API commands are supported, in lowercase or camelcase form.

Generation is limited to genproclimit processors, -1 is unlimited.

Options

You may pass options to the initialization function or to the set method.

var digibyte = require('digibyte')({
    user:'user'
})

digibyte.set('pass', 'somn')
digibyte.set({port:22555})

Available options and default values:

• host localhost
• port 22555
• user
• pass
• passphrasecallback
• https
• ca

Passphrase Callback

With an encryped wallet, any operation that accesses private keys requires a wallet unlock. A wallet is unlocked using the walletpassphrase <passphrase> <timeout> JSON-RPC method: the wallet will relock after timeout seconds.

You may pass an optional function passphrasecallback to the node-digibyte initialization function to manage wallet unlocks. passphrasecallback should be a function accepting three arguments:

function(command, args, callback) {}

• command is the command that failed due to a locked wallet.
• args is the arguments for the failed command.
• callback is a typical node-style continuation callback of the form function(err, passphrase, timeout) {}. Call callback with the wallet passphrase and desired timeout from within your passphrasecallback to unlock the wallet.

You may hard code your passphrase (not recommended) as follows:

var digibyte = require('node-digibyte')({
    passphrasecallback: function(command, args, callback) {
        callback(null, 'passphrase', 30);
    }
})

Because passphrasecallback is a continuation, you can retrieve the passphrase in an asynchronous manner. For example, by prompting the user:

var readline = require('readline')

var rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout
})

var digibyte = require('node-digibyte')({
  passphrasecallback: function(command, args, callback) {
    rl.question('Enter passphrase for "' + command + '" operation: ', function(passphrase) {
      if (passphrase) {
        callback(null, passphrase, 1)
      } else {
        callback(new Error('no passphrase entered'))
      }
    })
  }
})

Secure RPC with SSL

By default digibyted exposes its JSON-RPC interface via HTTP; that is, all RPC commands are transmitted in plain text across the network! To secure the JSON-RPC channel you can supply digibyted with a self-signed SSL certificate and an associated private key to enable HTTPS. For example, in your digibyte.conf:

rpcssl=1
rpcsslcertificatechainfile=/etc/ssl/certs/digibyted.crt
rpcsslprivatekeyfile=/etc/ssl/private/digibyted.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 digibyted.crt. Pass your self-signed certificate in the ca option and set https: true and node-digibyte is secured!

var fs = require('fs')

var ca = fs.readFileSync('digibyted.crt')

var digibyte = require('node-digibyte')({
  user: 'rpcusername',
  pass: 'rpcpassword',
  https: true,
  ca: ca
})

Testing

npm install -g nodeunit

nodeunit test/test-node-digibyte.js

Bounties

Digibyte donation address is DE4isu3m2RBma7nGEwnaX8cu4Y2m2J2g8Q

Donations in digibyte will be used for bounties. The first bounty will be awarded for creating a unit test suite. As a side note: I encourage all GitHub repository owners to post a donation address so their community can easily support development financially. If you accept donations at your repository, I'll send you a reward!