Ravencoin is attempting to roll back several days of transaction history after attackers exploited a critical consensus vulnerability and started adding invalid blocks to the network. Transfers and payments made since August 7 are now at risk, and several major exchanges have already halted RVN operations.
What happened: Ravencoin's consensus failure
Ravencoin, a blockchain forked in 2018 from Bitcoin's code, was built from the start not for payments but for issuing and transferring digital assets: shares, in-game items, any tokenized ownership rights directly on its own chain. Like Bitcoin, blocks here are added by miners who compete for computing power and jointly agree on a single version of the network's history.
The RVN network is hundreds of times smaller than Bitcoin by hashrate, which means a handful of large pools can single-handedly decide which chain branch survives if the network splits. That concentration became the problem: at 15:44 UTC on August 7, the first invalid block appeared at height 4,487,776 because of a flaw in the software. Other participants soon followed, repeating the same attack and adding their own invalid blocks.
Developers haven't disclosed the technical nature of the vulnerability in detail, so far describing it only as a "critical consensus-level flaw." That's especially sensitive for Ravencoin, since hundreds of third-party tokenized assets have been issued on its chain. They run under the same consensus rules and depend equally on which version of the chain ultimately wins.
How this hit the RVN price
RVN's price dropped to a record low. According to Decrypt, the token lost around 20% of its value within a day of the exploit news, and it's down 77% over the past year. The rest of the altcoin market barely reacted, though: the panic stayed a local story for a single network.
Two mining pools, 2Miners and RavenMiner, together control most of Ravencoin's computing power. They are already rebuilding the chain from block 4,487,775, the last valid block before the attack. If enough other participants join them, everything recorded on the network after that point will be replaced.
RVN liquidity was already fairly thin, so even moderate sell volume, by large-cap standards, can swing the price sharply in either direction. That amplifies the effect of any panic-driven news, including this one.
Risks for holders and traders
For an average user, the consequence is simple. A payment that looked complete over the weekend can disappear from the network's record, with coins returning to whoever sent them. The recipient is left with nothing, because a rollback rewrites the network's history itself.
The biggest exposure sits with anyone who already acted on such a payment: credited a deposit and let a customer withdraw against it. Several centralized exchanges have already responded to the threat:
- Amsterdam-based Bitvavo suspended RVN deposits and withdrawals as a precaution, citing the vulnerability
- South Korea's Upbit posted a risk warning on its won, bitcoin and tether pairs and also paused deposits
- Some smaller platforms limited trading of the RVN pair until the network stabilizes
Under normal conditions, exchanges rely on confirmation counts: the more blocks stacked on top of a transaction, the less likely it is to vanish. But when a reorganization stretches across several days, a buffer sized for random glitches rather than a coordinated attack turns out to be too thin.
Why the pools refused a partial rollback
The Ravencoin team released a patch that closes the vulnerability, but fixing the software doesn't undo blocks that are already written. Developers asked 2Miners and RavenMiner to start rebuilding from a later point so less history would be at risk.
The pools said no. RavenMiner announced on its website that it's already running what it called a clean chain, with payouts to participants paused until the network settles. The pool promised to cover any shortfall out of its own funds and confirmed that earnings from before 15:44 UTC on August 7 are unaffected.
The episode shows the limits of a project team's power in a proof-of-work network. Developers can ship a patch, but they can't force mining pools to follow a specific rollback plan: the final call belongs to whoever physically controls the computing power.
What's next for the network
Ravencoin has been through something like this before. In 2020, attackers exploited a different consensus flaw and minted roughly 31 million extra RVN beyond the set issuance limit. The token fell 17% in a day to $0.0029 back then, and the network's market cap dropped to around $48 million on just $10 million in trading volume.
This time the scale is different: what's at risk isn't the token supply itself but the integrity of several days of real user transactions. Small networks with concentrated hashrate keep running into this exact problem, because a couple of pools are physically capable of rewriting shared history.
Similar episodes have already hit other small networks. Bitcoin Gold and Ethereum Classic both suffered chain-rewriting attacks in past years, after which major exchanges raised confirmation thresholds for those coins for a long stretch. Until 2Miners and RavenMiner finish rebuilding Ravencoin's chain, exchanges are unlikely to fully restore RVN trading.
Comments
Your email address will not be published. Required fields are marked *