Ravencoin hits record low as network exploit puts transactions at risk
Reported by Cointelegraph · AI-assisted summary by ChikoCorp AI News Desk
AI-generated summary based on the linked source; not independently verified. This is not investment advice. Verify market-moving details at the original publisher before acting. See our editorial policy, AI content policy, and financial disclaimer.
Summary
Ravencoin experienced a new all-time low following the discovery of a consensus vulnerability that exposed several days of transactions to risk. This exploit caused some nodes to accept invalid blocks starting at block height 4,487,776. Mining pools 2Miners and RavenMiner, which control a majority of the network’s hash rate, are working on a competing chain that excludes the exploited blocks, possibly leading to a network reorganization. As a result, some exchanges like Upbit and Bitget suspended RVN transfers.
Why it matters
The exploit undermines transaction finality on the Ravencoin network, as transactions confirmed after block 4,487,775 could be reversed and may not be automatically reprocessed. This situation disrupts exchange operations and threatens network stability, prompting precautionary measures such as halting deposits and withdrawals.
Key context
The vulnerability was first detected on Friday at block 4,487,776, and since then, invalid blocks have continued appearing on the mainnet. The mining pools controlling the majority of hash power are creating a competing chain to exclude these invalid blocks. If their chain becomes dominant, the network may undergo a reorganization spanning about three days, which may affect confirmed transactions during that period.
Key numbers and entities
Ravencoin (RVN) dropped to $0.002754, approximately 22% below its 24-hour high of $0.003529. Trading volume peaked above $18 million before falling to around $9.6 million. The relevant block height where the issue began is 4,487,776. Mining pools involved are 2Miners and RavenMiner. Exchanges mentioned include Upbit and Bitget.
What remains unclear
The source does not flag open questions but notes that transactions reversed due to the reorganization may not return to the mempool or be mined again automatically, implying some uncertainty about the final state of affected transactions.