So if I understand correctly, starting may 15th, you can't use armory on the BCH chain anymore?
Entirely depends on the span of the new HF. If it's just a block size increase and new opcodes, Armory should still "work" provided the network magic word part is fixed.
Honestly, it would probably take me a single day to deal with this stuff assuming all they did was to increase the block size. I don't do it because I refuse to give up development time for BCH.
Got it, thank you for your hard work!
It works if you just remove some checks for the network magic, those was only added in the last update, peers for other chains will still be banned so it could only lead initial to some more wrong connections from and to your node.
See:
https://bitcointalk.org/index.php?topic=2070058.msg37065819#msg37065819
For now I think its the best solution, its not the optimal solution but that way you could still use armory and also update armory without needing to edit or add own code.
You just need to make sure you remove the checks also in future updates on Bitcoin Cash. ( I assume the checks wont be updated much so should be easy to find and remove it in future versions as well ).
Thanks, the problem is, as stupid as it may sound, that I don't really know how to download the code and build it with the changes, it will probably take me 2-3 days to do just that.
I would have done that don't get me wrong but I think that this is a bad practice.
goatpig don't want to support BCH which is his right and I respect it.
So now for each new version of both armory and BCH you will have to find more and more workarounds to make it work which is really a bad practice.
Armory is for BTC.
I think it is best to just find another wallet for BCH. Any Ideas?
I don't have much time atm else I would create a patch for either BitcoinABC or Armory.
I'm pretty sure that the BitcoinABC devs would include the patch if it only allows Armory to connect without the magic check.
Best practice would be probably if someone with time would fork armory and create and maintain a BCH version.
I don't expect or demand that Goatpig keeps supporting it.
It's also unlikely that the code for the magic checks will be changed in the future as it does what it should do, so on updates you probably only need to update the same file and comment out the same checks.
I know its not the best practice but its pretty quick and works for now.