bring formatting in line with bitcore standards
significant progress towards bitcore compatibility

Cryptography updated to use bitcore methods rather than bitcoinjs.
Get test vector 1 working in node
make things work in the browser by fixing sha512

...had to use jsSHA package to do SHA512 in the browser. Unfortunately it is
quite slow compared to node.
all vector 2 tests work
remove obsolete commented-out code
add convenience constructor for making new bip32s

Added the ability to create a new master bip32 with new private key and chain code. The way this works is like this:

var bip32 = new BIP32('mainnet');

or:

var bip32 = new BIP32('testnet');
move version constants to networks.js

...with all the other network-specific constants.
expose group operation

BIP32 needs to be able to add two points on the secp256k1 curve. This
functionality was not already being exposed from OpenSSL in bitcore. I have
added an "addUncompressed" function to the Key class which takes in two points
in uncompressed form, adds them, and returns the result. This is necessary for
BIP32.
fix issue by outputing proper pubkey format

The way I was outputting the pubkeys would be incorrect if the first byte of
one of the coordinates was 0, since it would print the first non-zero byte
first. The solution was to use the standard openssl function that outputs a
public key to oct.
update BIP32 to be able to derive pubkeys

...using the new addCompressed interface in Key.js
remove redundant and slow test
remove commented-out code
Update README.md
Merge pull request #187 from mljsimone/master

Update README.md
script parsing should be more loose on pushdata

This testnet transaction was being parsed incorrectly:

cc64de74ba7002bbf4e3646824d7bbf0920004fb2ce45aa7270c4116ff11b715

Script was throwing an error when it should not have been. The error was that
PUSHDATA1 was trying to push 117 bytes to the stack, but it was followed by
only 75 bytes. But this transaction is accepted as valid by bitcoin-qt on
testnet. So we are mistaken by throwing an error in this case.
add test of correct parsing of valid script

Even of OP_PUSHDATA1 says to push 117 bytes, if there are only 75 bytes
following, this should still be pushed to the stack.
Merge pull request #188 from ryanxcharles/bug/script-push-data

script parsing should be more loose on pushdata
random transaction and script generation
add sighash tests