[ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65%

[shveicar]

They should change the way the do business otherwise they will be out of business. It's just ridiculous.

Tell me about it .. I had no reply from them about updating Diamond wallet and the ticked was placed 18 days ago. I was reminding them every 2 -3 days about it and nothing, even now the ticket is still unresolved. Had to go great lengths to get to them... but if they lied to me about the update, then yes it would be ridiculous and no chance I would trust them again.

All this is unfortunately true. But cryptsy so far the only major exchangers for Diamond. After removing all the errors with the wallet, you should first resolve issues with additional heat exchangers.
DMD should develop and increase its capitalization.

[physixz]

Try running the wallet with these flags : -repairwallet (and if the first doesn't help use the other one) -salvagewallet

i ran both and the second one seems to have deleted everything so no i have no transactions or anything....

[polanskiman]

Same thing is happening to me. WTF? This time I mean it.

The coins are never lost, all information is stored in the distributed blockchain. (Unless the coins you've got come from the wrong fork, then they would not be compatible. However if you had them before all this drama started to unfold they are still there.)

Try running the wallet with these flags : -repairwallet (and if the first doesn't help use the other one) -salvagewallet

Cryptsy had ensured me they have updated the wallet (Have a tweet as a proof)... I'm inquiring about it now, but please don't expect any concrete answers straight away (it's not their style).

All the coins (99.9%) I have come from before the PoS started 2 days ago. Remember yesterday when I posted the screenshots. All my coins where there only moreless half was showing as "stake". That's why I posted about some of my coins missing. After I closed the wallet and restarted it and the assertion failed error moreless half are now effectively missing. I tried both flags and none brought my coins back... The -salvagewallet flags actually makes a backup file of the wallet, that all.

[polanskiman]

Try running the wallet with these flags : -repairwallet (and if the first doesn't help use the other one) -salvagewallet

i ran both and the second one seems to have deleted everything so no i have no transactions or anything....

The -salvagewallet flag backed up your wallet and changed the extension to .bak file. You can change it back to .dat and you should revert to your previous state. Still the missing coins are still gone for me too.......

[polanskiman]

I re-run the first command I am getting this:

Code:

00:07:20

repairwallet


00:07:24

{
"mismatched spent coins" : 28,
"amount affected by repair" : 132.27361300
}

SWEET they are back!!!! For some reason they didn't show up before. Thanks popshot. For a second a nearly became hulk!!


@physixz Try it again. I did it within the console of the wallet. One thing to remember. Whatever happens always keep a backup of your wallet.dat file. This is where all the coins are.

[polanskiman]

I am seeing a few like this with the getpeerinfo command:

Code:

{
"addr" : "50.77.68.233:36303",
"services" : "00000001",
"lastsend" : 1403889867,
"lastrecv" : 1403889867,
"conntime" : 1403889831,
"version" : 60006,
"subver" : "/Diamond:2.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 464631,
"banscore" : 0
},
{
"addr" : "93.186.192.53:50789",
"services" : "00000001",
"lastsend" : 1403889865,
"lastrecv" : 1403889865,
"conntime" : 1403889854,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 139501,
"banscore" : 0
}

Note the subversion. They have clearly not updated to the latest version.

[popshot]

Try running the wallet with these flags : -repairwallet (and if the first doesn't help use the other one) -salvagewallet

i ran both and the second one seems to have deleted everything so no i have no transactions or anything....

OK, lets do it the hard way then. They way you recover from paper wallets. I would have imagined that -salvagewallet would do just that  attempt to recover private keys from a corrupt wallet.dat, but if that hasn't helped lets try the other way.

Found and adapted this info:

1) Back up your entire folder that holds your wallet.
Users\Username\AppData\Roaming\Diamond 

2)  Start diamond-qt wallet and export a log of all your present transactions for safekeeping.

3) Click on Help > Debug window > Console to bring up the command line.

4) On the command line type (no quotes) "listaddressgroupings". Copy and paste all the addresses to a text file. Save that text file but keep it open.

5) For each address (you may have only a few or several) type on the command line of your QT wallet (again no quotes)

'dumpprivkey' and a space then after the space paste in the address.  The client will then give you a long set of letters and numbers.  Copy and paste this with the address it matches up with in your text file to use later.

6) Repeat step 5 for each address that you have. 

7)  Close the wallet.  Delete anything in the Users\Username\AppData\Roaming\Diamond folder  EXCEPT your conf file and make sure you have everything backed up.

8 ) Start diamond-qt wallet. It will connect to the network and start downloading the blockchain.

9) Use the same method as in step 3 above to open the command line.  Get that text file with the list of addresses and private keys and type on the command line (again no quotes)

'importprivkey' , a space, then paste a private key after it and hit enter. Wait a few seconds for the client to accept the command. Repeat as many times as necessary depending on how many private keys you had. Don't forget any.  If you try to do one twice you will get an error.

10) Close your diamond-qt wallet client. It does not matter how much of the blockchain may have downloaded.  Open it again and let the entire blockchain download. Do not try to send coins or mine while it is downloading.   

11) When the blockchain is complete your coins should all be in there where they belong

[shveicar]

look at the http://www.coinwarz.com/cryptocurrency Power of the network DMD periodically  exceeds an Groestlcoin. Is this normal?

[popshot]

look at the http://www.coinwarz.com/cryptocurrency Power of the network DMD periodically  exceeds an Groestlcoin. Is this normal?

When comparing, they seem to have twice as much hashing power - when we had 51 they had 109 ..
At the moment we seem to have the same hashing power as them, or even slightly more as they use improved mining soft.

I see it as a positive sign

[popshot]

Can I ask everyone to spam @cryptsy (Big Vern) Twitter and (so called) Cryptsy Helpdesk/feshdesk asking them to update the wallet, now they pushed it way too far.


As for mintpal.. it's not that easy to get there, for example through voting.. look at the amount of votes required to be accepted.
 
Vote MintPal:
https://www.mintpal.com/voting#DMD
 

[ruleland]

"proof-of-stake" : 0.02601358

Yes, all good, network difficulty is up which means it is working correctly.

Wallet is minting, but generated coins are not accepted (3 times in a row now)
 
wallet version 2.0.2.1

In what sense not accepted?

If orphaned then someone was quicker than you, however you should not lose coin age if stake attempt was not successful.

It looks like all 3 where orphaned (last one after 3 confirmations). Will wait for another stake attempt

Seems to be minting fine after removing the block chain data, the peers.dat and adding the specific node 193.68.21.19 and removing all others in the diamond.conf and let it resync again.

had to disable Detach databases at shutdown, as it seems to corrupt the blockchain data and throwing the runtime assertion on restart (had to resync with a older blockchain copy when it did).

just one question, is there any way to remove the orphaned transactions, as they fill up the "recent transactions" and don't show my most recent transactions (sorting issue on status?)

[ruleland]

Can I ask everyone to spam @cryptsy (Big Vern) Twitter and (so called) Cryptsy Helpdesk/feshdesk asking them to update the wallet, now they pushed it way too far.


As for mintpal.. it's not that easy to get there, for example through voting.. look at the amount of votes required to be accepted.
 
Vote MintPal:
https://www.mintpal.com/voting#DMD
 

anyone with a decent trading history can vote one time every hour without paying the BTC voting fee

[shveicar]

I hope everyone knows that the first of July, cryptsy administered verification for their clients. Without  verification, daily amount can not exceed $ 1,000 per day. Many people will not agree to such an exchanger. This is the way a broken exchanges mtgox. Diamond will be needed a new large exchanger.

[guidosuller]

i send coins for cryptsy and not arrived

[cryptonit]

MY WAY TO BE ON RIGHT BLOCKCHAIN:

i just returned today from italy

and read lot people who did not update their wallets
create fork rodeo  

so what i did was this

add to diamond.conf in appdata diamond folder the line

maxconnections=1
addnode=193.68.21.19



and remove all other addnode lines there

delete the peers.dat in appdata diamond folder

create a backup of in appdata diamond folder

start diamond 2.0.2.1 wallet

let the wallet sync (keep in mind i had a synced blockchain to around 21.june so not much to sync)

when sync completed compare diff (mouseover bottom right green checkmark of wallet) with http://dmdpool.digsys.bg/

if its same u are on right blockchain

close wallet

diamond.conf in appdata diamond folder remove the line maxconnections=1 save it

and start wallet again

once wallet started and sync

unlock wallet

and wait for pos rewards
(in my case first one came 30 sec after unlock wallet and nearly instant got first confirmation))



WELCOME ON RIGHT BLOCKCHAIN!

-------------------------------------------------


i read about other wallet troubles beside some people being unlucky synced to wrong fork

im sorry for the inconvenience this is creating for the people who got this

we did this time a extended beta and that error did not appear in beta

as popshot and danbi said already we will research and try to provode a fix  asap

[popshot]

This is the BlockChian form the foundation wallet. I tried several times to port it to the other client but each time ended with the 412 error.
Have a go and see if it works for you. Just make sure you make a backup of your old files.

https://mega.co.nz/#!aFU2GJjS!ncEOlQ8pesmQnSO0P48C_42VWmnRfl5-bapRpjqX7xE

[stoody]

They should change the way the do business otherwise they will be out of business. It's just ridiculous.

Tell me about it .. I had no reply from them about updating Diamond wallet and the ticked was placed 18 days ago. I was reminding them every 2 -3 days about it and nothing, even now the ticket is still unresolved. Had to go great lengths to get to them... but if they lied to me about the update, then yes it would be ridiculous and no chance I would trust them again.

i sold LTC for BTC on cryptsy and brought 49 DMD with it and sent it to my wallet after the minting started... and i have got them confermed in my wallet np at all it seems to be working fine for me

[That Guy]

I was running wallet 2.0.2.1 and had my wallet open for the starting of the POS, but found the next day that I appeared to be on the wrong chain, as I had all orphans. I fixed it by changing the node and reloading the blockchain, but why did I end up on the wrong fork? I thought being on the newest version would make sure I stayed on the right chain.

[Henle]

I originally let the wallet just run without doing anything, hoping the blockchain issue would work itself out.  It did, as previously reported by others.  Then I had to restart the pc, and the wallet wouldn't open.  Same error as others have posted.

This worked for me, so far, with a couple wallet close/wait a minute/restart wallets:
I backed up the whole roaming/Diamond directory, then deleted everything except Diamond.conf and wallet.dat
I added only the one indicated addnode to diamond.conf(addnode=193.68.21.19), so there was only one.
I added all the files and the database folder from Original.rar and let it resync using
    diamond-qt.exe -loadblock=blk0001.dat.  
I "lost" about 2/3 of my coins from my balance, but the transactions were still visible.
I closed the wallet, waited 1 minute, then opened it again using diamond-qt.exe -repairwallet

This worked.  My balance is correct, including some Diamonds minted yesterday 6/26.
I closed the wallet, waited 1 minute, then restarted it with just diamond-qt.exe.  It opened, and the balance was still correct.
So I did it again to be sure.  Closed the wallet, waited, restarted the wallet.  It's still good for me.

I assume since I only have one addnode I am on the right chain.  I have the same checkpoint info utahjohn and paladin281978 have posted:
{
"synccheckpoint" : "000000005babbddb5baad7bb9632738ab901b2f9eb3acfd2f390b2f4a97f1eee",
"height" : 463183,
"timestamp" : "2014-06-26 16:46:41 UTC"
}

getpeerinfo gives me 6 peers all running the right "subver" : "/Diamond:2.0.2.1/",

Can popshot, cryptonit, or Danbi confirm that's correct?

The only issue is now I have a whole mess of orphaned mint transactions from yesterday listed as my most recent transactions, even though they are not.  Someone else asked, with no reply, is there any way to get rid of them, or at least make them sort properly in date order so they disappear off the screen over time?

[polanskiman]

I originally let the wallet just run without doing anything, hoping the blockchain issue would work itself out.  It did, as previously reported by others.  Then I had to restart the pc, and the wallet wouldn't open.  Same error as others have posted.

This worked for me, so far, with a couple wallet close/wait a minute/restart wallets:
I backed up the whole roaming/Diamond directory, then deleted everything except Diamond.conf and wallet.dat
I added only the one indicated addnode to diamond.conf(addnode=193.68.21.19), so there was only one.
I added all the files and the database folder from Original.rar and let it resync using
    diamond-qt.exe -loadblock=blk0001.dat. 
I "lost" about 2/3 of my coins from my balance, but the transactions were still visible.
I closed the wallet, waited 1 minute, then opened it again using diamond-qt.exe -repairwallet

This worked.  My balance is correct, including some Diamonds minted yesterday 6/26.
I closed the wallet, waited 1 minute, then restarted it with just diamond-qt.exe.  It opened, and the balance was still correct.
So I did it again to be sure.  Closed the wallet, waited, restarted the wallet.  It's still good for me.

I assume since I only have one addnode I am on the right chain.  I have the same checkpoint info utahjohn and paladin281978 have posted:
{
"synccheckpoint" : "000000005babbddb5baad7bb9632738ab901b2f9eb3acfd2f390b2f4a97f1eee",
"height" : 463183,
"timestamp" : "2014-06-26 16:46:41 UTC"
}

getpeerinfo gives me 6 peers all running the right "subver" : "/Diamond:2.0.2.1/",

Can popshot, cryptonit, or Danbi confirm that's correct?

The only issue is now I have a whole mess of orphaned mint transactions from yesterday listed as my most recent transactions, even though they are not.  Someone else asked, with no reply, is there any way to get rid of them, or at least make them sort properly in date order so they disappear off the screen over time?

Not good for me. Each time I close the wallet and try to re-open it the same old assertion error happens and the circus starts all over again: delete the blkindex.dat file, add the OP blockchain files, open the wallet with the -loadblock flag, wait, wait, wait, then wait again for the sync. God forbids if I close the wallet or I am back to square one.