Go to file

Ryan X. Charles cfd509f859 make receivePubkey compatible with dark wallet I had been using this formula for the receiveKeypair: scanKeypair + payloadKeypair + sharedKeypair However, Dark Wallet uses this formula: payloadKeypair + sharedKeypair It is not actually necessary to add the scanKeypair in order to have all the features of stealth addresses, at least as far as I can tell. So in order to bring my implementation closer to Dark Wallet's, I have removed the scanKeypair from this calculation.		2014-09-19 14:32:32 -07:00
browser	rename bundle from privsec to bitcore	2014-09-01 14:59:42 -07:00
examples	update blockreader example to use toJSON	2014-09-18 17:52:43 -07:00
lib	make receivePubkey compatible with dark wallet	2014-09-19 14:32:32 -07:00
test	make receivePubkey compatible with dark wallet	2014-09-19 14:32:32 -07:00
.gitignore	rename bundle from privsec to bitcore	2014-09-01 14:59:42 -07:00
.travis.yml	add travis file	2014-09-17 16:56:36 -07:00
LICENSE.md	refine copyright	2014-08-19 11:57:15 -07:00
README.md	typo	2014-09-19 14:02:44 -07:00
index.js	expose	2014-09-17 17:36:59 -07:00
npm-shrinkwrap.json	update dependencies	2014-09-18 18:46:31 -07:00
package.json	update dependencies	2014-09-18 18:46:31 -07:00

bitcore2

Bitcore 2 is a rewrite of bitcore. It is alpha quality. It will ultimately be merged into upstream bitcore.

Our goals:

Support ease-of-use by being internally consistent. It should not be necessary to read the source code of a class or function to know how to use it. I.e., where in old bitcore a "privkey" might be anything from a buffer to a hex string to a key to a private key object, in bitcore 2 "privkey" is the same type of object always and everywhere.
Have 100% test coverage so that the library is known to be reliable.
Library objects have an interface suitable for use with a command-line interface and API, in particular having toString, fromString, toObject, fromObject methods.
All standard features of the bitcoin protocol are implemented and saved in lib/. All BIPs are correctly implemented and saved as BIPxx.js in lib/ (since that is their standard name). Any non-standard features (such as SINs and stealth addresses) are placed in the lib/expmt/ folder and are accessible at bitcore.expmt. Once they are standardized and given a BIP, they are renamed and placed in lib/.
It is always possible to create a new object without using "new".
Compatible with browserify (i.e., using require('bitcore/lib/message') should work both in node, and be automatically work in the browser with used in conjunction with browserify).
Minimize the use of dependencies so that all code can be easily audited.
All instance methods modify the state of the object and return the object. To access the result of an instance method, you must access the object property(s) that it modifies.

Features over bitcore: