Re: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency
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
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
I compiled 12.3.3 and everything was ok.
But when I tried to run dash-qt the following error occured three times in the console
(dash-qt:2119): GLib-GIO-CRITICAL **: 19:37:54.249: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
(dash-qt:2119): GLib-GIO-CRITICAL **: 19:37:54.250: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
(dash-qt:2119): GLib-GIO-CRITICAL **: 19:37:54.250: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
(dash-qt:2547): GLib-GIO-CRITICAL **: 19:49:04.879: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
(dash-qt:2547): GLib-GIO-CRITICAL **: 19:49:04.879: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
(dash-qt:2547): GLib-GIO-CRITICAL **: 19:49:04.879: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
..Dash-qt does not connect with any masternode server.
"0 active connections to the dash network"
and also |"HD key generation is disabled"
What wrong @udjim6?
Am I doing something wrong?
Is there a critical bug in your core wallet?
Normally i would refer you to : https://github.com/dashpay/dash/issues for better visibility, but since you went on a spamming spree there a few months ago
you may have burned some bridges there. Same with the dash.org/forum i guess.
I am not spamming. I just cannot post an issue in github. The developers of dash reported me there, and I am banned. Neither I can post the bug in dashtalk or in discord, you also banned me there.
Do you remember the story of my ban in github? Let me remind it to you!
Some remaining of the censorship in github are still visible, through the people who quoted my comments there:
https://github.com/dashpay/dash/pull/2083#issuecomment-393044779
Quote from: demo@github
This is a shame. You are trying to write the IP addresses of the masternodes in the blockchain!
This is an awfull crime against privacy.
THIS COIN USED TO BE DARKCOIN ONCE UPON TIMES!!!
How it ended like this??
Even Vitalik is a pro-privacy now, but the dashcore team goes against the stream!
https://twitter.com/VitalikButerin/status/1000869998385074176
This is an awfull crime against privacy.
THIS COIN USED TO BE DARKCOIN ONCE UPON TIMES!!!
How it ended like this??
Even Vitalik is a pro-privacy now, but the dashcore team goes against the stream!
https://twitter.com/VitalikButerin/status/1000869998385074176
Some other remainings are in dashtalk:
https://www.dash.org/forum/threads/which-masternodes-voted-and-what-exactly-voted-on-various-proposals-v2.34403/#post-189144
Quote from: xkcd@dashtalk
Yes, the github is now 404, can someone from DASH comment on this? What grounds was the repo reported on? I didn't think it was malicious or 'bad' in anyway, it was just aggregating data from the network. Am I missing something here?
For your sake i hope UdjinM6 does not have you on ignore in this bitcointalk forum....
For your sake i hope this is not a critical bug I am reporting!!!!I remember the story all too well :
Looks like you went a bit too far there. In general it is a bad idea to disrupt github like that.