[bitcoinxt/bitcoinxt]: Don't require CASH service bit for outgoing connections

[chaintip]

Repository: bitcoinxt/bitcoinxt
Issue #309: Don't require CASH service bit for outgoing connections

BU is removing the service bit NODE_BITCOIN_CASH, relying only on the network magic in BitcoinUnlimited/BitcoinUnlimited#905

We require this flag for outgoing connections. This means that XT will no longer make outgoing connections to Bitcoin Unlimited nodes.

We need to remove this requirement, preferably before the May network upgrade. We should also sunset announcing the NODE_BITCOIN_CASH service bit. Perhaps one year from now.

---

Total Bounty: 0 BCH| ~ 0.00 USD

To claim this bounty, get a pull request merged with @chaintip fixes #309 in the creation comment.

Returned Tips:

• 0.00068166 BCH| ~ 0.28 USD from tea-spoon returned 3 years ago.
• 0.003 BCH| ~ 1.23 USD from dagurval returned 3 years ago.

[dagurval]

This is neat. Is it possible for me or others to add to the bounty? Why not have a permanent address in this issue?

[chaintip]

Thanks. Each mention of @chaintip in the issue creates a unique holding address to pay. You can send to the same one and an amount will (if it's working as it should) be added to the bounty and the first on-chain tip. If you mention @chaintip again another address is given to you for another on-chain tip. I can't use the same address for a single issue because I need to know who has sent the money so that I can send the refund back to them if the issue is not fixed in time. I'll add to bit more to this issue to make sure that it's working.