ANN: Friexchange has Disabled BKC’s Trading, Deposits, and Withdrawal

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

ANN: Response to VinDAX’s Temporary Suspension of BKC Withdrawals – Resolved

Official Statement from VinDAX on the BKC Incident
https://vindax.com/announcement/notice-on-temporary-suspension-of-bkc-withdrawals

Dear Vindax Team and Community,

Thank you for your explanation regarding the recent BKC blockchain incident. We would like to clarify that the issue you described—often referred to as a “double spend”—is not a result of hacking or malicious attack but is related to the use of hashpower causing temporary blockchain reorganizations. These orphaned or invalid transactions will disappear during a reindex or full resynchronization of the node. BKC is forked from the latest version of BTC and merged with a very recent release of Bitcoin Core, which includes advanced consensus and security improvements. As a result, confirmed transactions cannot be reversed, making deep reorgs or rollbacks of high-confirmation transactions technically impossible under normal network conditions.

We understand the impact this has had on your platform and users. To demonstrate our commitment to resolving this matter and supporting Vindax, the BKC team is prepared to assist with covering 75% of the total losses, contingent upon receiving verifiable proof of the compromise and the affected transactions. Otherwise, we can offer support covering 30% as a donation for mutual and long-term cooperation.

It is important to note that other global nodes, centralized exchanges (CEX) and decentralized exchanges (DEX) platforms operating with BKC have not reported similar issues, indicating this is a localized technical challenge rather than a fundamental blockchain failure. This indicates that the BKC network is functioning normally, and the reported issue may be specific to your exchange’s configuration or node synchronization process.

As an additional security measure, we kindly suggest that in the case of a large BKC withdrawal, your system should 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, the minimum deposit confirmation should be set to more than or equal to 60 confirmations for higher 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 the incident.

The BKC Core Team confirms that the BKC chain maintains robust security, comparable to Bitcoin. Kindly re-enable withdrawals, as the BKC community currently faces frozen assets on the exchange. 

Best regards,
BKC Core Team

This case has already been resolved. It was due to an exchange technical issue, not from the main chain of Briskcoin

VinDAX Exchange has re-enabled trading, deposits, and withdrawals for BKC after thorough validation, confirming that the BKC chain offers a high level of security comparable to BTC. Additionally, a new market pair—BKC/BTC—has been added.