Updated on Aug 04, 2025

Dear Community,

Freiexchange has displayed a poor attitude and engaged in unethical communication with the Briskcoin team. They disabled Briskcoin (BKC) without prior notice, cooperation, or proof of compromise. Using a false double-spending narrative, they attempted to claim 900,000 BKC from the BKC team without valid evidence. This claim was rejected, as the amount is too large and no one on the BKC team manages such volumes.

The alleged double-spend isn’t due to hacking but results from hashpower causing temporary blockchain reorganizations. Orphaned or invalid transactions usually vanish after a reindex or full node resynchronization. A deposit confirmation of 80 or more is generally enough to prevent such issues and ensure transaction security.

Due to Freiexchange’s irresponsibility, the Briskcoin team has removed it from the official BKC website. To avoid high-risk losses, don’t send all your BKC to untrusted centralized exchanges (CEXs). Do thorough research. Decentralized exchanges (DEX) offer lower risk, as you can control your private keys directly.

If the Freiexchange team does not cooperate properly or resolve the issue before August 10th, 2025, Freiexchange will be permanently removed from the BKC exchange official listing. Any incidents that occur between Freiexchange and the Briskcoin will not be the responsibility of the BKC team.

If you believe you can hack or compromise the BKC blockchain ledger, remember that by the same logic, Bitcoin (BTC) could also be compromised. Verified proof of such a hack will earn a big reward from the BKC team.

Thanks you,
BKC Core Team

References:
https://discord.com/channels/1305685787744145489/1305740066831859805/1401845004820807751
https://t.me/c/2342624176/6039

Updated on July 24, 2025
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