[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 348.

qwizzie

legendary

Activity: 2548

Merit: 1245

Quote from: snakey on September 21, 2018, 04:08:40 AM

8% up today, what is next?
Is the surge because of dash text launched by dash team in Venezuela or it is general altcoin rally?

I think it is more of a general altcoins uptrend combined with a somewhat slower bitcoin uptrend.

https://www.newsbtc.com/2018/09/21/crypto-market-surges-20-billion-with-positive-developments-factors-and-trends/

snakey

legendary

Activity: 1386

Merit: 1001

8% up today, what is next?
Is the surge because of dash text launched by dash team in Venezuela or it is general altcoin rally?

qwizzie

legendary

Activity: 2548

Merit: 1245

SEC Begins Reviewing Physically-Backed Bitcoin ETF, Will Examine 1,400 Comments
https://www.ccn.com/sec-begins-reviewing-physically-backed-bitcoin-etf-will-examine-1400-comments/

Quote

According to the order dated Sept. 20 and published on the SEC’s website, the regulatory agency will now consider whether,
pursuant to federal securities guidelines, it should approve the fund — the VanEck Solidx Bitcoin Trust — for listing on CBOE BZX Exchange.

Quote

The order comes as somewhat of a surprise. CBOE first filed to list shares of the VanEck Solidx Bitcoin Trust in June, and in August the SEC postponed
ruling on the application, setting a new deadline of Sept. 30. Many analysts, including Canadian investment firm Canaccord, speculated that the SEC would likely
delay ruling on the fund once more, until March 2019.

afbitcoins

legendary

Activity: 2101

Merit: 1061

Quote from: qwizzie on September 20, 2018, 12:31:06 PM

For your sake i hope UdjinM6 does not have you on ignore in this bitcointalk forum....

I have him on ignore but I'm terrible at ignoring. I inevitably peek via the show/hide button. Or browse all comments on a device when not logged in Grin

I hope for your sake (demo) UdjinM6 sometimes peeks at what trolls post.

Anyway, Demo you are starting to sound like icebreaker again, Is he in there with you? Or are you just upping your game? DId icey get sacked?

afbitcoins

legendary

Activity: 2101

Merit: 1061

I think there is a reason you keep getting banned demo

demo16

newbie

Activity: 94

Merit: 0

Quote from: UdjinM6 on September 19, 2018, 05: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

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"

Whats wrong @udjim6?
Am I doing something wrong?
Is there a critical bug in your core wallet?

Spit the cancer of censorship and of spamming out of the dash forums.
Let's LIBERATE the users/readers of the dash forums, NOW!

qwizzie

legendary

Activity: 2548

Merit: 1245

Something for you demo ? Course is only 4 weeks and its an eCourse !!
It may even help with your paranoia issue, which seems to be getting worse.

demo16

newbie

Activity: 94

Merit: 0

Quote from: qwizzie on September 20, 2018, 02:21:47 PM

Quote from: demo16 on September 20, 2018, 02:10:57 PM

Quote from: qwizzie on September 20, 2018, 02:01:00 PM

I remember the story all too well :

https://i.imgur.com/W4JzgKi.jpg
https://i.imgur.com/Lg8BlKK.jpg

Looks like you went a bit too far there. In general it is a bad idea to disrupt github like that.

OH NO!
YOU DONT REMEMBER THE STORY, SINCE ALL MY COMMENTS HAVE BEEN DELETED!!!
ALONG WITH MY ENTIRE GITHUB REPOSITORY!!!

Yes, because you were disrupting the Github forum with your off topic comments. The consequences were communicated very clear to you. I'm not surprised of the outcome.
You should really draw a line between disrupting a forum like Bitcointalk with your censorship theme and trying to disrupt a forum like Github, where devs are hard at work and dont want to be distracted by off topic comments.

AND HOW THE HELL DO YOU KNOW THAT MY COMMENTS WERE DISRUPTIVE, SINCE THEY WERE ALL ENTIRELY DELETED? Huh

And why they deleted both my comments AND MY GITHUB REPOSITORY? Huh

WAS MY REPOSITORY ALSO DISRUPTIVE???

I bet it was, because there was a record there, containing all the votes of the masternode operators....

Spit the cancer of censorship and of spamming out of the dash forums.
Let's LIBERATE the users/readers of the dash forums, NOW!

qwizzie

legendary

Activity: 2548

Merit: 1245

Quote from: demo16 on September 20, 2018, 02:10:57 PM

Quote from: qwizzie on September 20, 2018, 02:01:00 PM

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.

OH NO!
YOU DONT REMEMBER THE STORY, SINCE ALL MY COMMENTS HAVE BEEN DELETED!!!
ALONG WITH MY ENTIRE GITHUB REPOSITORY!!!

Yes, because you were disrupting the Github forum with your off topic comments. The consequences were communicated very clear to you. I'm not surprised of the outcome.
You should really draw a line between disrupting a forum like Bitcointalk with your censorship theme and trying to disrupt a forum like Github, where devs are hard at work and dont want to be distracted by off topic comments.

This of course also puts the whole "censorship" theme of yours in another light...

Edit : no need to shout...

demo16

newbie

Activity: 94

Merit: 0

Quote from: qwizzie on September 20, 2018, 02:01:00 PM

Quote from: demo16 on September 20, 2018, 01:39:05 PM

Quote from: qwizzie on September 20, 2018, 12:31:06 PM

Quote from: demo16 on September 20, 2018, 11:49:52 AM

Quote from: UdjinM6 on September 19, 2018, 05: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

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: qwizzie on September 20, 2018, 12:31:06 PM

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 :

https://i.imgur.com/W4JzgKi.jpg
https://i.imgur.com/Lg8BlKK.jpg

Looks like you went a bit too far there. In general it is a bad idea to disrupt github like that.

OH NO!!!
YOU DONT REMEMBER THE STORY AT ALL, SINCE ALL MY COMMENTS HAVE BEEN DELETED!!!
ALONG WITH MY ENTIRE GITHUB REPOSITORY!!!

Spit the cancer of censorship and of spamming out of the dash forums.
Let's LIBERATE the users/readers of the dash forums, NOW!

TaoOfSaatoshi

legendary

Activity: 2156

Merit: 1014

Dash Nation Founder | CATV Host

Dash Decentral (Episode 2 | Africa, Venezuela, and CheapAir.com)

#DashDecentral #DashNation

qwizzie

legendary

Activity: 2548

Merit: 1245

Quote from: demo16 on September 20, 2018, 01:39:05 PM

Quote from: qwizzie on September 20, 2018, 12:31:06 PM

Quote from: demo16 on September 20, 2018, 11:49:52 AM

Quote from: UdjinM6 on September 19, 2018, 05: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

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: qwizzie on September 20, 2018, 12:31:06 PM

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.

demo16

newbie

Activity: 94

Merit: 0

Quote from: qwizzie on September 20, 2018, 12:31:06 PM

Quote from: demo16 on September 20, 2018, 11:49:52 AM

Quote from: UdjinM6 on September 19, 2018, 05: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

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: qwizzie on September 20, 2018, 12:31:06 PM

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!!!!

Spit the cancer of censorship and of spamming out of the dash forums.
Let's LIBERATE the users/readers of the dash forums, NOW!

qwizzie

legendary

Activity: 2548

Merit: 1245

Quote from: demo16 on September 20, 2018, 11:49:52 AM

Quote from: UdjinM6 on September 19, 2018, 05: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

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.

For your sake i hope UdjinM6 does not have you on ignore in this bitcointalk forum....

Quote

Sow an act and you reap a habit.
Sow a habit and you reap a character.
Sow a character and you reap a destiny.
Forget to sow and pretty much nothing will happen.

NibiruHybrid

sr. member

Activity: 1232

Merit: 260

Europol Concerned About Increasing Illicit Activities Using Cryptocurrencies

A new report by the EU-focused law-enforcement organization’s “Internet Organised Crime Threat Assessment 2018” (IOCTA) says that cryptocurrency users and exchanges are at increasing risk of “criminal abuse” by bad actors within the space.

The report cited the risk of hacking and “extortion of personal data and theft” plaguing individuals involved in the cryptocurrency space. Cryptojacking, where illicit miners are hidden in web code to maliciously mine cryptocurrencies on unsuspecting users is also on the rise; some report it to have risen just under 1000% year-over-year from June 2017 to June 2018. While the report only mentioned Bitcoin, it is beginning to be recognized that Zcash and Monero are the growing cryptocurrencies of choice for illicit activities, whereas Dash used to commonly be lumped into this group. The report also cited fears of decentralized exchanges for enabling money lauding since they do not implement AML/KYC compliance standards.

Read more - https://www.dashforcenews.com/europol-concerned-about-increasing-illicit-activities-using-cryptocurrencies/

demo16

newbie

Activity: 94

Merit: 0

Quote from: UdjinM6 on September 19, 2018, 05: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

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

Whats wrong @udjim6?
Am I doing something wrong?
Is there a critical bug in the core wallet?

Spit the cancer of censorship and of spamming out of the dash forums.
Let's LIBERATE the users/readers of the dash forums, NOW!

cjl1984

member

Activity: 336

Merit: 10

The technical strength of DASH project is very good. Investors can consider buying some positions at a reasonable bargain. Holding this coin in the medium and long term will yield good returns.

NibiruHybrid

sr. member

Activity: 1232

Merit: 260

SEC Commissioner Argues for Relaxed Cryptocurrency Regulations

SEC Commissioner Hester M. Peirce recently gave a speech at the Cato Institute’s FinTech Unbound Conference where she discussed the importance of allowing cryptocurrencies to thrive without heavy SEC interference to foster innovation to benefit investors and consumers.

Ms. Peirce is known for being on the dissenting side of the SEC ruling to not allow Bitcoin ETFs to be traded and for doing so, she joked that she earned the nickname ‘CryptoMom’. She elaborated by making an analogy of her cryptocurrency regulatory views to being a “free-range mother” vs. being a “helicopter mom” since “certain achievements are possible only if we take risks”. She went on to highlight how there is often an urge by regulators to over-implement regulations to not only to protect these investors and consumers, but also protect themselves since it is often regulators that get blamed when things go wrong and individuals lose money.

Read more - https://www.dashforcenews.com/sec-commissioner-argues-for-relaxed-cryptocurrency-regulations/

TaoOfSaatoshi

legendary

Activity: 2156

Merit: 1014

Dash Nation Founder | CATV Host

Quote from: SoulRey on September 19, 2018, 02:50:57 PM

Respected community Dash, there is such project as UCOM and think with their hand there is most that not there is theft logo dash, here is the reference on their branch on forum https://bitcointalksearch.org/topic/ann-kzcash-kzc-2312421 it's not like not advertising this project, but they just turned it over and use it as their own logo. For me it is unacceptable and developers Dasha is this something to solve if only You had not given its consent for its use.

Thanks for bringing this to our attention! I’ll make sure others know about this.

KnightRiderus

sr. member

Activity: 630

Merit: 250

Quote from: NibiruHybrid on September 19, 2018, 12:14:30 PM

Hedge Fund Doubts Litecoin's Viability, How Does Dash Measure Up?

The crypto-fund Multicoin Capital has released an in-depth analysis on why they believe the arguments in favor of bull market movements for Litecoin are weak and do not stand up to scrutiny.

The paper started off by disclosing that the firm is short Litecoin and went into saying “Litecoin is a relic of the pre-smart contract platform crypto ecosystem” and is on the decline. The paper listed many reasons that included market maturation, negative catalysts such as Segwit and Lightning Network reducing the need for Litecoin, lack of funding to the Litecoin Foundation, and Charlie Lee’s divestment from Litecoin. The paper then goes on to discuss these and other attributes in more detail and debunks common arguments that are used to support Litecoin due to inaccuracies or insufficient evidence.

Read more - https://www.dashforcenews.com/hedge-fund-doubts-litecoins-viability-how-does-dash-measure-up/

in time almost every major investor will have his own dashnode. simply because such a large and stable project that gives good interest can not be left aside as it seems to me. the main thing is that the press and independent analysts who hear big investors and funds write more like that.

Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 348. (Read 9723748 times)