A javascript Bitcoin library for node.js and browsers.

Find a file

Daniel Cousens a006e9a4ef travis: add standard test suite		2015-02-24 12:45:38 +11:00
src	use standardjs formatting	2015-02-24 12:45:38 +11:00
test	use standardjs formatting	2015-02-24 12:45:38 +11:00
.gitignore	package: remove uglify-js	2015-02-12 14:39:38 +11:00
.npmignore	adds .npmignore	2015-01-13 22:24:19 +11:00
.travis.yml	travis: add standard test suite	2015-02-24 12:45:38 +11:00
jshint.json	JSHint: add max line length 120	2014-06-04 15:55:25 +10:00
LICENSE	Updated license date	2015-01-01 11:41:21 +00:00
package.json	travis: add standard test suite	2015-02-24 12:45:38 +11:00
README.md	README: update decentralbank URL	2015-02-24 12:33:55 +11:00

README.md

BitcoinJS (bitcoinjs-lib)

The pure JavaScript Bitcoin library for node.js and browsers. A continued implementation of the original 0.1.3 version used by over a million wallet users; the backbone for almost all Bitcoin web wallets in production today.

Features

Clean: Pure JavaScript, concise code, easy to read.
Tested: Coverage > 90%, third-party integration tests.
Careful: Two person approval process for small, focused pull requests.
Compatible: Works on Node.js and all modern browsers.
Powerful: Support for advanced features, such as multi-sig, HD Wallets.
Secure: Strong random number generation, PGP signed releases, trusted developers.
Principled: No support for browsers with crap RNG (IE < 11)
Standardized: Node community coding style, Browserify, Node's stdlib and Buffers.
Fast: Optimized code, uses typed arrays instead of byte arrays for performance.
Experiment-friendly: Bitcoin Mainnet and Testnet support.
Altcoin-ready: Capable of working with bitcoin-derived cryptocurrencies (such as Dogecoin).

Should I use this in production?

If you are thinking of using the master branch of this library in production, stop. Master is not stable; it is our development branch, and only tagged releases may be classified as stable.

If you are looking for the original, it is tagged as 0.1.3. Unless you need it for dependency reasons, it is strongly recommended that you use (or upgrade to) the newest version, which adds major functionality, cleans up the interface, fixes many bugs, and adds over 1,300 more tests.

Installation

npm install bitcoinjs-lib

Setup

Node.js

var bitcoin = require('bitcoinjs-lib')

Browser

If you're familiar with how to use browserify, ignore this and proceed normally. These steps are advisory only and allow you to use the API to its full extent.

Browserify is assumed to be installed for these steps.

From your repository, create a foobar.js file

var foobar = {
  base58: require('bs58'),
  bitcoin: require('bitcoinjs-lib'),
  ecurve: require('ecurve'),
  BigInteger: require('bigi'),
  Buffer: require('buffer')
}

module.exports = foobar

Each of these included packages are seperate to bitcoinjs-lib, and must be installed separately. They are however used in the bitcoinjs-lib public API.

Using browserify, compile foobar.js for use in the browser:

$ browserify foobar.js -s foobar > foobar.js

You will then be able to load foobar.js into your browser, with each of the dependencies above accessible from the global foobar object.

NOTE: See our package.json for the currently supported version of browserify used by this repository.

Examples

The below examples are implemented as integration tests, they should be very easy to understand. Otherwise, pull requests are appreciated.

Projects utilizing BitcoinJS

Contributors

Stefan Thomas is the inventor and creator of this project. His pioneering work made Bitcoin web wallets possible.

Since then, many people have contributed. Click here to see the comprehensive list.

Daniel Cousens, Wei Lu, JP Richardson and Kyle Drake lead the major refactor of the library from 0.1.3 to 1.0.0.

Contributing

Join the ongoing IRC development channel at #bitcoinjs-dev on Freenode. We are always accepting of Pull requests, but we do adhere to specific standards in regards to coding style, test driven development and commit messages.

Please make your best effort to adhere to these when contributing to save on trivial corrections.

Running the test suite

$ npm test
$ npm run-script coverage