It could work fine without a single masternode, so long as there are at least some nodes that accept incoming connections. For the SwiftTX feature, minimum of 6 MNs are required.

I'd say the network needs a minimum of 2 honest nodes in different locations that accept incoming connections from everyone in order to be stable. BTC2 has hundreds of them.

ANN

The upgraded web wallet is now online!

You can already login with your old keys and migrate your balance to newly created web wallet addresses.

You can cancel the migration process within 48 hours after starting it. We recommend you to check the web wallet's migration timer and address once a day until the migration is complete.

Sending BTC2 with the new web wallet addresses will be possible starting tomorrow, but you can already set up and
test the optional two-factor authentication and send BTC2 to your new web wallet addresses to stake.

Why we chose to do it as a snapshot fork instead of just copying the blockchain:
- We used a proof of stake codebase without segwit support.
- In order to prune the blockchain from a massive 147 GB to less than 1.5 GB. That original size would have severely limited masternode creation and increased staking node hardware requirements. We wouldn't have anywhere close to the 170 or so full nodes running that we have now and 0 managed masternode hosts.

To get the full bitcoin fork marketing benefits, BTC2 would have needed to launch its main net in 2017 like the early simple forks did. It just wasn't ready at that time.

You're right, it is because of executable hardening and Bitcoin's executables appear the same way on some Linux desktop environments. It works though if you execute it from the command line with ./bitcoin2-qt

Turns out that a few configuration flags were not set for that version so I compiled a more widely compatible Linux 64-bit version and updated https://github.com/BITC2/bitcoin2/releases/download/2.2/bitcoin2-2.2.0-x86_64-linux-gnu.tar.gz.

So you can now download it and try again. Meanwhile, we'll test this more than just the quick test I did so far.

If you're interested in running Bitcoin 2 Core on your Raspberry Pi, a member of our community created an in-depth step by step guide:
https://www.bitc2.org/How_to_set_up_your_Bitcoin_2_Staking_Raspberry_Pi.pdf

Our website is down temporarily. Should be back online soon.

Whales are likely to have multiple addresses anyway and getting a whale on board would be far more important than getting a regular guy on board. So unlikely to differentiate between whales and others when deciding who can claim.

Earlier on this thread we talked about doing such a fork and it seemed people here welcomed it and yes, it would be easier now. We even thought of a way to do it without forced forking which would just make it harder but not impossible to claim BTC2.

It hasn't really been a priority lately because there hasn't been many claims that simply sold straight away after claiming lately. The claiming block height is over a year ago and only true hodlers are likely to remember their private keys of that time since they still have the same addresses. But a coinmarketcap listing could still let more of those people know that they have something to claim.

No actual stats have been compiled of how much has been claimed as it would take a lot of blockchain analysis by a program or human to do it but it is a minor %.

There are cons to stopping claims, such as perception about it of those that don't yet own BTC2 and keeping the supply unaffected would make our coin market cap look high and make it easier to be in the top 100 at coinmarketcap. The solution we are most likely to do would not affect this supply number. Then again Bitcoin private did a coinburn more than a month ago and yet coinmarketcap did not update their circulating supply, yet anyway.

Now compiling the version 2.1.5 for all platforms. Probably releasing it within 24 hours. zBTC2/privacy functionality will be re-enabled within a couple of days after the release of the new version.

While not a bad idea, they tend to be reported anyway.
Perhaps for finding bugs in the source code.

Speaking of which, someone reported that his windows staking wallet shuts down occasionally by itself like once a week. anyone else here with that problem?

You can get up to date answer to that at https://www.bitc2.org/#roi

Yeah, not only was Bisq a bit overly complicated to use. But also they went as far as to delist Bitcoin Cash due to their own personal bias.

The web wallet has been improved.
- It now displays the actual blockchain balance
Instead of the internally counted balance.

- Ensured that when sending something out from an account, only the mature coins of the account can be used. So if you see a clock icon next to an incoming staking reward, you will need to wait until that staking reward matures and the clock icon turns into a check mark before those coins are spendable again. But most of the time your coins will be spendable.

- We will soon be re-activating the web wallet staking fee script, and it will retroactively catch up on sending out the unpaid fees. (0.2 BTC2 per staking reward of 0.6+ BTC2).

- If a significant % of users request it, we may also make staking optional on the web wallet.

POW was needed to recreate the Bitcoin balances. There was no reason to take the time to completely remove that unused code afterwards as POW cannot be used after the main net launch without forking away from the main chain and changing the code.

Your BTC2 for the masternode is supposed to be kept in a local wallet as per the setup guide, that means that you either set it up in an insecure manner or if your btc2 was actually in your local wallet, then the local wallet was compromised rather than the AWS one.

There's various reasons why a peer could be automatically banned from being connected to you temporarily.

Perhaps your node thinks that they are doing something outside of the consensus rules, or attempt and then fail to do something too many times or are on a different chain.

Usually the ban on a peer lasts for a day. If you want to figure out the exact reason why, you could check your data folder's debug.log.

It is rare to see banned peers however so check that the current block number, or block height of that wallet is the same as in your other wallet or the block explorer.

The block, if it ever happened, would more likely be on the old transactions instead of addresses actually in order to make a ban database that is small and efficient.
It could be done with a protocol change that would require everyone to update their Bitcoin 2 Core client instead of just recommend to do so like usual.

Keeping Bitcoin 2 fork airdrop intact may still be worth it, all things considered, because not everyone who claims will dump, even though free coins are indeed more likely to be dumped than researched and saved.
There's always a chance that one of those who take their time to claim become a supporter of the project as has also happened in the past.

The total amount of BTC2 claimed from the fork and then deposited to crex24 for dumping/selling during the past few days is way higher than normal. (Around 1800 BTC2) but still nothing too major yet. It just had a major effect due to there being so few people trading BTC2 on a daily basis. Will be interesting to see if this goes on for a while or if there's nothing left to claim by him/them.

It would be hard to judge which Bitcoin addresses belong to the exchanges. So most likely if we do this one day, all unclaimed ones would be locked. Meaning the fork airdrop of Bitcoin 2 would end.

Yes after the new features we better create an updated white paper and preferably a wiki. Such translations will be much appreciated.

Regardless, we will investigate this and if needed, improve the masternode rewards queue system.

By the way, I expect Bitcoin 2 to be listed on Bisq soon, along with the release of the next version of Bisq. There was a big delay between new altcoin adds to it due to listing fee policy discussion but they said they will resume adding them now. Bisq is a decentralized exchange that uses Tor for anonymity.