Dear Freiexchange and Community,
Please be informed that Friexchange has immediately disabled BKC trading, deposits, and withdrawals without prior notice.
We would like to clarify that the issue described—often referred to as a “double spend”—is not the result of hacking or a malicious attack but rather is related to the use of hashpower causing temporary blockchain reorganisations. These orphaned or invalid transactions typically disappear during a reindex or full node resynchronisation.
BKC is forked from the latest version of BTC and merged with a recent release of Bitcoin Core, which includes advanced consensus and security improvements. As a result, confirmed transactions cannot be reversed, making deep reorganisations or rollbacks of high-confirmation transactions technically impossible under normal network conditions.
It is important to note that other global nodes, centralised exchanges (CEXs), and decentralised exchanges (DEXs) operating with BKC have not reported similar issues. This suggests a localised technical challenge rather than a fundamental blockchain failure. The BKC network appears to be functioning normally, and the reported issue may be specific to your exchange’s configuration or node synchronisation process.
As an additional security measure, we kindly suggest that for large BKC withdrawals, your system validate that the withdrawal amount matches the current balance of your BKC hot wallet before processing. This can help prevent mismatches, reduce risk, and ensure transaction integrity for all parties. Additionally, we recommend setting the minimum deposit confirmation threshold to 60 or more confirmations for enhanced security.
We value our partnership and remain open to continued collaboration to improve network stability and user experience. Please let us know how we can assist further in verifying and resolving this incident.
The BKC Core Team confirms that the BKC chain maintains robust security, comparable to Bitcoin. Kindly re-enable trading, deposits, and withdrawals, as the BKC community currently faces frozen assets on the exchange.
Best regards,
BKC Core Team