Skip to content

breaks if you use this with bitcore-lib-cash #31

@brad1121

Description

@brad1121

If you use this with bitcore-lib-cash you will get issues when trying to sign.

In particular

 throw new errors.InvalidArgument(argumentName, message, docsPath);
      ^
Invalid Argument: First argument should be an instance of PrivateKey

This is because bitcore-message requires bitcore-lib not bitcore-lib-cash as a dependency. Thus they reference a different instance of PrivateKey

Simple fix is to change the bitcore-lib dependency to bitcore-lib-cash to proceed.

Just a pain if you run npm update/install, you will have to change this back each time.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions