Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 783. (Read 1260636 times)

sure but by leave them on exchange u wasted all that coin-age

once u transfer them to your wallet u will start with 0 days coin-age and have to wait until ur coins old enough to earn pos rewards

I purchased DMD ages ago on cryptsy and held them there for months. are they still valid?

The checkpoint in my wallet:

{
"synccheckpoint" : "000000005babbddb5baad7bb9632738ab901b2f9eb3acfd2f390b2f4a97f1eee",
"height" : 463183,
"timestamp" : "2014-06-26 16:46:41 UTC"
}


Still minting and receiving pool payments, so I'm assuming I'm on the right chain (have not reason not to believe otherwise).

Not sure where Cryptsy got this transaction ID from for my withdraw, but it does not show in the block explorer:

ac97d25a0f0377f54ac45eacf6d3bbf36b89e75d4be266ba1cc06d93b8119c78


Hopefully, one day Cryptsy support will answer my ticket beyond "escalated to to tech support".  Would really like to stake my diamonds. 

same problem even if i copy the blockchain before close the wallet then open it again it's won't load same error

First of all first check as others instructed whether you are on the right chain by providing us with your latest checkpoint (type getcheckpoint in the console).

Cryptsy has most likely just one wallet for Diamond and the rest is managed by some smart accounting program. The 'coins' you see and trade on Cryptsy are not real 'coins' as these are just Cryptsy tokens. Only when you want to cash in from Cryptsy the 'real' coins are sent out. If people are able to get some coins out of Cryptsy then it should really  doesn't matter if the amount was small or big as your transaction forms a transaction block consisting of many transactions and they have specific weight limits (basically the same rules apply to small and big).  
The transaction you provided has been confirmed over 2k times so really not sure where it might have gone.

Having some info from Cryptsy would be helpful. But... lets wait for the wallet fix to see if that helps.

we all do  

 but in the meantime its easy workaround to restore a backuped blockchain and delete peers.dat and sync up again and this time dont close wallet

what u see here is always the same atempt to POS

once its not conformed coins return from stake to balance and try again

a likely reason beside being on wrong fork chain could be have a unlocked wallet and a not finished sync of blockchain

then it can happen it try top POS but it will always fail until wallet is synced up

u can ignore that entries in transaction logs

the coins that did try to stake returned to balance once their POS atempt did orphan and they kept their whole coin-age

this is a cosmetic problem

and we have on todo list a better check to not try POS until sync is finished (but at low priority)

normally all people have a password protected wallet and wouldn't unlock wallet until sync is finished

Unfortunately after restart, the wallet cannot load anymore.



I think, we need new wallet too

I had a backup copy of wallet.dat that was dated before the 26th, I used that one and did a full sync, all my failed mints dissapeared .. just yesterday I minted sucessfuly twice

I am pretty sure he is on the right block-chain. He is using the correct node. His issue is pretty much what I am having and to this very moment I still have those questions marks. Those minted coins are part of the orphaned blocks that occured on 26.

You're not alone on this one.  I made a large withdraw from Cryptsy as well yesterday as well and was given a bogus transaction ID:

Diamond  1000.00100000 DMD    Yes    2014-06-28 13:36:10
Processed    TrxID: ac97d25a0f0377f54ac45eacf6d3bbf36b89e75d4be266ba1cc06d93b8119c78 @ 2014-06-28 13:40:08

Made a 100 DMD withdraw earlier without any problems, but it seems the larger ones are getting forked over or something.

Put my support ticket in, but we'll see if I actually get a response.

go to debug console
type getcheckpoint
copy/past output and post it here to be verified you are on proper blockchain.

Popshot - Would you please check this transaction ID.  I bought and withdrew theses diamonds as per the attached:

Diamond 433.85467256 DMD Yes 2014-06-28 16:47:49
Processed TrxID: a92ae34e2adfd55576feb2f5f387ec6946db5b8cc51923171f87aa848d452a9a @ 2014-06-28 16:50:11

I tried checking the trxID with no luck on the block explorer.  I also submitted a ticket to Cryptsy.   Just wondering if it is showing confirmed?

The weird part is that I did a small purchase of 32 dmds and was able to receive that with no problem.  Do you think some of the diamonds on cryptsy are on the wrong fork?  Would that be messing things up when you make a large purchase?

Lost. You can say good bye to those. Orphaned. You can try the 'repairwallet' command in the console but it will only bring the coins that you mined, not the minted ones. Same happened to me and others. I recommend doing a backup of your wallet before tempting anything.

My wallet synced after deleting all in appdata ( w/o wallet.dat ) then downloaded blockchain and put it to appdata.
In conf file addnode=193.68.21.19

Than syncked after some time ... but I have another peoblem. Seems the PoS system not working well. Here is a shot:



Any ideas ?

i also got the assertion failed error

so, downloaded the Block Chain+Data from OP

deleted the necessary files and extract the Block chain from OP

open diamond QT and was able to successfully fully sync

shutdown diamond QT

back up and compress up-to-date Block Chain+Data

open diamond QT

... boom Assertion failed! again

tried to extract my up-to-date Block Chain+Data and still Assertion failed!

looks like ill just wait for new wallet

Anything < 2.0.2.1 Goodbye

bingo thats what we working on 
beside some other trace of problem origin which we deeper analyze now

New and improved next wallet version should just ban connections to old wallets LOL

10 out of 50 connections towards my wallet are using wrong wallet version!
thats 20% old wallets in network and constant troublemakers


console 29.06.2014 11:33:13

getpeerinfo

right wallet version: "subver" : "/Diamond:2.0.2.1/",
filtered and only show that wallets which run with wrong version

WALL OF SHAME: please update ur wallet from http://bit.diamonds/download.html

{
"addr" : "91.228.90.18:25046",
"services" : "00000001",
"lastsend" : 1404034326,
"lastrecv" : 1404034283,
"conntime" : 1403987273,
"version" : 60006,
"subver" : "/Diamond:2.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 466209,
"banscore" : 0
},
{
"addr" : "141.0.103.214:56782",
"services" : "00000001",
"lastsend" : 1404034354,
"lastrecv" : 1404034354,
"conntime" : 1403987273,
"version" : 60006,
"subver" : "/Diamond:0.7.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 466207,
"banscore" : 0
},

{
"addr" : "71.185.54.112:54144",
"services" : "00000001",
"lastsend" : 1404034379,
"lastrecv" : 1404034330,
"conntime" : 1403987307,
"version" : 60006,
"subver" : "/Diamond:0.7.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 466210,
"banscore" : 0
},

{
"addr" : "72.78.100.2:39940",
"services" : "00000001",
"lastsend" : 1404034326,
"lastrecv" : 1404034330,
"conntime" : 1403987343,
"version" : 60006,
"subver" : "/Diamond:2.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 466211,
"banscore" : 0
},


{
"addr" : "31.17.60.238:17771",
"services" : "00000001",
"lastsend" : 1404034326,
"lastrecv" : 1404034281,
"conntime" : 1403987385,
"version" : 60006,
"subver" : "/Diamond:2.0.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 466211,
"banscore" : 0
},

{
"addr" : "72.224.219.173:51137",
"services" : "00000001",
"lastsend" : 1404034326,
"lastrecv" : 1404034329,
"conntime" : 1403994301,
"version" : 60006,
"subver" : "/Diamond:2.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 466327,
"banscore" : 0
},
{
"addr" : "70.115.220.224:56232",
"services" : "00000001",
"lastsend" : 1404034355,
"lastrecv" : 1404034355,
"conntime" : 1403995903,
"version" : 60006,
"subver" : "/Diamond:2.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 466357,
"banscore" : 0
},

{
"addr" : "173.57.140.157:52461",
"services" : "00000001",
"lastsend" : 1404034326,
"lastrecv" : 1404034330,
"conntime" : 1403997549,
"version" : 60006,
"subver" : "/Diamond:2.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 466383,
"banscore" : 0
},

{
"addr" : "81.167.91.10:17652",
"services" : "00000001",
"lastsend" : 1404034326,
"lastrecv" : 1404034281,
"conntime" : 1404004719,
"version" : 60006,
"subver" : "/Diamond:2.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 466501,
"banscore" : 0
},

{
"addr" : "72.208.240.122:59851",
"services" : "00000001",
"lastsend" : 1404034326,
"lastrecv" : 1404034281,
"conntime" : 1404015622,
"version" : 60006,
"subver" : "/Diamond:2.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 466672,
"banscore" : 0
},