In order to have gotten the coins from the fork, you would have needed to have claimed it with the Bitcoin 2 Core wallet when claiming was still supported.

To be clear, BTC2 started as a 1:1 snapshot fork, which means that all BTC holders got 1 BTC2 for each BTC they held but the transaction IDs are different.

Claiming from the fork has been made harder 15 months after main net launch as per https://www.bitc2.org/#faq.
I just updated the thread's first page image accordingly. It was outdated.

So if a billionaire pump and dumped Bitcoin, would Bitcoin then be a scam? Give us a break.
BTC2 just was an easier target at that time for an opportunist to do that. Not so easy target anymore.

On this thread there's only one person calling it a scam and for no actual reason.
If someone suddenly bumps some altcoin up 5500% in a day and then dumps it, does that make that altcoin a scam? No.

https://bitc2.org/#faq answers that, but also debug console: getstakingstatus will tell you if you're staking or what's missing.

I don't really know your setup, but if you have an exact 1000 BTC2 unspent transaction output remaining (most likely not as it probably has staked and become bigger, but check with Coin Control option), you can use the transaction details from that still. Otherwise yes you can start the process over and send the coins to yourself again.

Nothing has changed in the process, but both your masternode and your wallet need to run v.2.2.1 wallets.
And your masternode.conf file should be set up as per https://bitc2.org/bitcoin-2-masternode-guide in order to lock the coins.

Bitcoin 2 Version 2.2.1 wallets are now available for all our supported platforms. Updating your Bitcoin 2 Core wallet is highly recommended if you had any problems before. Also recommended to upgrade any masternodes, especially those that you were not able to start successfully. Details at https://github.com/BITC2/bitcoin2/releases.

Details about the recently fixed Proof of Stake vulnerabilities

More than a month ago while we were working on the wallets we noticed severe vulnerabilities that existed with most Proof of Stake coins. Properly identifying the vulnerabilities and how they could be exploited, fixing them and testing it all took a while but they have been fixed since Bitcoin 2 Core v.2.2.

Around August 20 2019 a news article started circulating about a Proof of Stake vulnerability, but the author of the article had no real clue about the nature of the attack and just thought that it was the "fake stake" attack, which is different and could have been used to crash or slow down nodes one by one that the attacker could connect to.

In reality the actual vulnerability allowed someone to gain way more staking power than he should with the amount of coins that he owned. This affected Bitcoin 2 as well. He or they were able to gain a much higher share of the daily block rewards than they should have, and sold them every now and then. No extra coins were minted. So the supply rules were not vulnerable.

These vulnerabilities were fixed in Bitcoin 2 Core v.2.2 and we were among the first of PoS v.3 algorithm using coins to notice the attacks and successfully implement a proper, lasting fix. Our Proof of Stake algorithm can no longer be called PoS 3.  We added time-tested solutions that have not been able to be exploited and extra checks and rules of our own to ensure that no one can gain more staking power than someone else who has an equal amount of coins.

Using Windows?
Try setting it to English in Tools - Options - Display - Your interface language drop down.

Best if you wait a bit. We are rolling out fixed wallets (v.2.2.1). The source code is already available at our Github and we are now compiling and testing the new wallets.

You can try to restart the wallets. We upgraded to the new more secure staking protocol yesterday. But the network got issues afterwards that we're working on. Some of the issues have been fixed already. Your BTC2 are safe, but best to refrain from doing any transactions with others during this transition because you or the person you are transacting with might not be synced correctly which could lead to confusions. (Except you can transact at Crex24).

If it's not a managed masternode, login to it and update the executables on the server like you would for a local node.  if it is a managed one, then they probably already did it for you.

Windows 32-bit version of v.2.2 is now available at https://github.com/BITC2/bitcoin2/releases/download/2.2/bitcoin2-2.2.0-win32.zip
Just download it, then shut down your wallet and copy the executable files in the bin folder to replace the ones you had installed already.

Did you download this one: https://github.com/BITC2/bitcoin2/releases/download/2.2/bitcoin2-2.2.0-x86_64-linux-gnu.tar.gz ?
If so, will look into the problem.
Which Ubuntu version is that? 64-bit? Trusty, Bionic, etc.?

If you have Windows 64-bit, you can update to the Windows 64-bit version. If not, hold on, we will compile and release the 32-bit Windows version soon.

Bitcoin 2 Core v.2.2 wallets have been released and are available at https://www.bitc2.org/#wallets.
Details at https://github.com/BITC2/bitcoin2/.

Updating your Bitcoin 2 Core wallet to this version is mandatory. That includes upgrading all your Masternodes. After enough nodes have upgraded to this version, a new staking protocol will be activated and the old nodes that fail to upgrade their wallet before that will end up forking to the wrong chain. Estimated time of this protocol upgrade is between August 21 - August 24 2019. As soon as possible.

We are close to releasing the v.2.2 Bitcoin 2 Core wallets. They are going through final testing. Most likely to be released on 20th of August 2019. This will be a mandatory upgrade.

Like we've stressed before, the wallet upgrade is very important. If you want to look at it from marketing/price perspective, consider that once BTC2 is in the spot light next, would you rather have it seen as high quality safe coin with all the fundamentals looking good, or as just another temporary pump? Those with not that many coins just waiting for a pump might not care about the long-term use cases and value of BTC2, but we do.

We have the funds for exchange listings, but any new listings will also require volume so even if we got listed today, does not mean that we would be immediately eligible for a top 200 ranking. Not that a ranking is even the only way to gain spotlight again.

Check out how much Ethereum's POS update has been delayed as an example. Delays in crypto development are common. ETA is not a deadline, it was our best guess at the time that we made it. We would refrain from making such guesses if it wasn't for the community asking for them.

Yes to be shown in the top 200 on CMC according to their current rules we need at least 3 qualified, non-decentralized exchange listings.