Sit Tight Boys.

With old address and new address the diamond coins are still not depositing into cryptsy. There still seems to be a problem with them.

The second deposit that I made which was only a while ago has no confirmations and a question mark. So what does this all mean?

Quite effective if is a DDoS, has completley disabled the correct blockchain sync from Danbi node not happening.

If you do not want to contradict yourself, you will admit that this is not centralized, publicly developed crypto currency. As such, if you know what the solution is, please either speak up, or if you have the expertise, contribute code to fix it.

Yes, this is a very temporary and very inconvenient measure, mostly for the permanent node operator!

By the way, we already implemented a fix related to the bitcoin bug you described.

According to this page at peercoin, pszTimestamp is supposed to have a max of 91 chars:
https://github.com/Peershares/Peershares/wiki/Genesis-Block-(Starting-a-New-Blockchain-Instance)

But ours is 117 characters:
https://github.com/DMDcoin/Diamond/blob/master/src/main.cpp#L2649

Is that the problem?

I believe I am good sync listening.........



02:53:44

[
{
"addr" : "[2001:0:5ef5:79fd:34b5:38b6:c1d3:1ded]:51258",
"services" : "00000001",
"lastsend" : 1406973105,
"lastrecv" : 1406973143,
"conntime" : 1406972800,
"version" : 60006,
"subver" : "/Diamond:2.0.3/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 514028,
"banscore" : 0
},
{
"addr" : "62.44.226.18:17771",
"services" : "00000001",
"lastsend" : 1406973143,
"lastrecv" : 1406973143,
"conntime" : 1406972802,
"version" : 60006,
"subver" : "/Diamond:2.0.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 514028,
"banscore" : 0
},
{
"addr" : "193.68.21.19:17771",
"services" : "00000001",
"lastsend" : 1406973144,
"lastrecv" : 1406973143,
"conntime" : 1406972812,
"version" : 60006,
"subver" : "/Diamond:2.0.3.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 514028,
"banscore" : 0
},
{
"addr" : "86.18.76.197:34821",
"services" : "00000001",
"lastsend" : 1406973145,
"lastrecv" : 1406973165,
"conntime" : 1406972939,
"version" : 60006,
"subver" : "/Diamond:2.0.3/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 241142,
"banscore" : 0
},
{
"addr" : "131.191.88.111:17771",
"services" : "00000001",
"lastsend" : 1406973143,
"lastrecv" : 1406973180,
"conntime" : 1406972950,
"version" : 60006,
"subver" : "/Diamond:2.0.2.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 386226,
"banscore" : 0
},
{
"addr" : "178.248.85.73:17771",
"services" : "00000001",
"lastsend" : 1406973143,
"lastrecv" : 1406973143,
"conntime" : 1406972978,
"version" : 60006,
"subver" : "/Diamond:2.0.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 514033,
"banscore" : 0
},
{
"addr" : "192.186.133.74:17771",
"services" : "00000001",
"lastsend" : 1406973143,
"lastrecv" : 1406973143,
"conntime" : 1406972979,
"version" : 60006,
"subver" : "/Diamond:2.0.2.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 386226,
"banscore" : 0
},
{
"addr" : "46.242.73.221:17771",
"services" : "00000001",
"lastsend" : 1406973143,
"lastrecv" : 1406973144,
"conntime" : 1406973013,
"version" : 60006,
"subver" : "/Diamond:2.0.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 514033,
"banscore" : 0
},
{
"addr" : "122.149.252.123:17771",
"services" : "00000000",
"lastsend" : 1406973223,
"lastrecv" : 0,
"conntime" : 1406973223,
"version" : 0,
"subver" : "",
"inbound" : false,
"releasetime" : 0,
"startingheight" : -1,
"banscore" : 0
}
]

My node went on a wrong fork again! :-(

cryptsy does the only right thing at this moment
they dont sync their exchange with their wallet
until everything is sorted

so ur coins there but not visible at exchange