Quote from: qwizzie on September 22, 2018, 09:54:01 AM

https://www.coindesk.com/the-latest-bitcoin-bug-was-so-bad-developers-kept-its-full-details-a-secret/

Quote

While this sounded bad enough for many, it turns out developers for Bitcoin Core kept a second, bigger part of the bug a secret. As disclosed through an official Common Vulnerabilities and Exposures (CVE) report,
an attacker could have actually used it to create new bitcoin above the 21 million hard-cap of coin creation thereby inflating the supply and devaluing current bitcoins.

This makes the latest mandatory Dash update that contains a hotfix for the Bitcoin vulnerability (mentioned in above link) even more important. It also makes me wonder if Dash and any other direct forks from Bitcoin,
were informed by Bitcoin's Core-Team in time about this bug, including receiving full details about the "secret" part.
Since mining pools can be notoriously slow on updating, i hope this additional information does not put Dash network in any danger.

Emphasis should now be on having Dash mining pools update as soon as possible

Current update progress with regards to versions seen on the network in the last 24 hours : https://chainz.cryptoid.info/dash/#!network
(i assume these include the Dash mining pools)

50,7% updated to v0.12.3.3
23,0 % still on older version 0.12.3.2

Quote from: UdjinM6 on September 19, 2018, 10:29:35 AM

Dash Core 0.12.3.3 Release Announcement

Dash Core 0.12.3.3 is a critical bugfix release of the Dash Core 0.12.3.x series.

There was a serious vulnerability discovered in Bitcoin Core's codebase recently which
can cause node receiving a specially crafted block to crash https://github.com/bitcoin/bitcoin/pull/14247

We encourage all full node operators (masternodes, mining pools, explorers, exchanges etc.) to update ASAP.

Full release notes are available at https://github.com/dashpay/dash/blob/v0.12.3.3/doc/release-notes.md,
release binaries can be downloaded from https://github.com/dashpay/dash/releases/tag/v0.12.3.3.

Note: this release does NOT require masternode owners to start their masternodes from cold wallets.
Masternode operators should stop the daemon running on a remote node, replace old binaries with the new ones and start the daemon again.

Same ann on github:
https://github.com/dashpay/dash/releases/tag/v0.12.3.3

https://dash.suprnova.cc is fully updated