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

Just happened. Desynchronized again. That was fast.
So deleting the peer.dat doesnt help.

My wallet quit syncing. I tried adding a .conf with addnode's but nah-dah.
What is the fix?
I even tried connection to tor.
literally the timer is going backwards. It says syncing but it's not.
That coin has been unconfirmed for 16 hrs.
 

Will do. Can tell you the result tomorrow. It's mostly ok for the first 2 hours.
I found an old deleted peer.dat form 21.4 so I guess I already tried that and didnt work. Not sure though if it were with the beta or the rc1.
I think this peer.dat deleting will only work if no other node still has this foreign nodes in their list.
We will see.

Dito, sure it's a good investment!

Try deleting peers.dat and restarting. I'm curious to see if that fixes it.

Wait some longer.
I have the RC1 running since it was available. The issue did not dissapear.




It is something that has to be corrected in the coin itself. Amuseing to me LimeCoin dev's understood it. They decided not to do it since it requires a hard fork. I recomment the dev to read it up on the link I posted. It links over to that Limecoin.

I didn't mine LimeCoins because that issue and I don't see any future in that coin anyway (byway there a 2 different LimeCoins now so they kill themself)

DarkCoin is a bit a different story. I am not really happy with DarkCoin for a number of reasons but I know that it is a major player and gains values and so I go along with it.

Chaeplin's instruction is a workaround.

He listed all the foreign IP's coming from LiteCoin and WorldCoin that connect to DarkCoin and tells you to set your routing on your system to route those IP's into nirvana so the client doesn't sees them.

I haven't tested it yet. Busy with others. But I am confident it will work.

However in looking into the future I more liked the dev would take it serious and fix it by the next occasion.
A serious coin with such a flaw is a bit of a joke.

coinmine.pw


first multipool with x11 algo with profit switcher

@the moment only darkcoin and hirocoin.
vote for more x11 coins to be added

LOL

Come on dude, Evan writes a decentralized CoinJoin and you don't think he can change an int?

Ya'll be trippin'. He'll get to it, I guarantee it.

I was a big believer in DRK but have now liquidated my position. It has been too long without a proper response/fix from the developer on this issue. Perhaps if they correct it I will believe in the coin again. Its hard to take DRK seriously until this is addressed.

The main change that has occurred is that DRK coin was in its own bearish trend for the last several months. I believe it initiated when the theft occurred at C-Cex and many, many DRK kept being dumped on Poloniex.  So while the rest of the alt currency space saw its own down trend that had a spectacular reversal (particularly with BC leading the charge) DRK was still in its own Bear trend.  With the recent run up with the release of RC 1 there was a test of that bearish sentiment and a reversal appeared to occur.   Now that the market has formed a very bullish pattern of cup and handle on the daily charts the order book is getting very thin at these prices and multiple whales who had been waiting on the sideline for confirmation have obviously been moving in to get a piece of DRK.

 The difference between a bear trend and a bull trend is that in a bear trend the market "bear"ly (sorry) reacts to any positive news, but has an over-exaggerated response to negative news.  In a bull market that is reversed. While there were plenty of updates and developments in the DRK space during the last two months they hardly made any impact on the price before encountering waves of selling pressure. Now every bit of positive news should make the price rise significantly.  DRK being one of the few coins with TRULY innovative functionality will make it a serious contender in the altcoin space in the next 6 months to year.

I think now that the DRK market has been released from the stranglehold of the bear trend it will start to reflect some of the recent developments:  
One, Dark send is functional;
Two, The maximum coin limit has been set at ~22 Million which was lower than the ~80 million it was for a time;
Three, X11 is its own very innovative mining algorithm;
Four, Dark Gravity Wave is its own unique difficulty adjustment functionality;
Five; the master node functionality is its own innovation which gives whales incentive to load up on 1000 blocks of DRK because now they act somewhat analogously to miners/PoS.  

All that, and we have a known upcoming news event that is virtually guaranteed to raise the price, which is the release of Open Source. Actually according to Evan's timeline, 3 upcoming news events:
 One, RC 2 which gives master node income generating functionality;  
Two, a "trusted third party" vets the code;
Three, the release of the code as fully open source.

 The coin has one of the most innovative Devs in the alt space.  He is one of the only Alt devs I see playing in the same league of intellect as Satoshi Nakamoto.  To get an idea of where DRK is goin one only need to look at the other recent hot investments in the Cryptospace.  Look at Safecoin. They were able to raise $8 million in a day with just hype. They are suspiciously similar to namecoin in concept. $8 million dollars is over twice DRK's current market cap.  If $8 Million flowed into an existing coin and not an IPO then the market cap would actually be an order of magnitude higher than $8 million because most holders actually wouldn't part with their coins at existing prices. Then look at Black Coin. The only innovation Black Coin had was how they set up multi pool which was really still a rip off of the Bitcoin Multi Pool concept, otherwise the coin's concept itself was a rip off of Mintcoin and PeerCoins PoS. I'll give it that it was a unique application of multipool functionality, instead of pointing the multipool at BTC they pointed it at an alt.  Clever, but only a fraction of the cleverness we've seen in the DRK space. And that has gotten BC up to spot 9 on coinmarketcap as of today with $11 Million, AFTER a huge pullback in BC price (4 days ago it was $20 million, ~5x DRK's current market cap).  If DRK gos up to meet or exceed BC in market cap that would put it at at virtually triple today's price.     I think the fundamentals clearly suggest that its a matter of WHEN not IF that happens (at minimum).  Barring any Black Swan events the future is looking rosy for the price indeed and its starting to look very cheap even at the current price.

Is BTC mind bogglingly even slower than usual for anyone else today or is it just me? 

Wait some longer.
I have the RC1 running since it was available. The issue did not dissapear.




It is something that has to be corrected in the coin itself. Amuseing to me LimeCoin dev's understood it. They decided not to do it since it requires a hard fork. I recomment the dev to read it up on the link I posted. It links over to that Limecoin.

I didn't mine LimeCoins because that issue and I don't see any future in that coin anyway (byway there a 2 different LimeCoins now so they kill themself)

DarkCoin is a bit a different story. I am not really happy with DarkCoin for a number of reasons but I know that it is a major player and gains values and so I go along with it.

Chaeplin's instruction is a workaround.

He listed all the foreign IP's coming from LiteCoin and WorldCoin that connect to DarkCoin and tells you to set your routing on your system to route those IP's into nirvana so the client doesn't sees them.

I haven't tested it yet. Busy with others. But I am confident it will work.

However in looking into the future I more liked the dev would take it serious and fix it by the next occasion.
A serious coin with such a flaw is a bit of a joke.

Ok thanks for the prompt response! I was under impression that RC1 was optional.

Edit: Can confirm - RC1 has resolved the issue.

Agreed, The issue is reoccuring for me. Chaeplin's instructions were a little confusing for me to follow - did it solve the issue?

Could DEV please comment on the severity of this issue? Is it simply not an issue? Not sure =/

Grab RC1, the version is v0.10.4.0. There was a bug with downloading blocks in the previous beta. I just tested both updated versions with no problem