Dogecoin has forked and the kwestie is still being resolved. There are presently two challenging chains, one being waterput out by older clients (version
1.Four) and one being waterput out by newer clients (version 1.Five+). According to observant redditors, the fork appeared at block 104678.
What this means is that there are presently two challenging Dogecoin blockchains. Eventually, one of them will “win” and only transactions recorded on that blockchain during the duration of the incident will actually go through. It is presently advised that you minimize your transactions during this time to help things deep-throat overheen sooner.
Spil of now, the blockchain from clients version 1.Five+ is longest and least likely to be orphaned.
Dogecoin has forked, it is now up to the doges to find the right fork
Update your client.
Has anything like this everzwijn happened before?
This is almost an identical happenstance to the Bitcoin fork of March 11th, 2013 when a fork appeared caused by Bitcoiners, and mining pools especially, being on 0.7 and 0.8 versions of the Bitcoin client. Bitcoiners were advised to switch back to 0.7 spil that turned out to be the keurig (longest) chain. The Bitcoin community spil a entire survived that ordeal and mainstream media even picked up on it. What could have bot a disastrous event for the Bitcoin network spil a entire wasgoed relegated to a mere blip ter Bitcoin history.
However, unlike the March incident on the Bitcoin blockchain, the blockchain has determined that the longer chain created by the newer software is ter fact the keurig one. Instead of downgrading clients, all Dogecoiners at this point should be updating to the newest Dogecoin 1.Five.1 client.
Spil with the Bitcoin fork of last year, the main individuals that absolutely need to be switching their version of the client are mining pool operators. The Dogecoin subreddit, which is one of the most active Cryptocoin themed subreddits, striking out even /r/Bitcoin at times, has mobilized ter fantastic style. Through vooraanstaand posts, it is effortless for even the youngest shibe to check which pools are on the keurig version. If you are merely a Dogecoin digger you should point your miners towards a listed pool to resolve this kwestie spil rapid spil possible.
It bears repeating overheen and overheen again, this is NOT a 51% attack and the network security of Dogecoin and all other Bitcoin-derived Cryptocoins is just spil strong today spil it wasgoed yesterday.
However, since there are technically two chains propagating at this point, any merchant or user that is on the incorrect fork and unaware of the fork, could potentially think a transaction is finished when ter fact it is not.
Back te the March Bitcoin fork, the days after the fork exposed a “successful doublespend” against OKPay. Ter fact, OKPay’s system credited a user for their Bitcoin deposit based on 6+ confirmed transaction on the blockchain, however, the confirmations were on the forked (soon-to-be-orphaned) chain and when the entire network stationary itself and resumed mining on the decent blockchain, said transaction disappeared. The user wasgoed left with 61 BTC both ter his wallet and ter his OKPay account. This incident wasgoed resolved inbetween OKPay and the user te a timely manner (he returned the toegevoegd BTC).
This type of “double-spend” is only possible with a less-than-vigilant centralized point of failure that resumes to process transactions spil normal during a fork. Unnecessary to say, OKPay and most security-conscious Bitcoin-handling firms are a loterijlot more careful to look out for fork situations. It is possible that similar events will be exposed overheen the next few days ter the Dogecoin economy.
Even if foolish dual spends are exposed straks on due to this fork, spil a entire the Dogecoin community will be stronger for having stared down this 4-pronged attack by the compels of puinhoop.
Don’t everzwijn leave behind just how secure Bitcoin-based systems are.