79d79012d4
It should be possible to check to see if a message isForMe with only the scanKeypair, and not the payloadKeypair. There was a bug where only the scanKeypair was being used to produce the receiveKeypair, but this was a mistake. Both the scanPubkey and payloadPubkey should be necessary to produce the receivePubkey, and both the scanPrivkey and payloadPrivkey should be necessary to produce the receivePrivkey. If an online computer has only the public keys of both (and the scanPrivkey), then that is good enough to check for isForMe. |
||
|---|---|---|
| browser | ||
| examples | ||
| lib | ||
| test | ||
| .gitignore | ||
| index.js | ||
| LICENSE.md | ||
| npm-shrinkwrap.json | ||
| package.json | ||
| README.md | ||
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 stealtha 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:
- Stealth addresses
- Proper handling of reading and writing big varInts
- Browserifiable
- A proper point class
- Better test coverage
- Proper message signing and verification
- npm-shrinkwrap.json ensures npm install works as intended
- byte-for-byte reading/writing scripts