What's even more unfortunate is how CT is doing their "journalism":
1. Create a ticket on Service Desk (which is used for user support to address issues/bugs/general questions) instead of using CMO or Communications contacts listed here https://www.dash.org/team/
2. Publish your article just 2 hours (!) after you created a ticket and claim the team has not answered your request "at press time"
3. ...
4. PROFIT!!!111

It's the setup files that are signed, so that you know you are installing a legit software (the one that is signed by the verified software publisher i.e. DCG in this case).

There you go: GPG verification results I get by clicking on dashcore-0.14.0.3-osx.dmg.asc (assuming you have GPG Tools installed and codablock's key imported into it already) on top of Downloads with the binary itself and this signature file on top of Github releases page with both these files lilsted

Each binary file has a corresponding signature (.asc) file, SHA256SUMS.asc is a signed list of hashes for all files. Corresponding dev keys to check these signatures can be found on github (the easiest way to verify keys - check the modification/commit date to make sure they were not altered recently) and on keybase. Keys on both resources should match (it's highly unlikely that they would be compromised in both places).

Thanks! Can you clarify why "Developer Fee: yes"? There is no such thing in Dash. Also, there are two great block explorers https://chainz.cryptoid.info/dash/ and https://blockchair.com/dash/, would be nice to see them as additional options in "Explores" (I personally prefer the former over the "official" ones tbh).

Try adding dash.rossbennetts.com:55002 to your server list.

EDIT: drk.p2pay.com:50002 should also be up and running now.

There are quite a few exchanges and brokers who support InstantSend actually https://www.dash.org/full-list-of-exchanges/ but I agree, the more the better

В Южной Америке суммарно что-то около 3000 мерчантов принимающих Dash напрямую.
https://discoverdash.com/location/colombia-2/
https://discoverdash.com/location/venezuela-2/

В Африке да, больше на стадии митапов и "коференций", но все регионы с этого начинают, только-только какие-то попытки с мерчантами начались и то с мелкими магазинчиками. Но сказать, что прям проигрываем... ну, не знаю, как-то не видел я особых успехов у кого-то еще 

Трудно отвечать на такие общие вопросы, но я попробую

Если имеется в виду разработка, то и релизы выпускаются достаточно регулярно, на мой взгляд, https://github.com/dashpay/dash/releases, и разработка идет нон-стоп https://github.com/dashpay/dash/commits/develop (это основной репозиторий, но мобильные кошельки и будущие компоненты evo тоже не стоят на месте). Если про все остальное, то краткие Product Update-ы еженедельно публикуются в блоге https://blog.dash.org, а ребята из https://dashnews.org периодически публикуют статьи про разного рода интеграции. Можно еще следить за твиттером http://twitter.com/dashpay, реддитом http://reddit.com/r/dashpay/ и присоединиться к дискорду (даже двум staydashy.com и dashnation.com), там все время какие-то анонсы публикуются.

В целом же, уже давно замечено, что крипто-пресса Dash не жалует и позитив в новости не идет, зато негатив раздувают так как-будто все, туши свет и т.д., отсюда и впечатление, что ничего хорошего не происходит. И вообще впечатление, что все живут в 2014 - "инстамайн", "Dash это скам", "мастерноды это понзи", вот это все. Теперь вот еще "крах Dash Core", при том что пришлось сократить 4 человека из 49...  ¯\_(ツ)_/¯

Рискну предположить, что это связано с переходом на 0.13, который по своей сути является хардфорком, и они таким образом перестраховываются.

Можете пояснить?

https://blog.dash.org/mitigating-51-attacks-with-llmq-based-chainlocks-7266aa648ec9
tl;dr: использование мастернод для противодействия атакам 51%.

Для запуска этой фичи нужно сначала реализовать LLMQ https://blog.dash.org/introducing-long-living-masternode-quorums-76ea8b23a85a. Частично код для LLMQ написан и смёржен (https://github.com/dashpay/dash/pull/2617 и https://github.com/dashpay/dash/pull/2631), но потребуется переписать один кусок, добавить еще https://github.com/dashpay/dash/pull/2634 и все это "причесать". Ну и протестировать, конечно. Пару месяцев уйдет точно.

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

All inputs of InstantSend transactions are locked until corresponding transaction has at least 24 confirmations.

Nice! But you get website, github and reddit links wrong (should be dash.org, github/dashpay/dash and r/dashpay). Not sure about Telegram, maybe someone else can confirm/provide the correct one.

Yep, MNOs vote on proposals (manually) and then MNs vote on triggers (automatically), which are created by Sentinel by scanning proposal list (automatically).

The logic for superblock creation is in sentinel.

See https://github.com/dashpay/dash/wiki

~100000001st time: https://dashpay.atlassian.net/wiki/spaces/OC/pages/19759164/Dash+Instamine+Issue+Clarification

Just a small overview of the network status.

We have ~50% MNs running on the latest version (0.12.2.3), good job everyone who updated! However, 12.5% are still running on 0.12.2.2 and 21.5%(!) are still on 0.12.2.1  

Not to add any drama but 0.12.2.2 fixed pretty critical Corebleed vulnerability which could crash your node by a specifically crafted set of transactions. While we don't see any evidence of a preparation of such an attack on the network, there is really no reason risking and running 0.12.2.1. 0.12.2.3 also fixed few stability issues and an issue with MN behavior which could lead to a situation where your MN could be banned in some (very rare) edge cases, so it worth updating from 0.12.2.2 as well IMO. Note, that NO start from your local wallet is required for this kind of update, all you need is to stop the daemon, replace dashd/dash-cli with a newer version and start the daemon again. Doing so in a timely manner (< 3h), you will NOT lose your place in the payment queue.

Speaking of the payment queue though, there are 185 masternodes that are NOT being paid atm (probably due to some mis-configuration), see the list https://pastebin.com/SM1n12RR. If you can find your node in this list, make sure that both local wallet AND remote node are running on the latest software and start your masternode from your local wallet. Note, that starting your 0.12.2.x masternode using 0.12.1.x wallet will NOT work, you MUST have 0.12.2.x local wallet for "start" command to work properly with 0.12.2.x node. EDIT: also make sure that your node is in sync and hasn't forked off.

And finally, there are also 31 MNs still running on 0.12.1.x.... Not really sure what to say to these people, probably just WAKE UP!!