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

[Ozziecoin]

I don't think the market realises that Drk has functional anonymity now.

It had functional anonymity before RC4 and RC3. RC4 is implementation of DS+ improving the set.

RC4 needs to be regression utilized, all scenarios vetted in mainnet, any and all bugs squashed over the next few days. 10s of people put 100s of hours in testnet, so it is upto users to get it going now on mainnet.

I know Evan will never confess to it in the open, but the sneaky release was needed to not give pump and dumpers any chance to manipulate which they did with announcements for RC3 and all other wannabe anon coins.

You will see the buys coming in slowly over the next few days though with media hype, KA's code review and what not. But then again whales may also sneak in anytime they want. You never know what and how they play games.

ok, makes sense. TBH, I had some Drk ready to dump into the market on spike. LOL. But now I'll transfer to own wallet.

[1714934021]

1714934021

[1714934021]

1714934021

[JGCMiner]

make a backup of your wallet.dat

delete everything in the folder where it was

run latest qt

wait for new chain

close client when new chain full

move backup wallet over the one that the qt just created

launch qt with --salvagewallet option

just doing the --salvagewallet option won't do it. It's probably something in chainstate that needs killed, but it's easier to just wipe the whole folder and MAKE SURE YOUR BACKUP IS NOT IN THERE WHEN YOU WIPE IT!

This fixed my issue as well. Thanks again.

Good to here this got fixed.  Still no idea why it happened in the first place? Also, if you get a chance it would probably be good to send your debug file to Evan.

[Jesse Livermore]

I don't think the market realises that Drk has functional anonymity now.

I one million percent agree.
The BTC sacred cow taking a shellacking might have something to do with it, too.

[AlexGR]

So long as there is no forking (which there isn't) you are right that coins can be lost. Evan did say something about not selecting "no preference" when sending....

Wow, he said that? Maybe next time he should post that on the wallet download page so people don't lose a grand like I may have.

I think JGCMiner meant to say "So long as there is no forking (which there isn't) you are right that coins CAN'T be lost" to be in agreeance. JGC, am I correct?

Actually they can't be lost with forking either. A fork can only double the number of coins (double spend).

As far as I know, coins can never be lost, under any circumstance. The only issue is whether a wallet can see them or not (corruption scenario for example).

[Ozziecoin]

make a backup of your wallet.dat

delete everything in the folder where it was

run latest qt

wait for new chain

close client when new chain full

move backup wallet over the one that the qt just created

launch qt with --salvagewallet option

just doing the --salvagewallet option won't do it. It's probably something in chainstate that needs killed, but it's easier to just wipe the whole folder and MAKE SURE YOUR BACKUP IS NOT IN THERE WHEN YOU WIPE IT!

This fixed my issue as well. Thanks again.

Good to here this got fixed.  Still no idea why it happened in the first place?

There were several incidences of wallet corruption on testnet, mainly at the time of wallet upgrades. It happened to me once, and I ran salvagewallet to recover.

[Ozziecoin]

So long as there is no forking (which there isn't) you are right that coins can be lost. Evan did say something about not selecting "no preference" when sending....

Wow, he said that? Maybe next time he should post that on the wallet download page so people don't lose a grand like I may have.

I think JGCMiner meant to say "So long as there is no forking (which there isn't) you are right that coins CAN'T be lost" to be in agreeance. JGC, am I correct?

Actually they can't be lost with forking either. A fork can only double the number of coins (double spend).

As far as I know, coins can never be lost, under any circumstance. The only issue is whether a wallet can see them or not (corruption scenario for example).

The wallet can be out of sync with the network and then try to double spend inputs that are not there. This happened to someone who opened their wallet.dat in two locations.

[camosoul]

I don't think the market realises that Drk has functional anonymity now.

I know Evan will never confess to it in the open, but the sneaky release was needed to not give pump and dumpers any chance to manipulate which they did with announcements for RC3 and all other wannabe anon coins.

I don't believe it's a conscious effort. Evan, and his project, are not about hype. He does without it because he's not all about it. If you don't care about show dogs, do you subscribe to a monthly magazine about them? DRK doesn't care about hype, so there isn't any.

[camosoul]

I'd say my coins are anonymized if I hadn't had to show part of them to everyone... :-p

[georgem]

I'd say my coins are anonymized if I hadn't had to show part of them to everyone... :-p

No more the mysterious wallet amount guy...  

Now you know what it feels like to be nude all the time, like me.
But one day, ... I will put the camouflage clothes on and disappear... FOREVER!

[JGCMiner]

make a backup of your wallet.dat

delete everything in the folder where it was

run latest qt

wait for new chain

close client when new chain full

move backup wallet over the one that the qt just created

launch qt with --salvagewallet option

just doing the --salvagewallet option won't do it. It's probably something in chainstate that needs killed, but it's easier to just wipe the whole folder and MAKE SURE YOUR BACKUP IS NOT IN THERE WHEN YOU WIPE IT!

This fixed my issue as well. Thanks again.

Good to here this got fixed.  Still no idea why it happened in the first place?

There were several incidences of wallet corruption on testnet, mainly at the time of wallet upgrades. It happened to me once, and I ran salvagewallet to recover.

Hmmm, I dont remember it being widespread, but if so then this needs to be looked at ASAP.  Even if you get the coins back it is not good for DRK, and then you have rare cases like Camo when you really may not get them back (unrecoverable wallet.dat corruption).  

[AlexGR]

Is IP obfuscation through masternodes enabled with RC4? Or is it RC5 material?

[oblox]

Well, after waiting for the denominates to confirm, I turned darksend off and to 1 round, closed the wallet, reopened, and turned it back on. Started denominating about 15 minutes or so after specifying 2500 for anon coins (had around 2100 in this wallet). All but 2 are anon.

I'm happy with the RC4 release. No forks, it works for many. While the rounds need fixing, we can start getting some real testing done on a large network with major hash. We now have the base to build off of. Exciting times.

[Ozziecoin]

Is IP obfuscation through masternodes enabled with RC4? Or is it RC5 material?

Not RC4, AFAIK.

[sharkbyte093]

Is IP obfuscation through masternodes enabled with RC4? Or is it RC5 material?

That's not implemented yet, I think that's next release.

[AlexGR]

Is IP obfuscation through masternodes enabled with RC4? Or is it RC5 material?

That's not implemented yet, I think that's next release.

Alright, it's building up nicely for the final version...

[Sapien]

make a backup of your wallet.dat

delete everything in the folder where it was

run latest qt

wait for new chain

close client when new chain full

move backup wallet over the one that the qt just created

launch qt with --salvagewallet option

just doing the --salvagewallet option won't do it. It's probably something in chainstate that needs killed, but it's easier to just wipe the whole folder and MAKE SURE YOUR BACKUP IS NOT IN THERE WHEN YOU WIPE IT!

I have a little bit different issue and it didn't help. My denominate transaction got stuck for 6 hours and --salvagewallet option works strangely. It returns only 500 drk, not my total balance(~623.6). What do?

https://i.imgur.com/Z5AlGPL.png

[libivan]

DRK deposits and withdrawals are frozen at Poloniex... I've got no luck with polo, it's always the same story

Hi,

DRK deposits and withdrawals are frozen, as soon as this normalize your transaction will be credited.

I apologize for the inconvenience,

Johnny Garcia

Ticket: http://poloniex.freshdesk.com/helpdesk/tickets/...

[tifozi]

Hmmm, I dont remember it being widespread, but if so then this needs to be looked at ASAP.  Even if you get the coins back it is not good for DRK, and then you have rare cases like Camo when you really may not get them back (unrecoverable wallet.dat corruption).  

That is a total outlier. It doesn't have anything with DRK. It could have happened with any other coin (wallet.dat "corruption").

Basically when sending large amounts, paying transaction fees ensures delivery. I usually override it in wallet without waiting for a prompt. This goes for all Bitcoin clones.

[meatgrinder]

Guys, while you watch your wallets denominating, could you vote for DRK here: https://www.coingateway.net/

Done.

Done

[georgem]

Guys, while you watch your wallets denominating, could you vote for DRK here: https://www.coingateway.net/

Done.

Done

Done that too.