Skip to content
This repository was archived by the owner on Apr 3, 2019. It is now read-only.

Conversation

@braydonf
Copy link
Contributor

@braydonf braydonf commented Feb 4, 2016

Brings better compatibility between "testnet" and "regtest". Services such as
Bitcore Wallet Service and wallets such as Copay that have "testnet" and not
"regtest" will be compatible with "regtest" if enabled in a Bitcore node. This
adds two new API methods to enable/disable regtest on the testnet network:

  • bitcore.Networks.enableRegtest()
  • bitcore.Networks.disableRegtest()

Closes: bitpay/bitcore#1190

Brings better compatibility between "testnet" and "regtest". Services such as
Bitcore Wallet Service and wallets such as Copay that have "testnet" and not
"regtest" will be compatible with "regtest" if enabled in a Bitcore node. This
adds two new API methods to enable/disable regtest on the testnet network:
- `bitcore.Networks.enableRegtest()`
- `bitcore.Networks.disableRegtest()`
@fanatid
Copy link
Contributor

fanatid commented Feb 4, 2016

👍

@gabegattis
Copy link
Contributor

reviewing...

@gabegattis
Copy link
Contributor

Looks good to me. I npm linked this to a bitcore node with the following patch braydonf/bitcore-node@6e8f3ee and set my bitcore-node.json network to "regtest". The node runs fine. I connected it to a separate bitcoin qt regtest node and it synced up.

I ran insight-api, insight-ui, and bitcore-wallet-service on the bitcore node. Insight worked properly, copay worked properly and I was able to send funds between copay and bitcoin qt.

There is only one issue. On the status page of insight, under "bitcoin node information", it says testnet is false. This can be changed to simply display the network name instead of a boolean, but I think that is beyond the scope of this issue. see bitpay/insight#702

gabegattis added a commit that referenced this pull request Feb 4, 2016
Networks: Added regtest to networks
@gabegattis gabegattis merged commit 9702105 into bitpay:master Feb 4, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants