BitcoinCash’s contested November 15th Hardfork


0) Introduction & General information
The BitcoinCash network is undergoing regular upgrades via scheduled hardforks every 6 months, the last of which happened on May 15th and included a maximum blocksize increase to 32MB and various opcode changes. Based on this schedule, the next hardfork would be due on November 15th. Unlike last time, though, there is no clear consensus about what kind of changes to be included in the upcoming November hardfork, and the way to approach it has been contested for the last couple of weeks, with two groups fighting over the direction into which they believe BitcoinCash should be going.
As this conflict does not seem to be resolved before the November 15th deadline, the BitcoinCash network is heading towards a possible chainsplit as result of the two proposed, incompatible hardforks. In this contingency plan, we’re going to have a look at the current situation on the BitcoinCash network, outline the preparations CryptoGames is taking in response to it, brief the process CryptoGames has previously established for similar situation (for example during the BTC/BCH split, the BTC/BTG split or the ETH/ETC split), and explain what you, as a user on CryptoGames have to do in order to ensure a smooth process through all of this.


1) The Situation of the BitcoinCash network
Who are these two groups and what are the differences in their proposed hardforks?
The two groups can be best described based on their clients. First off, there is the group around BitcoinABC (sometimes also called “BCHABC”). This group includes the following compatible implementations: BitcoinABC v0.18.3, BitcoinUnlimited v1.5.0.1, BitcoinXT Release K, and bcoin v1.1.0, which has yet to be released. Their proposed hardfork includes a change to canonical transaction ordering, newly added OpCodes, and a minimum transaction size limit.
The opposing group formed around the BitcoinSV client (equivalent to the first group also called “BCHSV”), with SV standing for Satoshi Vision. The group backing this implementation includes nChain, Craig Wright, and the mining pool CoinGeek. The main aspects of the hardfork proposed by BitcoinSV is the maximum blocksize increase to 128MB which is the biggest increase so far, and the reactivation of some old OpCodes initially added by Satoshi himself (thus the name of their implementation).
Other clients that have not yet released compatible versions for either of the proposed hardforks or client versions that are older than the thresholds and thus not compatible with the proposed hardforks will remain on the legacy chain and not undergo any hardfork.
If you are interested in an overview about the stance mining pools, nodes, and other service have regarding these two groups and the legacy chain, Coin.Dance has a statistics overview page dedicated to this hardfork.

What are the possible scenarios for the days after the fork arise from this situation?
There are a few possible ways in which this could play out. The outcome that is most likely to happen is the hardforks resulting in two split chains coexisting from this point, BitcoinCash ABC and BitcoinCash SV. Depending on whether or not the legacy chain is continued to be mined by some, there could not only be two, but three parallel chains fighting for the BitcoinCash name. It is however also possible, though less likely, that only one of these chains survives long term. Which of these situations will happen in the end remains to be seen. Due to the uncertainty, it is best to prepare for every possible outcome.

2) The preparations taken by CryptoGames
After distributing both BCH and BTG to BTC holders, as well as distributing ETC to ETH holders, we at CryptoGames had previously announced that we would no longer support chainsplit tokens and would not distribute any minority forks to our users, thus users who would want to access coins resulting from chainsplits and forks off the supported coins on CryptoGames would have to withdraw their coins prior to the forking date, take care of securely splitting those coins themselves, and could later redeposit those coins that are still supported by CryptoGames. We did so with BitcoinGod, BitcoinPizza, BitcoinSmart, BitcoinInterest, and a long list of other forks splitting off the Bitcoin network during the last two years. A full explanation of our current policy regarding chainsplits and minority forks can be found in the following blogpost: Our renewed policy about hardforks and chainsplits.
While we do not plan to alter this policy, we are prepared to make an exception in the case of BitcoinCash’s November hardforks. This is correct, CryptoGames will distribute any coins resulting from the November 15th BitcoinCash hardforks and possibly resulting chainsplit to its users. We believe this is the right step to take since both proposed hardforks have a roughly equal amount of support. The problem with many previous chainsplits was that there was only one majority chain and a tiny minority splitting off that chain, making preparing for distribution split tokens and processing their withdrawals costlier than the value gained from doing so. In this case, however, there is no clear majority yet, and we believe users should be able to decide for themselves on which chain they continue to operate, not being forced into taking one side by the services they use to hold their coins.
A few technical aspects: We at CryptoGames are currently running the latest version of BitcoinABC, meaning we will continue to operate on the BCHABC chain after the fork/split. We will only support the BCHABC chain from that point forward, and do not plan to add BCHSV to our portfolio. As a result, we will make BCHSV tokens available for withdrawal to those users holding BCH at CryptoGames during the split.
On November 15th, shortly before the two hardforks activate, we will halt all incoming and outgoing transactions for BCH. Deposits and withdrawals will thus no longer be possible, until the network has stabilized after the split and we deem all resulting chains to be stable, most importantly the BCHABC chain which we will operate on. Once the block for the activation of both hardforks is mined, we will take a snapshot of all user’s BCH balances. This snapshot will include the balance of all those users who hold 0.05 BCH or more in their accounts, meaning either in their active playing balance or as an investment into the BCH bankroll. The distributions of BCHSV will be according to this snapshot, any changes afterwards, wins or losses, as well as tips, will not be reflected in your BCHSV distribution amount.
The distribution of BCHSV tokens itself will only start a little while after the forks happen, depending on how fast the networks stabilize, whether there is any replay protection available, how this replay protection is implemented and depending on how many requests for BCHSV withdrawals we get. Transactions will be processed in the order BCHSV addresses are submitted to us, so if you want your coins as early as possible, make sure to submit your BCHSV address as soon as possible.

3) Things you have to do as a user
There are a few things you have to consider as a user when holding BCH on CryptoGames during the split. First off, ensure you are eligible to receive a distribution of BCHSV via CryptoGames, meaning check if you hold more than 0.05 BCH with us. If you are eligible, you will have to decide whether you want us to take care of splitting the coins for you or not. If you want immediate access to both your split coins after the fork, you should consider handling the coinsplit yourself. If you hold less than 0.05 BCH, but still want access to your BCHABC and your BCHSV, you will also have to handle the split yourself, and should withdraw your BCH from CryptoGames. If you are not in a hurry and can wait some days to get all your resulting coins, or if you do not know how to split the coins yourself, letting CryptoGames take care of the split for you might be the best option.
All users that hold more than 0.05 BCH on CryptoGames and that want to take advantage of the distribution offered by CryptoGames will have to submit an address they want their BCHSV sent to. The feature for address collection has already been enabled and users can submit BCHSV addresses to us starting right now. To do so, head over to CryptoGames, select Your account -> Settings, and you will see a “BCH SV address” tab on the very right end of the window. Enter your desired address into the input section, and click the button to confirm your input. After that, please verify the correct address has been saved by closing and reopening the window.
Users will be able to submit BCHSV addresses for up to 10 days after the fork, until November 25th 23:59 UTC, after this deadline, no more addresses will be accepted and those who did not submit an address in time will lose their claim, so please ensure you complete your submission before the time runs out. Claims from users that did submit an address in time, but could not have their transactions processed within the time window, will of course still be honoured.

4) Further information
If you have any general questions regarding the BitcoinCash hardforks, the split, our handling of the situation, or the necessary actions from your end, you can best ask them directly in our on-site chatroom. Should you get no answer there, you can also post a public response on our bitcointalk thread (right here), maybe someone else has a similar question, or can help you find the answer. If you have specific account related issues, the support team (support@crypto-games.net) is around to help you resolve those and ensure a smooth distribution process.
Should there be any major new development or any important change to this situation and the distribution done by CryptoGames, we will do our best to update you about the events on here with another blogpost, and via newsletter and social media.