Quote from: OutCast3k on August 23, 2017, 08:21:56 AM

---snip---

As much as I personally do not support the bitcoin cash hard fork, allowing users to dump it is probably a good thing.

I am reviewing and testing this pull request, but I am also aware that there are a few very minor issues in this pull request, which leaves me wondering if they should be fixed before or after.

Quote from: OutCast3k on September 30, 2017, 07:19:56 AM

---snip---

Bitcoin cash and bitcoin do not use the same sighashes as a method of replay protection. This means transactions built for the bitcoin network can't be broadcasted to the bcash network with out an update to the signing procedure.

There is a bitcoin cash pull request on the github repo, which I've not accepted but it does work (I choose to support segwit right now over bcash) You can download it and use it to create transactions for the bcash network.

so I take it you will never going to merge that BCH pull request?
you were talking about pull #113 by dabura667, right?
which finally he forked to https://github.com/dabura667/coinbin/tree/bitcoincash

Quote from: Pente on October 01, 2017, 07:32:02 PM

---snip---

We can recover BCH, but apparently we will have to sign the transaction while online, so not 100% secure.

It would be possible to rewrite the code to allow offline signing, but I don't think anyone will be motivated enough to do that.

what do you mean by "have to sign the transaction while online"
is this new procedure? I've never heard signing tx must be online connected to any network