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

[xxxgoodgirls]

LOL!!!!

xxx have you recivered the coins???

 http://explorer.darkcoin.io/address/Xp2Eu9LGarCHNrFpEyZurUcuZQyStLso9A

1 input has moved!

Yeah they are safe (I hope) now. I just sent 5DRKs to the foundation.

[splawik21]

Xxx wallet has been moved!
1005 almost coin went on two directions
5 coins aent on http://explorer.darkcoin.io/address/3G5JS6bqJiYdpVcFb3zBiwHAcpRXsNaros

can someone tell me since when darkcoin addres starts with 3? Iwas convinced it is always X
Check this address inputs...strange....

Edit: just read your post now.
So where was your wallet??? Dump your privkey! And later you can drink
Happy end I think

[Minotaur26]

Xxx wallet has been moved!
1005 almost coin went on two directions
5 coins aent on http://explorer.darkcoin.io/address/3G5JS6bqJiYdpVcFb3zBiwHAcpRXsNaros

can someone tell me since when darkcoin addres starts with 3? Iwas convinced it is always X
Check this address inputs...strange....

That is a multisignature address and that is why it starts with 3. It needs two out of three signatures to send out funds. Foudnation addresses are multisig.

[splawik21]

Thnx Minotaur. Didn't know about that!
I hope that people will learn something from this lesson.

[xxxgoodgirls]

Edit: just read your post now.
So where was your wallet??? Dump your privkey! And later you can drink
Happy end I think

C:\VTRoot\HarddiskVolume3\Users\XXXX\AppData\Roaming\DarkCoin found the whole folder here.
Anyway I am taking now a lot more precautions than before, I learnt the lesson indeed.

[noobtrader]

just compress the whole folder and keep them safe in cold storage... 

[RenegadeMan]

I absolutely love Darkcoin and all the people that make up this community, but reading through all that's just happened to xxxgoodgirls and what stonehedge went through with the hack he suffered recently one would have to come to the conclusion that managing your locally stored Darkcoin is far from certain and assured. It's alarming to me that substantial amounts of value can be lost so easily and with such accompanying confusion that entraps even very experienced people.

Until the retention and securing of coins in wallets can be lifted up and out of this level of technical confusion and need for extreme (almost forensic) troubleshooting, Darkcoin is NOT going to be used by regular people. To read through pages and pages of someone battling to understand where their thousands of $ have gone and finally admitting defeat is terrible (so sorry for your loss xxx; l sure hope something gets resolved and you can retrieve your DRK somehow).

This really is an aspect of crypto that will prevent many people from getting involved (read: virtually everyone who is outside of these levels of technical ability which is 99.9%), We really need to spend a whole lot more time and effort on firming up wallet apps and infrastructure if Darkcoin is to be taken seriously as the potential to inexplicably lose all your DRK is very real.

I think you're being a bit pessimistic, but what I would like to see is automatic periodic backup to a second location of the wallet.dat, and a big popup on initial startup of a new wallet (or creation of a new address) encouraging the user to click a button to print out their privkey(s) - with "KEEP THESE PRIVATE AND SAFE!" at the top of the page and instructions on how to import them.

Yes, the concept is not so complex : you have to take care of Only ONE file protect by a complex password. (Mine have more than 25 char lenght).
After you have the dumpprivkey for anoher security feature.

For the hack and stole it's really another thing.
As i say : waiting for the 2FA, maybe enable a virtual keyboard (with randomnly placed key) that will not permit keyloger see you passphrass.
More complex, replace passphrase with biometirc like fingerprints.

Edit: well not sure good idea, if you loose your finger, then you loose you drk too... Lol bad luck

Yes I understand it's not so complex. I'm religiously backing up my wallet.dat, saving it in multiple locations and have it protected by a complex password. I guess my main concerns are that if someone not particularly technical is reading this thread and sees so much complexity when a competent user like xxxgoodgirls goes to move 1005 DRK, performs a basic test first by sending 1 DRK (which is successful) then follows through with the 1004 balance and it all turns to crap, it's hardly assuring. Six pages of intense interaction later and it's resolved (thank goodness; good work everyone) but people who aren't inclined to get that down and dirty into the guts of everything are just going to perceive it's techo-territory, very risky something will go terribly wrong and not a real product yet.

I agree the 2FA will make a huge difference and substantially mitigate the risk of having your coins stolen. And I think the virtual randomly-place-key keyboard would be a great feature too.

Is there a guide somewhere that explains what "dumpprivkey" actually does? It's mentioned here in this thread again and again but I've never seen any real explanation of what this achieves, why it's important and how it helps protect you. I'd really like to see more plain-English explanations of these various functions and how to maintain best practise with wallets re hot and cold storage, paper, etc.

[thelonecrouton]

Is there a guide somewhere that explains what "dumpprivkey" actually does? It's mentioned here in this thread again and again but I've never seen any real explanation of what this achieves, why it's important and how it helps protect you. I'd really like to see more plain-English explanations of these various functions and how to maintain best practise with wallets re hot and cold storage, paper, etc.

Help > Debug window > console:
'walletpassphrase <passphrase> 30'
'dumpprivkey <address>'  *note, you may have more than one address in your wallet that has coins in it, dumpprivkey for each address or move all coins into one address first*

 - copy/print/keep safe the privkey, then, when disaster strikes:

Help > Debug window > console:
'importprivkey <privkey>'


Simple.

[xxxgoodgirls]

I absolutely love Darkcoin and all the people that make up this community, but reading through all that's just happened to xxxgoodgirls and what stonehedge went through with the hack he suffered recently one would have to come to the conclusion that managing your locally stored Darkcoin is far from certain and assured. It's alarming to me that substantial amounts of value can be lost so easily and with such accompanying confusion that entraps even very experienced people.

Until the retention and securing of coins in wallets can be lifted up and out of this level of technical confusion and need for extreme (almost forensic) troubleshooting, Darkcoin is NOT going to be used by regular people. To read through pages and pages of someone battling to understand where their thousands of $ have gone and finally admitting defeat is terrible (so sorry for your loss xxx; l sure hope something gets resolved and you can retrieve your DRK somehow).

This really is an aspect of crypto that will prevent many people from getting involved (read: virtually everyone who is outside of these levels of technical ability which is 99.9%), We really need to spend a whole lot more time and effort on firming up wallet apps and infrastructure if Darkcoin is to be taken seriously as the potential to inexplicably lose all your DRK is very real.

I think you're being a bit pessimistic, but what I would like to see is automatic periodic backup to a second location of the wallet.dat, and a big popup on initial startup of a new wallet (or creation of a new address) encouraging the user to click a button to print out their privkey(s) - with "KEEP THESE PRIVATE AND SAFE!" at the top of the page and instructions on how to import them.

Yes, the concept is not so complex : you have to take care of Only ONE file protect by a complex password. (Mine have more than 25 char lenght).
After you have the dumpprivkey for anoher security feature.

For the hack and stole it's really another thing.
As i say : waiting for the 2FA, maybe enable a virtual keyboard (with randomnly placed key) that will not permit keyloger see you passphrass.
More complex, replace passphrase with biometirc like fingerprints.

Edit: well not sure good idea, if you loose your finger, then you loose you drk too... Lol bad luck

Yes I understand it's not so complex. I'm religiously backing up my wallet.dat, saving it in multiple locations and have it protected by a complex password. I guess my main concerns are that if someone not particularly technical is reading this thread and sees so much complexity when a competent user like xxxgoodgirls goes to move 1005 DRK, performs a basic test first by sending 1 DRK (which is successful) then follows through with the 1004 balance and it all turns to crap, it's hardly assuring. Six pages of intense interaction later and it's resolved (thank goodness; good work everyone) but people who aren't inclined to get that down and dirty into the guts of everything are just going to perceive it's techo-territory, very risky something will go terribly wrong and not a real product yet.

Remember the issue had nothing to do with the tech itself but it was a figment of the human error (I ignored the sandbox popup alert). Good the notification flashed to my mind, otherwise it would have lasted several pages more till the loss acceptance .
Anyway hacking, phishing and all of those activies which involve stealing on the internet are also threats to fiat currencies as well.
Do not panic, we are still in the early phase, bitcoin and its brothers are still nerd money.
With adoption, you'll see everything becoming more and more user friendly.

ps I alway blame Windows, moving my coins to fedora asap!

[RenegadeMan]

Is there a guide somewhere that explains what "dumpprivkey" actually does? It's mentioned here in this thread again and again but I've never seen any real explanation of what this achieves, why it's important and how it helps protect you. I'd really like to see more plain-English explanations of these various functions and how to maintain best practise with wallets re hot and cold storage, paper, etc.

Help > Debug window > console:
'walletpassphrase <passphrase> 30'
'dumpprivkey <address>'  *note, you may have more than one address in your wallet that has coins in it, dumpprivkey for each address or move all coins into one address first*

 - copy/print/keep safe the privkey, then, when disaster strikes:

Help > Debug window > console:
'importprivkey <privkey>'


Simple.

Sorry lonecrouton but that is the sort of answer I'd expect from some arrogant young punk on a support line somewhere. Perhaps you're being sarcastic?

I'm waving the "hey guys if we want to see wider adoption this thing has to be lifted up out of technobabble speak" flag and your "simple" response is just more technobabble.

I'll ask again. Is there a plain-English guide to some of these commands that explains what they achieve and what the best practise is to ensure you're not going to lose your coins?

[YourMother]

Is there a guide somewhere that explains what "dumpprivkey" actually does? It's mentioned here in this thread again and again but I've never seen any real explanation of what this achieves, why it's important and how it helps protect you. I'd really like to see more plain-English explanations of these various functions and how to maintain best practise with wallets re hot and cold storage, paper, etc.

Help > Debug window > console:
'walletpassphrase <passphrase> 30'
'dumpprivkey <address>'  *note, you may have more than one address in your wallet that has coins in it, dumpprivkey for each address or move all coins into one address first*

 - copy/print/keep safe the privkey, then, when disaster strikes:

Help > Debug window > console:
'importprivkey <privkey>'


Simple.

It's actually too simple

I will forward your message to my grandma because she's excited on using cryptocurrencies for her online shopping. "Grandma, use DUMPPRIVKEY before sending the funds" "Also, make sure that your Antivirus will not sandbox shit randomly."

[Lebubar]

I absolutely love Darkcoin and all the people that make up this community, but reading through all that's just happened to xxxgoodgirls and what stonehedge went through with the hack he suffered recently one would have to come to the conclusion that managing your locally stored Darkcoin is far from certain and assured. It's alarming to me that substantial amounts of value can be lost so easily and with such accompanying confusion that entraps even very experienced people.

Until the retention and securing of coins in wallets can be lifted up and out of this level of technical confusion and need for extreme (almost forensic) troubleshooting, Darkcoin is NOT going to be used by regular people. To read through pages and pages of someone battling to understand where their thousands of $ have gone and finally admitting defeat is terrible (so sorry for your loss xxx; l sure hope something gets resolved and you can retrieve your DRK somehow).

This really is an aspect of crypto that will prevent many people from getting involved (read: virtually everyone who is outside of these levels of technical ability which is 99.9%), We really need to spend a whole lot more time and effort on firming up wallet apps and infrastructure if Darkcoin is to be taken seriously as the potential to inexplicably lose all your DRK is very real.

I think you're being a bit pessimistic, but what I would like to see is automatic periodic backup to a second location of the wallet.dat, and a big popup on initial startup of a new wallet (or creation of a new address) encouraging the user to click a button to print out their privkey(s) - with "KEEP THESE PRIVATE AND SAFE!" at the top of the page and instructions on how to import them.

Yes, the concept is not so complex : you have to take care of Only ONE file protect by a complex password. (Mine have more than 25 char lenght).
After you have the dumpprivkey for anoher security feature.

For the hack and stole it's really another thing.
As i say : waiting for the 2FA, maybe enable a virtual keyboard (with randomnly placed key) that will not permit keyloger see you passphrass.
More complex, replace passphrase with biometirc like fingerprints.

Edit: well not sure good idea, if you loose your finger, then you loose you drk too... Lol bad luck

Yes I understand it's not so complex. I'm religiously backing up my wallet.dat, saving it in multiple locations and have it protected by a complex password. I guess my main concerns are that if someone not particularly technical is reading this thread and sees so much complexity when a competent user like xxxgoodgirls goes to move 1005 DRK, performs a basic test first by sending 1 DRK (which is successful) then follows through with the 1004 balance and it all turns to crap, it's hardly assuring. Six pages of intense interaction later and it's resolved (thank goodness; good work everyone) but people who aren't inclined to get that down and dirty into the guts of everything are just going to perceive it's techo-territory, very risky something will go terribly wrong and not a real product yet.

I agree the 2FA will make a huge difference and substantially mitigate the risk of having your coins stolen. And I think the virtual randomly-place-key keyboard would be a great feature too.

Is there a guide somewhere that explains what "dumpprivkey" actually does? It's mentioned here in this thread again and again but I've never seen any real explanation of what this achieves, why it's important and how it helps protect you. I'd really like to see more plain-English explanations of these various functions and how to maintain best practise with wallets re hot and cold storage, paper, etc.

I ear you, and sure that someone like my mother in law will never put it hand on this...
Maybe we need to have a site wallet ( maybe like coinbase), i already ear everybody screaming out the centralized thing about this. But we have to think that some people don't want to mess up with all this "tecnicals details" maybe a site ran by foundation approved or something... WebWallet no block chain to download no need to backup walet.dat etc... Only for one part of the user. If this can attract new user why not no?

I also ear about gox... That's why it should be run by foundation and/or approved by it!

[AlexGR]

No, --zapwallettxes would delete any unconfirmed payments.  -rescan or -reindex (not sure if they're different) would redownload the blockchain.

I was thinking that it shouldn't be too difficult, code-wise, to create 2-3 buttons or options in the qt client that would restart the wallet with such options.

It would be extremely useful to prevent "scares" for users who do not know how to recover, reindex or delete/reset a broadcast and who come here for help.

It would be much easier, support-wise, to simply tell a user "click on the reindex button", or "click on delete unconfirmed payments" (which would automatically restart the client in this mode).

CMD-line is so 80's and 90's....

[qwizzie]

No, --zapwallettxes would delete any unconfirmed payments.  -rescan or -reindex (not sure if they're different) would redownload the blockchain.

I was thinking that it shouldn't be too difficult, code-wise, to create 2-3 buttons or options in the qt client that would restart the wallet with such options.

It would be extremely useful to prevent "scares" for users who do not know how to recover, reindex or delete/reset a broadcast and who come here for help.

It would be much easier, support-wise, to simply tell a user "click on the reindex button", or "click on delete unconfirmed payments" (which would automatically restart the client in this mode).

CMD-line is so 80's and 90's....

i agree, would be very helpfull and make the wallet far more user friendly

[illodin]

diamonds as an asset backed reserve for DRK

Could you (or anyone who understands it) explain what that means for someone who's not familiar with those financial terms.   

[thelonecrouton]

Is there a guide somewhere that explains what "dumpprivkey" actually does? It's mentioned here in this thread again and again but I've never seen any real explanation of what this achieves, why it's important and how it helps protect you. I'd really like to see more plain-English explanations of these various functions and how to maintain best practise with wallets re hot and cold storage, paper, etc.

Help > Debug window > console:
'walletpassphrase <passphrase> 30'
'dumpprivkey <address>'  *note, you may have more than one address in your wallet that has coins in it, dumpprivkey for each address or move all coins into one address first*

 - copy/print/keep safe the privkey, then, when disaster strikes:

Help > Debug window > console:
'importprivkey <privkey>'


Simple.

Sorry lonecrouton but that is the sort of answer I'd expect from some arrogant young punk on a support line somewhere. Perhaps you're being sarcastic?

I'm waving the "hey guys if we want to see wider adoption this thing has to be lifted up out of technobabble speak" flag and your "simple" response is just more technobabble.

I'll ask again. Is there a plain-English guide to some of these commands that explains what they achieve and what the best practise is to ensure you're not going to lose your coins?

What more do you want? What part exactly are you confused about? Since you are here on the internet posting in a cryptocurrency thread I didn't think 'Help > Debug window > console' followed by a few simple words to type into the text entry box would be quite such a baffling and insurmountable  intellectual challenge for you.

[oblox]

diamonds as an asset backed reserve for DRK

Could you (or anyone who understands it) explain what that means for someone who's not familiar with those financial terms.   

Means there would be some exchange rate for x DRK for x carats in diamonds (although then you are going into the four C's). Asset backing helps hold value. Terms obviously are unknown but I doubt we'll see any sort of backing personally.

[turk-fx]

So i have an issue. My masternode hasnt been paid for 8 days. So I will move my funds to a new address. Does it have to be created by "getoccountaddress 0" or Can I use the first address that is created in the wallet? And once I move the funds to a new address, all I have to do is masternode start command?

[AlexGR]

diamonds as an asset backed reserve for DRK

Could you (or anyone who understands it) explain what that means for someone who's not familiar with those financial terms.   

Means there would be some exchange rate for x DRK for x carats in diamonds (although then you are going into the four C's). Asset backing helps hold value. Terms obviously are unknown but I doubt we'll see any sort of backing personally.

Hmm... I would think that diamonds, being unique / non-uniform / subjective in their valuation, are not a very suitable for backing assets of financial instruments. Precious metals on the other hand are much better suited for this job. They are divisible and fungible.

[xxxgoodgirls]

So i have an issue. My masternode hasnt been paid for 8 days. So I will move my funds to a new address. Does it have to be created by "getoccountaddress 0" or Can I use the first address that is created in the wallet? And once I move the funds to a new address, all I have to do is masternode start command?

The address must be the 0 address or it won't work as far as I know.