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

[pokeytex]

i send 43 DMD in cryptsy and these dont arrived in my account
ITs de Tix e7de04a854c9445ae0ebedcbb6e310b071fdc5dbe0de1a41c5e469958b76e70c
i dont understand the explorer
as I can tell if they came?

When I pasted the transaction ID you provided into the Block Crawler (http://dmdpool.digsys.bg/bc/block_crawler.php) it showed me that the transaction took place on June 28, 2014 at 01:48:11
and was confirmed 1513 times... so judging by that it should have arrived a long time ago.
However, things like that should be directly reported to Cryptsy really, as they should know for sure what's happening in their system.

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?

[utahjohn]

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 ?

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

[Coinish]

i send 43 DMD in cryptsy and these dont arrived in my account
ITs de Tix e7de04a854c9445ae0ebedcbb6e310b071fdc5dbe0de1a41c5e469958b76e70c
i dont understand the explorer
as I can tell if they came?

When I pasted the transaction ID you provided into the Block Crawler (http://dmdpool.digsys.bg/bc/block_crawler.php) it showed me that the transaction took place on June 28, 2014 at 01:48:11
and was confirmed 1513 times... so judging by that it should have arrived a long time ago.
However, things like that should be directly reported to Cryptsy really, as they should know for sure what's happening in their system.

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?

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.

[polanskiman]

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 ?

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

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.

[utahjohn]

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

[kondiomir]

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 ?

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

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.

Unfortunately after restart, the wallet cannot load anymore.



I think, we need new wallet too

[cryptonit]

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 ?

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

[cryptonit]

I think, we need new wallet too

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

[popshot]

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?

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.

[murders10]

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 ?

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

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.

Unfortunately after restart, the wallet cannot load anymore.



I think, we need new wallet too

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

[Coinish]

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. 

[HasHe]

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

[cryptonit]

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

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

[polanskiman]

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 ?

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

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.

Unfortunately after restart, the wallet cannot load anymore.

I think, we need new wallet too

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

It wont work. You need to use a block-chain pre-dating the PoS each time you close and re-open your wallet. Even after synching if you backup the block-chain and try using it, you will end up with the same assertion error.

Some have stated that re-downloading the wallet from scratch eventually solved the assertion error. I haven't tried that.

[pokeytex]

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?

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.

Current Checkpoint is:
"synccheckpoint" : "000000005babbddb5baad7bb9632738ab901b2f9eb3acfd2f390b2f4a97f1eee",
"height" : 463183,
"timestamp" : "2014-06-26 16:46:41 UTC"

[polanskiman]

Interesting entry in the peers:

Code:

"addr" : "185.16.108.205:17771",
"services" : "00000000",
"lastsend" : 1404093925,
"lastrecv" : 0,
"conntime" : 1404093925,
"version" : 0,
"subver" : "",
"inbound" : false,
"releasetime" : 0,
"startingheight" : -1,
"banscore" : 0

Note the subver line.

This is very easily spoofed anyways if you change the right code lines in the source code and then compile the wallet yourself.

[polanskiman]

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?

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.

Current Checkpoint is:
"synccheckpoint" : "000000005babbddb5baad7bb9632738ab901b2f9eb3acfd2f390b2f4a97f1eee",
"height" : 463183,
"timestamp" : "2014-06-26 16:46:41 UTC"

You are in the right block-chain.

[polanskiman]

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

As already stated by Danbi on post #1577 (https://bitcointalk.org/index.php?topic=580725.msg7569389#msg7569389) using an old backup (specially pre-dating PoS) of your wallet is not a good idea. I quote:

"Important: Because of the way PoS works, you should never restore your wallet from an old copy, once you have minted coins via PoS. This is, because PoS (sometimes) creates new private/public keys (addresses in your wallet)  and sends minted coins to these addresses in your wallet. If you restore an old wallet you will not have the secret keys and your minted amounts will be gone for good. Once you start minting, always make frequent backups of your wallet.dat file!"

Those who still have minted coins that are valid, you've been warn in doing such wallet swaps.

[Mxrider420z]

Anybody wanna trade DMD´s for a Watch Dogs game for pc, i have a spare one for trading

[utahjohn]

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

As already stated by Danbi on post #1577 (https://bitcointalk.org/index.php?topic=580725.msg7569389#msg7569389) using an old backup (specially pre-dating PoS) of your wallet is not a good idea. I quote:

"Important: Because of the way PoS works, you should never restore your wallet from an old copy, once you have minted coins via PoS. This is, because PoS (sometimes) creates new private/public keys (addresses in your wallet)  and sends minted coins to these addresses in your wallet. If you restore an old wallet you will not have the secret keys and your minted amounts will be gone for good. Once you start minting, always make frequent backups of your wallet.dat file!"

Those who still have minted coins that are valid, you've been warn in doing such wallet swaps.

The only stake attempt the day of 26th when PoS started was a failed mint, I don't mind losing that from wallet

The backup I used was a few days before 26th before minting.
I have staked successfully since re-sync with backup and have backed up wallet after minting, I feel safe with that