How Memo is handling the BCH fork: https://memo.cash/bch-fork
hmm, it seems like non-enforcing of no-split-protocol will be a pain for the future-implementers of memo-protocol; what if someone with SV-coins replies to a post made with ABC-coins?
In theory this could be distributed outside of the normal upgrade cycle if it's just a node configuration.
I think you're right. Just a matter of getting enough momentum of miners to change the setting, but it may be good to just remove the setting entirely. It seems "anti-usage".
Everyone, let’s do another stress test on 10/1. I used 1.1 BCH on last test. I’ll commit 2 BCH to this one. I’ll be using Txblaster2 and Txblaster3. How do we move forward?