Skip to content

Add support for testnet #15

@venzen

Description

@venzen

It is not enough to simply specify the port, it seems that due to a different magic in the message header, testnet doesn't accept connection and throws the following error:

PROCESSMESSAGE: INVALID MESSAGESTART

Perhaps add a default argument to BitcoinClient and BitcoinBasicClient?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions