At press time, the Dash team has not answered Cointelegraph’s request for comment. That is unfortunate. ... 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 |
|
|
|
---snip--- I have one remaining question though, our last Dash update included this in the release notes : Signed binaries for Windows
This release is the first one to include signed binaries for Windows. I assume this is different from above described hash / GPG verification and is more like a digital signature in Windows 10 ? I tried rightclicking on the dash-qt.exe and checking properties, but i'm not seeing any digital signatures tab there. Where do we find that digital signature ? Or how does this work in Windows 10 ? 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).  |
|
|
|
---snip--- To UdjinM6 : Each binary file has a corresponding signature (.asc) file, SHA256SUMS.asc is a signed list of hashes for all files. it looks like most Hash Files are SHA256SUMS.asc files, i'm not seeing any individual .asc files for individual binaries. I guess it saves time this way.  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  |
|
|
|
I like to use 7zip and right click the file to verify the hash checksum when using windows. Looks like a bunch of coins are getting infected wallets switched in lately. That hash file should be posted in multiple places, as this happened on Linux Mint at some point and the hashes were also compromised on the website.
I agree that hash files should be stored on a separate server, and not on the normal download server (to avoid getting compromised too in case of a hack). Also I like to point out that Dash also offer both it's binaries and the SHA256SUMS.asc (hash file) on Github . Link : https://github.com/dashpay/dash/releases (see assets) I understand there are also ways to verify hash files themselves, by checking who pgp signed them and compare that with developers that have signature rights. Maybe someone from Dash Core Group can comment on the above ? I guess we have to wait and see how Monero's official site got compromised in the first place and then check if our own security measurements are still sufficient. Good to hear that 7zip also has a hash verification tool inside. 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). |
|
|
|
GrepBlock.com + Dash (Dash) 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). |
|
|
|
all Electrum wallets are not working today
Try adding dash.rossbennetts.com:55002 to your server list. EDIT: drk.p2pay.com:50002 should also be up and running now. |
|
|
|
Finally an exchange with Instasend support. Tho it is aimed to markets - let's see will other exchanges pick up and will it boost adoption!
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/В Африке да, больше на стадии митапов и "коференций", но все регионы с этого начинают, только-только какие-то попытки с мерчантами начались и то с мелкими магазинчиками. Но сказать, что прям проигрываем... ну, не знаю, как-то не видел я особых успехов у кого-то еще  |
|
|
|
Рискну предположить, что это связано с переходом на 0.13, который по своей сути является хардфорком, и они таким образом перестраховываются.
А насчёт Дашки, вопрос то по сути не в Поло. Это я уже узнал, когда пошёл сливать Дашку. Практического продвижения монеты - я не вижу. Трудно отвечать на такие общие вопросы, но я попробую Если имеется в виду разработка, то и релизы выпускаются достаточно регулярно, на мой взгляд, 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... ¯\_(ツ)_/¯ |
|
|
|
Тогда точнее будет сказать: "Поло сильно тормозит", так как в самой сети Dash подтверждения идут как обычно, 1 раз в 157 секунд. "Торможение Форклога" - это вообще отдельная история, всегда советую сверять с первоисточником то, что они придумывают "от себя".  ... Они увеличили количество подтверждений для Дашки, до 50. Вопрос почему. ... Рискну предположить, что это связано с переходом на 0.13, который по своей сути является хардфорком, и они таким образом перестраховываются. |
|
|
|
...
Сеть Дашки тормозит сильно.
Можете пояснить? |
|
|
|
Technical question: does InstantX have transaction finality? If so, by when and how does it work if the blockchain reorganizes?
Thanks to anyone who can answer.
All inputs of InstantSend transactions are locked until corresponding transaction has at least 24 confirmations. |
|
|
|
Hello Dash believers, Our aim is to add value to the whole crypto community by giving the best user experience to analyse cryptocurrencies. It would be really great help from your side if you can spend 60 seconds of your time and give us your valuable feedback for our two recent updates 1) Snapshot and 2) Colourful interface of Etherium at: https://cointopper.com/coin/dashConstructive criticisms are always welcome at CoinTopper. Thank you!! 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. |
|
|
|
do masternodes have to submit a superblock trigger once every funding round, who submits it for dash every time?
Network generates the payment automatically and sends it to approved budget proposals. Unused funds are not created. im not seeing it in the code it expects a trigger which is only created by a gobject trigger call done by a masternode. in the superblock code it waits for a trigger if none exist it wont pay any proposals. The logic for superblock creation is in sentinel. thanks! I see that so that means a masternode must create a trigger(superblock) vote proposal for others to vote on that includes payments for the next budget payment cycle? so masternodes would vote twice once on proposal and once on the trigger for the superblock? thats what im seeing in the code just wanted to confirm. Yep, MNOs vote on proposals (manually) and then MNs vote on triggers (automatically), which are created by Sentinel by scanning proposal list (automatically). |
|
|
|
do masternodes have to submit a superblock trigger once every funding round, who submits it for dash every time?
Network generates the payment automatically and sends it to approved budget proposals. Unused funds are not created. im not seeing it in the code it expects a trigger which is only created by a gobject trigger call done by a masternode. in the superblock code it waits for a trigger if none exist it wont pay any proposals. The logic for superblock creation is in sentinel. |
|
|
|
How much of dash was premined? and is there any sharing masternode pool to be a part of it
Dash was never premined [...] It was instamined, which means instead of being mined by the devs before the project is released it was mined right after by the devs before other's joined in. The difference is only a technicality. Not that it makes DASH scam, but you can't hide the fact it happened. ~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!!  |
|
|
|
|
Show Posts
