Using with Bitcore about bitcore-message

[trevinhofmann]

I was also having this problem.

I ended up "fixing" it by modifying my local bitcore-message module by changing the sign function to this:

Message.prototype.sign = function sign(privateKey) {
  var privateKey = new PrivateKey(privateKey);
  var signature = this._sign(privateKey);
  return signature.toCompact().toString('base64');
};

Adding the new PrivateKey will cast it to a locally recognizable PrivateKey. This doesn't address the actual problem, but it does fix it.

[braydonf]

Updating the version required in bitcore-message to the same minor version of bitcore should fix this issue (fixed in #14 if you're using 0.11.x).

[olalonde]

For now, I just exposed bitcore on Message so that I can use that bitcore when creating private key:

master...olalonde:master

[maraoz]

should be good to go if you use latest npm versions of both modules (released today). Error messages were improved too. Let me know if the problem persists.