Dear Beldians,
First and foremost, thank you for your patience, understanding, and continued trust in Beldex. We understand that the ongoing network interruption has caused uncertainty, and we sincerely appreciate your patience and support during this time.
Our team acted immediately upon identifying the issue, coordinating with ecosystem partners across the globe to safeguard the network and restore normal operations. We'd like to share a complete update on the incident, the measures taken, and the path forward.
At approximately 08:45 UTC on 26 June 2026, the Beldex network detected an anomaly that resulted in an incorrect masternode reward being generated. Instead of the expected 6.25 BDX block reward, a validator was incorrectly rewarded with approximately 900018906.34 (approx. 900 million) BDX.
Upon detecting the issue, the Beldex core team immediately initiated its incident response procedures. To preserve the integrity of the blockchain and restore the network to its last valid state, an emergency hardfork was initiated.
What happened?
The anomaly occurred at block height 5518800. By the time it was identified, the network had progressed further to block height 5520127, making it necessary to roll back approximately 1,327 blocks to the last valid block.
As a result, the blockchain will recognize block height 5518799 as the last valid state. The incorrectly generated 900 million BDX will not exist on the canonical chain, fully restoring the intended circulating supply and token economics.
What does this mean for users?
Any native BDX transactions that occurred after block height 5518800 will be reverted as part of the rollback.
This means that:
- Native BDX sent between wallets during the affected period will be returned to the originating wallet.
- Native BDX deposits made to exchanges during the affected period will also be reverted, with the funds automatically restored to the sender's wallet on the canonical chain.
- No action is required from most users.
We are actively coordinating with exchanges and infrastructure partners to reconcile any exceptional cases that may arise.
Was the network compromised?
No.
The issue was isolated to the incorrect masternode reward transaction. The transaction validation process and the network's consensus mechanism were not compromised, and no double-spend was detected or is expected.
Security improvements
A patched version of the beldexd daemon has been released to address the underlying issue. With this update, reward transactions of this nature will no longer be accepted by the network.
Obscura v7.0.2 (latest Beldex daemon):
https://github.com/Beldex-Coin/beldex/releases/tag/v7.0.2
We have requested all masternode operators, exchanges, wallets, and infrastructure partners to upgrade to the latest version before rejoining the network.
Our commitment
The security and stability of the Beldex network remain our highest priorities.
We are committed to ensuring that no legitimate user is disadvantaged by this incident. While native BDX balances affected by the rollback will automatically return to their originating wallets (custodial and non-custodial), we will continue working closely with our exchange and ecosystem partners to review and resolve any exceptional cases.
We appreciate the support and cooperation of our community, masternode operators, exchanges, and infrastructure partners throughout this process. Further updates will be shared as the network returns to normal operation.
Listen
back to blog